[Samba] Samba 4.1.6 + RPC Problem + DNS + RSAT

[Günter Kukkukk]

Am 17.03.2014 22:38, schrieb Manfred Weiß:
> Hy everybody, 
> 
> I have a little problem. Since a crash of my server we have problems to connect over the RSAT tools to our Samba 4 domain with the DNS tool. 
> 
> At the moment we have a Centos 6.5 server with Version 4.1.6-SerNet-RedHat-7.el6. 
> 
> If I connect to the AD server with the RSAT tool, i get this message in the log.smb: 
> 
> dnsserver: Found DNS zone _msdcs.nagy-blumen.at 
> [2014/03/17 21:57:36.010984, 0] ../lib/util/fault.c:72(fault_report) 
> =============================================================== 
> [2014/03/17 21:57:36.011186, 0] ../lib/util/fault.c:73(fault_report) 
> INTERNAL ERROR: Signal 11 in pid 26870 (4.1.6-SerNet-RedHat-7.el6) 
> Please read the Trouble-Shooting section of the Samba HOWTO 
> [2014/03/17 21:57:36.011373, 0] ../lib/util/fault.c:75(fault_report) 
> =============================================================== 
> [2014/03/17 21:57:36.011497, 0] ../lib/util/fault.c:144(smb_panic_default) 
> PANIC: internal error 
> 
> 
> Same error we get on command line with this command: samba-tool dns query ad01.domain.test domain.test @ ALL -UAdministrator 
> 
> 
> 
> netstat before connecting : 
> 
> netstat -anp | grep '88\|135\|389\|464\|636\|1024\|3268\|3269\|53' | grep -i listen 
> tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN 27695/samba 
> tcp 0 0 10.30.0.2:53 0.0.0.0:* LISTEN 26519/named-sdb 
> tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 26519/named-sdb 
> tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 27695/samba 
> tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 26519/named-sdb 
> tcp 0 0 0.0.0.0:636 0.0.0.0:* LISTEN 27693/samba 
> tcp 0 0 0.0.0.0:1024 0.0.0.0:* LISTEN 27689/samba 
> tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 880/nrpe 
> tcp 0 0 0.0.0.0:3268 0.0.0.0:* LISTEN 27693/samba 
> tcp 0 0 0.0.0.0:3269 0.0.0.0:* LISTEN 27693/samba 
> tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 27693/samba 
> tcp 0 0 0.0.0.0:135 0.0.0.0:* LISTEN 27689/samba 
> tcp 0 0 ::1:53 :::* LISTEN 26519/named-sdb 
> tcp 0 0 ::1:953 :::* LISTEN 26519/named-sdb 
> 
> 
> netstat after connecting: 
> 
> netstat -anp | grep '88\|135\|389\|464\|636\|1024\|3268\|3269\|53' | grep -i listen 
> tcp 0 0 0.0.0.0:464 0.0.0.0:* LISTEN 27120/samba 
> tcp 0 0 10.30.0.2:53 0.0.0.0:* LISTEN 26519/named-sdb 
> tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 26519/named-sdb 
> tcp 0 0 0.0.0.0:88 0.0.0.0:* LISTEN 27120/samba 
> tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 26519/named-sdb 
> tcp 0 0 0.0.0.0:636 0.0.0.0:* LISTEN 27118/samba 
> tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 880/nrpe 
> tcp 0 0 0.0.0.0:3268 0.0.0.0:* LISTEN 27118/samba 
> tcp 0 0 0.0.0.0:3269 0.0.0.0:* LISTEN 27118/samba 
> tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 27118/samba 
> tcp 0 0 ::1:53 :::* LISTEN 26519/named-sdb 
> tcp 0 0 ::1:953 :::* LISTEN 26519/named-sdb 
> 
> Somebody has an idea what that might be ? 
> 
> Kind regards 
> Manfred 
> 

looks like the endpoint mapper (port 135) is dieing.
Run samba inside a root console as:  samba -i -M single -d10
and carefully watch all initial startup messages - and
then what happens during dns query...

Cheers, Günter

--