[Samba] Latest winbind creating fault

[Bjoern Baumbach]

Dear Dimitri,

thank you for reporting this issue.

Unfortunately your posted backtrace does not include the needed debug
symbols. To get these information you can install the SerNet
samba3-debuginfo package on your system. After the installation you can
run the following to get a full backtrace:

gdb /usr/sbin/winbindd var/log/samba/cores/winbindd
(gdb) bt full

Best regards,
Björn Baumbach

On 05/01/2013 02:24 PM, Dimitri Yioulos wrote:
> All,
> 
> Yesterday morning, I updated samba from samba3-3.6.13-45 to  
> samba3-3.6.14-45 (obtained from sernet) on a couple of 
> CentOS 5.9 boxes.  As soon as users started access these 
> boxes, one of my sensors detected a winbind error, as in:
> 
> Apr 30 08:19:36 norwell winbindd[13283]:   INTERNAL ERROR: 
> Signal 11 in pid 13283 (3.6.14)
> 
> Here's what appears in syslog:
> 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.667710,  0] lib/fault.c:47(fault_report) 
> Apr 30 08:19:36 norwell winbindd[8938]:   
> =============================================================== 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.670612,  0] lib/fault.c:48(fault_report) 
> Apr 30 08:19:36 norwell winbindd[8938]:   INTERNAL ERROR: 
> Signal 11 in pid 8938 (3.6.14) 
> Apr 30 08:19:36 norwell winbindd[8938]:   Please read the 
> Trouble-Shooting section of the Samba3-HOWTO 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.671113,  0] lib/fault.c:50(fault_report) 
> Apr 30 08:19:36 norwell winbindd[8938]:    
> Apr 30 08:19:36 norwell winbindd[8938]:   From: 
> http://www.samba.org/samba/docs/Samba3-HOWTO.pdf 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.671456,  0] lib/fault.c:51(fault_report) 
> Apr 30 08:19:36 norwell winbindd[8938]:   
> =============================================================== 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.671683,  0] lib/util.c:1117(smb_panic) 
> Apr 30 08:19:36 norwell winbindd[8938]:   PANIC (pid 8938): 
> internal error 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.675330,  0] lib/util.c:1221(log_stack_trace) 
> Apr 30 08:19:36 norwell winbindd[8938]:   BACKTRACE: 17 
> stack frames: 
> Apr 30 08:19:36 norwell winbindd[8938]:    #0 
> winbindd(log_stack_trace+0x2d) [0x31b655] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #1 
> winbindd(smb_panic+0x7c) [0x31b787] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #2 winbindd 
> [0x30b8ce] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #3 [0xd39420] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #4 winbindd 
> [0x23a080] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #5 
> winbindd(_wbint_LookupRids+0x8a) [0x258d08] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #6 winbindd 
> [0x263596] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #7 
> winbindd(winbindd_dual_ndrcmd+0x13a) [0x257a42] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #8 winbindd 
> [0x256a0c] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #9 winbindd 
> [0x32e432] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #10 
> winbindd(tevent_common_loop_immediate+0x111) [0x32ceed] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #11 
> winbindd(run_events_poll+0x3e) [0x32b095] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #12 winbindd 
> [0x32b80f] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #13 
> winbindd(_tevent_loop_once+0x9d) [0x32bd2d] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #14 
> winbindd(main+0xd32) [0x22e303] 
> Apr 30 08:19:36 norwell winbindd[8938]:    
> #15 /lib/libc.so.6(__libc_start_main+0xdc) [0xdc0ebc] 
> Apr 30 08:19:36 norwell winbindd[8938]:    #16 winbindd 
> [0x22b111] 
> Apr 30 08:19:36 norwell winbindd[8938]: [2013/04/30 
> 08:19:36.677068,  0] lib/fault.c:372(dump_core) 
> Apr 30 08:19:36 norwell winbindd[8938]:   dumping core 
> in /var/log/samba/cores/winbindd 
> Apr 30 08:19:36 norwell winbindd[8938]: 
> 
> Unfortunately, I was unable to do any further debugging.
> 
> This morning, I rolled back installation to 
> samba3-3.6.13-45, and the problem has gone away.
> 
> Bug in latest version on sernet?
> 
> Dimitri
> 

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de