I started my AD-member server with the DC not being present.
Afterwards, I executed the "good practice" sequence from the howtos for
testing a installation:
"testparm ..."
"nmblookup -d ..."
"nmblookup -M ..."
"nmblookup __SAMBA__ ..."
"smbclient -L ..."
And some domain tests:
"net ads testjoin"
"net ads lookup"
"wbinfo -D"
"getent passwd"
"getent group"
"wbinfo -t"
What was strange: wbinfo -D returned "Active Directory: No"
I then started my DC and tried to connect to a share.
That was the point where I noticed, that winbind had a panic!
Due to issue #5625 I had set my debug level to 0, so a have only limited
information from the logs.
Below are the complete logs.
It looks, like winbind is still trying to connect to 0.0.0.0, that's why
I think, that #5551 is not completely resolved.
I have a core-dump (arm9-cpu), would this help?
After restarting the daemons (with the DC being online), no further
problems appeared.
-
smblog.ad
-
[2008/07/22 14:16:30, 0] printing/nt_printing.c:nt_printing_init(659)
nt_printing_init: error checking published printers: WERR_ACCESS_DENIED
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\domänencomputer
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\domänencontroller
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\schema-admins
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\organisations-admins
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\zertifikatherausgeber
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\domänen-admins
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\domänen-gäste
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\richtlinien-ersteller-besitzer
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\dnsupdateproxy
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\backoffice template users
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\backoffice folder operators
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\backoffice mail operators
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\backoffice remote operators
[2008/07/22 14:20:49, 0] nsswitch/winbindd_group.c:winbindd_getgrent(1110)
could not lookup domain group DOMAIN\nasdriveuser
[2008/07/22 14:22:01, 0] lib/fault.c:fault_report(41)
===
[2008/07/22 14:22:01, 0] lib/fault.c:fault_report(42)
INTERNAL ERROR: Signal 6 in pid 17485 (3.0.31)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/07/22 14:22:01, 0] lib/fault.c:fault_report(44)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/07/22 14:22:01, 0] lib/fault.c:fault_report(45)
===
[2008/07/22 14:22:01, 0] lib/util.c:smb_panic(1633)
PANIC (pid 17485): internal error
[2008/07/22 14:22:01, 0] lib/util.c:log_stack_trace(1737)
BACKTRACE: 1 stack frames:
#0 /boot/usr/local/adsamba/bin/winbindd(log_stack_trace+0x20) [0xce48c]
[2008/07/22 14:22:01, 0] lib/fault.c:dump_core(181)
dumping core in /var/log/adsamba/cores/winbindd
[2008/07/22 14:22:42, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2008/07/22 14:22:42, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2008/07/22 14:22:42, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 0.0.0.0. Error =
Connection reset by peer
-
wb-BUILTIN.log
-
[2008/07/22 14:21:54, 0]
nsswitch/winbindd_dual.c:async_request_timeout_handler(181)
async_request_timeout_handler: child pid 17541 is not responding.
Closing connection to it.
-
winbind-idmap.log
-
[2008/07/22 14:21:17, 0]
nsswitch/winbindd_dual.c:async_request_timeout_handl
