Winbindd does not start a long time after add a new domain in a domain forest.
Following output with debug level 10:
Adding cache entry with key = SOME/DOMAIN; value =
S-1-5-21-xxxxxxxxx-xxxxxxxx-xxxxxxx and timeout = Tue Jul 19 16:58:08 2005
(297 seconds ahead)
Found domain (null)
INTERNAL ERROR: Signal 11 in pid 19792 (3.0.14a-SerNet-RedHat)
Please read the appendix Bugs of the Samba HOWTO collection
PANIC: internal error
BACKTRACE: 11 stack frames:
#0 winbindd(smb_panic2+0x1b6) [0x80d6922]
#1 winbindd(smb_panic+0x19) [0x80d6768]
#2 winbindd [0x80c4339]
#3 winbindd [0x80c43ae]
#4 /lib/tls/libc.so.6 [0x38eeb8]
#5 winbindd [0x808052b]
#6 winbindd [0x808088c]
#7 winbindd(init_domain_list+0x121) [0x8080b8d]
#8 winbindd(main+0x580) [0x807b161]
#9 /lib/tls/libc.so.6(__libc_start_main+0xda) [0x37c78a]
#10 winbindd(chroot+0x31) [0x807981d]
client_read: read 0 bytes. Need 1824 more for a full request.
read failed on sock 8, pid 19792: EOF
I suppose, that the domain exist but no SID is appropriate at the moment. The
domain is not completed replicate on all other domaincontrollers,inclusive my
"password server". When winbind try to get Information about the domain, they
will be not available.
I think winbindd should start at this point but don't inlcude the not completed
Winbindd has had significant work put into it between 3.0.14a and 3.0.20. Is it
possible you can test this with the 3.0.20 pre-release ?
closing . no response.