Bug 5868 - Windbind crashes after upgradeing from 3.0.23 to 3.2.4
Summary: Windbind crashes after upgradeing from 3.0.23 to 3.2.4
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.2
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 3.2.4
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-03 09:34 UTC by Erik Sørnes
Modified: 2009-08-06 09:29 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Sørnes 2008-11-03 09:34:36 UTC 
After upgradeing from sles9-x86 samba 3.0.23 to 3.2.4 Windind suddenly crashes
After starting winbind again, everything seems fine.
Samba server was joined to domain in ads mode (net join ads) when it was running 3.0.23

I will upload core-file
I will upload other files at request

-regards
Erik
Comment 1 Erik Sørnes 2008-11-03 09:58:46 UTC 
Output of log.winbindd when the dump happened:

[2008/11/03 16:18:36,  3] winbindd/winbindd_sid.c:winbindd_sid_to_gid(296)
  [ 7362]: sid to gid S-1-5-21-1100344877-3013322779-101495848-19260
[2008/11/03 16:18:36,  3] winbindd/winbindd_sid.c:winbindd_sid_to_gid(296)
  [ 7000]: sid to gid S-1-5-21-29509730-458046710-584457872-12263
[2008/11/03 16:19:30,  0] lib/fault.c:fault_report(40)
  ===============================================================
[2008/11/03 16:19:30,  0] lib/fault.c:fault_report(41)
  INTERNAL ERROR: Signal 6 in pid 5791 (3.2.4-0.1.130-1906-SUSE-SLES9)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2008/11/03 16:19:30,  0] lib/fault.c:fault_report(43)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2008/11/03 16:19:30,  0] lib/fault.c:fault_report(44)
  ===============================================================
[2008/11/03 16:19:30,  0] lib/util.c:smb_panic(1663)
  PANIC (pid 5791): internal error
[2008/11/03 16:19:30,  0] lib/util.c:log_stack_trace(1767)
  BACKTRACE: 16 stack frames:
   #0 /usr/sbin/winbindd(log_stack_trace+0x2d) [0x8158170]
   #1 /usr/sbin/winbindd(smb_panic+0x8e) [0x8157fce]
   #2 /usr/sbin/winbindd [0x8142290]
   #3 /usr/sbin/winbindd [0x81422a1]
   #4 [0xffffe420]
   #5 /lib/tls/libc.so.6(abort+0x1a5) [0x4027fe65]
   #6 /usr/sbin/winbindd(talloc_parent+0) [0x81259ae]
   #7 /usr/sbin/winbindd(talloc_get_name+0x3e) [0x8126a4c]
   #8 /usr/sbin/winbindd(talloc_check_name+0x31) [0x8126aa3]
   #9 /usr/sbin/winbindd(talloc_check_name_abort+0x2c) [0x815a597]
   #10 /usr/sbin/winbindd [0x80c449c]
   #11 /usr/sbin/winbindd(run_events+0x13b) [0x816ae65]
   #12 /usr/sbin/winbindd [0x8094cad]
   #13 /usr/sbin/winbindd(main+0xb66) [0x8095cf2]
   #14 /lib/tls/libc.so.6(__libc_start_main+0xd0) [0x4026c210]
   #15 /usr/sbin/winbindd [0x80932e1]
[2008/11/03 16:19:30,  0] lib/fault.c:dump_core(201)
  dumping core in /var/log/samba/cores/winbindd
Comment 2 Erik Sørnes 2008-11-03 10:04:06 UTC 
Not able to upload core-file. To big.
Comment 3 Jeremy Allison 2008-11-03 19:41:28 UTC 
Add the following to the [global] section of your smb.conf :

panic action = "/bin/sleep 90000"

load the symbols for winbindd from the SuSE distro and reproduce the crash. winbindd will be blocked at the crash point waiting for the sleep. Attach to the crashed winbindd process with gdb and type "bt" (backtrace). Please post the output of this command.

Jeremy.
Comment 4 Erik Sørnes 2008-12-11 03:15:24 UTC 
We have not been able to reproduce the problem. 
If it arises anew, I will follow Jeremys action plan

-regards
Erik
Comment 5 Guenther Deschner 2009-08-06 09:29:59 UTC 
Closing, as no longer reproduceable. Please reopen once you see this happen again.