From a user of the Debian packages in unstable (3.0.25a): I am using the rid idmap backend to resolve names from my windows 2003 domain. This system was working until I updated the packages recently. I receive an e-mail from samba whenever I try to connect from my windows server: The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 17401 (/usr/sbin/winbindd). Looking at /var/log/samba/log.winbind shows the following entries (partial log): [2007/06/11 10:19:24, 3] nsswitch/winbindd_misc.c:winbindd_ping(470) [ 0]: ping [2007/06/11 10:19:24, 10] nsswitch/winbindd.c:process_request(311) process_request: request fn PING [2007/06/11 10:19:24, 3] nsswitch/winbindd_misc.c:winbindd_ping(470) [ 0]: ping [2007/06/11 10:19:24, 10] nsswitch/winbindd.c:process_request(311) process_request: request fn ALLOCATE_GID [2007/06/11 10:19:24, 0] lib/fault.c:fault_report(41) =============================================================== [2007/06/11 10:19:24, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 6 in pid 17395 (3.0.25a) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/06/11 10:19:24, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/06/11 10:19:24, 0] lib/fault.c:fault_report(45) =============================================================== [2007/06/11 10:19:24, 0] lib/util.c:smb_panic(1632) PANIC (pid 17395): internal error [2007/06/11 10:19:24, 0] lib/util.c:log_stack_trace(1736) BACKTRACE: 13 stack frames: #0 /usr/sbin/winbindd(log_stack_trace+0x1c) [0x4d1c3c] #1 /usr/sbin/winbindd(smb_panic+0x43) [0x4d1d23] #2 /usr/sbin/winbindd [0x4bfb52] #3 /lib/libc.so.6 [0x2b863eea0ca0] #4 /lib/libc.so.6(gsignal+0x35) [0x2b863eea0c45] #5 /lib/libc.so.6(abort+0x110) [0x2b863eea25c0] #6 /usr/sbin/winbindd(talloc_get_name+0x38) [0x4b8a28] #7 /usr/sbin/winbindd(talloc_check_name+0x1e) [0x4b8c7e] #8 /usr/sbin/winbindd(talloc_check_name_abort+0x19) [0x4d1e59] #9 /usr/sbin/winbindd [0x476bc4] #10 /usr/sbin/winbindd(main+0x83c) [0x44fa2c] #11 /lib/libc.so.6(__libc_start_main+0xf4) [0x2b863ee8d8e4] #12 /usr/sbin/winbindd [0x44e0e9] [2007/06/11 10:19:24, 0] lib/util.c:smb_panic(1637) smb_panic(): calling panic action [/usr/share/samba/panic-action 17395] BFD: /usr/sbin/winbindd: don't know how to handle OS specific section `.gnu.hash' [0x6ffffff6] "/usr/sbin/winbindd": not in executable format: File format not recognized BFD: /usr/sbin/winbindd: don't know how to handle OS specific section `.gnu.hash' [0x6ffffff6] "/usr/sbin/winbindd": not in executable format: File format not recognized //17395: No such file or directory. No stack. Downgrading back to 3.0.24 from Debian testing solved the issue
Created attachment 2772 [details] smb.conf file
Created attachment 2773 [details] Level 10 debug log of a failed session
Created attachment 2774 [details] gdb output This attachment is the output of gdb when running unstripped winbind binary from the samba-dbg Debian package
THe backtrace is lacking symbols, but from the context of the debug output I think this problem is completely fixed in revision 23525 This will be out with 3.0.25b