Samba Panic and Internal Error periodically. Mostly found in log for one client Windows XP machine. Text of log file follows. The cores directory was empty, despite the message below. [2009/06/09 10:55:31, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 11 in pid 31514 (3.2.5) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/06/09 10:55:31, 0] lib/fault.c:fault_report(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/06/09 10:55:31, 0] lib/fault.c:fault_report(44) =============================================================== [2009/06/09 10:55:31, 0] lib/util.c:smb_panic(1663) PANIC (pid 31514): internal error [2009/06/09 10:55:31, 0] lib/util.c:log_stack_trace(1767) BACKTRACE: 22 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8201d24] #1 /usr/sbin/smbd(smb_panic+0x80) [0x8201e81] #2 /usr/sbin/smbd [0x81ecc73] #3 [0xb7f9e400] #4 /usr/sbin/smbd(cli_receive_smb+0x83) [0x80efe82] #5 /usr/sbin/smbd(cli_negprot+0x1a1) [0x80f1761] #6 /usr/sbin/smbd(cli_start_connection+0x3d7) [0x80f2060] #7 /usr/sbin/smbd(cli_full_connection+0x85) [0x80f55db] #8 /usr/sbin/smbd(_spoolss_rffpcnex+0x533) [0x816d31a] #9 /usr/sbin/smbd [0x815c9d6] #10 /usr/sbin/smbd(api_rpcTNP+0x2b6) [0x818d229] #11 /usr/sbin/smbd(api_pipe_request+0x238) [0x818d821] #12 /usr/sbin/smbd [0x8186d85] #13 /usr/sbin/smbd(write_to_pipe+0x13d) [0x818530e] #14 /usr/sbin/smbd [0x841506e] #15 /usr/sbin/smbd [0x84157d5] #16 /usr/sbin/smbd(reply_trans+0x726) [0x84163c8] #17 /usr/sbin/smbd [0x80de096] #18 /usr/sbin/smbd(smbd_process+0x429) [0x80dfbe1] #19 /usr/sbin/smbd(main+0xfa2) [0x80a747f] #20 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b54455] #21 /usr/sbin/smbd [0x80a4511] [2009/06/09 10:55:31, 0] lib/util.c:smb_panic(1668) smb_panic(): calling panic action [/usr/share/samba/panic-action 31514] [2009/06/09 10:55:31, 0] lib/util.c:smb_panic(1676) smb_panic(): action returned status 0 [2009/06/09 10:55:31, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/smbd [2009/06/09 10:56:06, 1] smbd/service.c:make_connection_snum(1194) hp-audrey (::ffff:192.168.1.199) connect to service Projects initially as user audrey (uid=1003, gid=1003) (pid
Is there a possibility that you install debuginfo packages? This way we would get the exact line number of the crash. It would be absolutely brilliant if you could run that smbd under valgrind --tool=memcheck. Be aware that valgrind slows down operations a LOT (10x or more). Volker
(In reply to comment #1) > Is there a possibility that you install debuginfo packages? This way we would > get the exact line number of the crash. It would be absolutely brilliant if you > could run that smbd under valgrind --tool=memcheck. Be aware that valgrind > slows down operations a LOT (10x or more). > > Volker > I'm afraid I'm not familiar with debuginfo packages. Is there somewhere I can download? Running valgrind is probably not an option on this server at this point. Sorry I can't be of more help.
Ok, what kind of Unix are you using? If it is a recent Linux distro, it might be the case that you have additional Samba packages that have "debuginfo" in their names. Just install them and wait for the next crash, if all goes right then you will see line numbers in the backtrace. Please upload that. Thanks, Volker
The server is running Debian Lenny. I did a package search but found nothing containing "debuginfo" related to Samba. Regards, David
This is very likely either fixed or a different problem on modern Samba versions. Closing bug report.