Bug 1444 - Winbindd crash
Winbindd crash
Product: Samba 3.0
Classification: Unclassified
Component: winbind
Other Linux
: P3 major
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2004-06-08 12:32 UTC by Robin Rosenberg
Modified: 2005-08-24 10:26 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Robin Rosenberg 2004-06-08 12:32:01 UTC
Winbindd crashed without any obvious reason so all NT users were unknown to the 
Linux machine. After restarting winbind it started identifying users as 
DOMAIN+username instead of just username. Then it turned out that restarting 
winbindd wasn't that successfull and a number of winbindd daemons was left 
hanging. Kill -9:ing them and then restarting winbindd didn't fix the usernames 
After rebooting the machine all usernames were correct again. Can I restart 
winbindd fully without rebooting the machine? 
Here's the crash dump that I found in the logs (before attempting restart). 
[2004/06/08 00:57:58, 0] lib/fault.c:fault_report(36) 
[2004/06/08 00:57:59, 0] lib/fault.c:fault_report(37) 
  INTERNAL ERROR: Signal 11 in pid 9070 (3.0.2a) 
  Please read the appendix Bugs of the Samba HOWTO collection 
[2004/06/08 00:57:59, 0] lib/fault.c:fault_report(39) 
[2004/06/08 00:57:59, 0] lib/util.c:smb_panic(1400) 
  PANIC: internal error 
[2004/06/08 00:57:59, 0] lib/util.c:smb_panic(1408) 
  BACKTRACE: 11 stack frames: 
   #0 winbindd(smb_panic+0x1ab) [0x80bced0] 
   #1 winbindd [0x80ab995] 
   #2 winbindd [0x80aba0a] 
   #3 /lib/tls/libc.so.6 [0x4019f718] 
   #4 winbindd(winbindd_pam_auth_crap+0x980) [0x8079397] 
   #5 winbindd(strftime+0x12c8) [0x806d22c] 
   #6 winbindd(winbind_process_packet+0x1f) [0x806d518] 
   #7 winbindd(strftime+0x1e7c) [0x806dde0] 
   #8 winbindd(main+0x51c) [0x806e3df] 
   #9 /lib/tls/libc.so.6(__libc_start_main+0xed) [0x4018c95d] 
   #10 winbindd(ldap_msgfree+0x7d) [0x806cb51] 
Searching the logs on the Linux machine did not reveal anything, but on the NT 
server I could see this: 
Accesses		CreateUser  
..as well as password management calls of (brrr) unknow origin.
Comment 1 Gerald (Jerry) Carter 2004-06-08 12:54:38 UTC
I think this should already be fixed in 3.0.4.  I remember we 
fixed a bug with and identical stack trace.  I can't find an 
exact bug id though.
Comment 2 Robin Rosenberg 2004-06-08 13:13:34 UTC
Thanks. It seems easy to repeat, so I'll try that. After a while I found the 
I was playing around with Sharity and checked the Store Credentials and Use as 
default boxes and that caused the crash instantly. 
Comment 3 Gerald (Jerry) Carter 2005-08-24 10:26:29 UTC
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.