Dear list, I have Debian Etch with Samba Version 3.0.24 configured as a PDC. Every day I get exactly 9 emails with panic action:> The Samba 'panic action' script, /usr/share/samba/panic-action, > was called for PID 4170 (). > > This means there was a problem with the program, such as a segfault. > However, the executable could not be found for process 4170. > It may have died unexpectedly, or you may not have permission to debug > the process.All emails are sent at the same time usually in the morning between 7:30 and 8:30. I cannot find anything dubious within the logfiles (samba's and syslog) nor do I recognize any functional errors. How can I find out what triggers these panic actions? Thanks, Ralph
Noone got an idea? *push* *push* :) Ralph Kutschera schrieb:> Dear list, > > I have Debian Etch with Samba Version 3.0.24 configured as a PDC. > > Every day I get exactly 9 emails with panic action: > >> The Samba 'panic action' script, /usr/share/samba/panic-action, >> was called for PID 4170 (). >> >> This means there was a problem with the program, such as a segfault. >> However, the executable could not be found for process 4170. >> It may have died unexpectedly, or you may not have permission to debug >> the process. > > All emails are sent at the same time usually in the morning between 7:30 > and 8:30. > > I cannot find anything dubious within the logfiles (samba's and syslog) > nor do I recognize any functional errors. > > How can I find out what triggers these panic actions? > > Thanks, > Ralph >
2009/10/27 Ralph Kutschera <news2010 at ecuapac.at>:> Michael Wood schrieb: >> >> Try adding in "ulimit -S -c unlimited" as well to change the soft limit. > > I did so, but there are still no coredumps :(Does this work for you? $ cat /proc/sys/kernel/core_pattern core $ ulimit -c 0 $ cat abort.c #include <stdlib.h> int main() { abort(); } $ gcc -o abort abort.c $ ./abort Aborted $ ulimit -H -c unlimited $ ulimit -S -c unlimited $ ulimit -c unlimited $ ./abort Aborted (core dumped) $ ls -l core -rw------- 1 user user 143360 2009-10-27 17:21 core -- Michael Wood <esiotrot at gmail.com>
Michael Wood schrieb:> Does this work for you? > [..]YES, it does!> # cat /proc/sys/kernel/core_pattern > /var/log/coredumps/core.%e.%p> # ulimit -c > 0> # cat abort.c > #include <stdlib.h> > int main() > { > abort(); > }> # gcc -o abort abort.c> # ./abort > Aborted> # ulimit -H -c unlimited > # ulimit -S -c unlimited > # ulimit -c > unlimited> # ./abort > Aborted (core dumped)> # ls -l /var/log/coredumps/core.abort.25679 > -rw------- 1 root root 163840 2009-10-30 12:11 /var/log/coredumps/core.abort.25679Ralph
Hallo again, Well, after installing logwatch I found the following. Maybe this can help? TIA, Ralph lib/fault.c:dump_core(168) unable to change to /var/log/samba/cores/smbdrefusing to dump core : 9 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25337 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25346 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25355 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25364 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25372 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25380 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25388 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25397 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 25405 (3.0.24) Please read the Trouble-Shooting section of the Samba3-HOWTO : 1 Time(s) lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf : 9 Time(s) lib/util.c:log_stack_trace(1706) BACKTRACE: 16 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6] #2 /usr/sbin/smbd [0x821a69a] #3 [0xb7f1a420] #4 /usr/sbin/smbd [0x81327bb] #5 /usr/sbin/smbd(api_rpcTNP+0x15f) [0x818b71f] #6 /usr/sbin/smbd(api_pipe_request+0x183) [0x818bd03] #7 /usr/sbin/smbd [0x818603e] #8 /usr/sbin/smbd [0x809bced] #9 /usr/sbin/smbd [0x809c1dc] #10 /usr/sbin/smbd(reply_trans+0x56f) [0x809ce4f] #11 /usr/sbin/smbd [0x80ea674] #12 /usr/sbin/smbd(smbd_process+0x6fd) [0x80eb83d] #13 /usr/sbin/smbd(main+0x10df) [0x82c384f] #14 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7b8cea8] #15 /usr/sbin/smbd [0x8082b11] : 3 Time(s) lib/util.c:log_stack_trace(1706) BACKTRACE: 18 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x23) [0x822c3d3] #1 /usr/sbin/smbd(smb_panic+0x46) [0x822c4c6] #2 /usr/sbin/smbd [0x821a69a] #3 [0xb7f1a420] #4 /usr/sbin/smbd [0x8193cd1] #5 /usr/sbin/smbd(lsa_io_r_lookup_sids2+0x85) [0x8194f35] #6 /usr/sbin/smbd [0x81302a4] #7 /usr/sbin/smbd(api_rpcTNP+0x15f) [0x818b71f] #8 /usr/sbin/smbd(api_pipe_request+0x183) [0x818bd03] #9 /usr/sbin/smbd [0x818603e] #10 /usr/sbin/smbd [0x809bced] #11 /usr/sbin/smbd [0x809c1dc] #12 /usr/sbin/smbd(reply_trans+0x56f) [0x809ce4f] #13 /usr/sbin/smbd [0x80ea674] #14 /usr/sbin/smbd(smbd_process+0x6fd) [0x80eb83d] #15 /usr/sbin/smbd(main+0x10df) [0x82c384f] #16 /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7b8cea8] #17 /usr/sbin/smbd [0x8082b11] : 6 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25337): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25346): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25355): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25364): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25372): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25380): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25388): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25397): internal error : 1 Time(s) lib/util.c:smb_panic(1599) PANIC (pid 25405): internal error : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25337] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25346] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25355] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25364] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25372] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25380] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25388] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25397] : 1 Time(s) lib/util.c:smb_panic(1607) smb_panic(): calling panic action [/usr/share/samba/panic-action 25405] : 1 Time(s) lib/util.c:smb_panic(1615) smb_panic(): action returned status 0 : 9 Time(s) lib/util_sock.c:read_socket_with_timeout(497) read_socket_with_timeout: timeout read. read error = Input/output error. : 1 Time(s) nmbd/nmbd_browsesync.c:announce_local_master_browser_to_domain_master_browser(108) announce_local_master_browser_to_domain_master_browser: We are both a domain and a local master browser for workgroup WTSP. Do not announce to ourselves. : 96 Time(s) nmbd/nmbd_browsesync.c:sync_with_dmb(152) sync_with_dmb: Initiating sync with domain master browser SERVER1<20> at IP xxx.xxx.xxx.xxx for workgroup WTSP : 96 Time(s) nmbd/nmbd_packets.c:process_dgram(1270) process_dgram: ignoring malformed3 (datasize = 494, len=408, off=100) datagram packet sent to name WTSP<00> from IP 129.27.223.23 : 17 Time(s) nmbd/nmbd_packets.c:process_dgram(1270) process_dgram: ignoring malformed3 (datasize = 494, len=408, off=100) datagram packet sent to name WTSP<00> from IP 129.27.223.9 : 17 Time(s) printing/pcap.c:pcap_cache_reload(159) Unable to open printcap file /etc/printcap for read! : 260 Time(s) rpc_server/srv_samr_nt.c:_samr_lookup_domain(2797) Returning domain sid for domain WTSP -> S-1-5-21-xxxxxxxxx-xxxxxxxxx-xxxxxxxxx : 20 Time(s)
Hi 2009/11/24 Ralph Kutschera <news2010 at ecuapac.at>:> Hallo again, > > ?Well, after installing logwatch I found the following. Maybe this can help? > > TIA, > ?Ralph > > ?lib/fault.c:dump_core(168) ?unable to change to > /var/log/samba/cores/smbdrefusing to dump core : 9 Time(s)Make sure /var/log/samba/cores/smbd exists and that smbd will be able to write core dumps there. Although, since you are getting the stack traces anyway, I suppose there might not be much point to doing that. -- Michael Wood <esiotrot at gmail.com>
On Thu, Nov 26, 2009 at 01:54:42PM +0100, Ralph Kutschera wrote:> Volker Lendecke schrieb: >> On Tue, Nov 24, 2009 at 04:59:19PM +0100, Ralph Kutschera wrote: >>> Well, after installing logwatch I found the following. Maybe this >>> can help? >> >> What version of Unix and what version of Samba are you >> running? > > # cat /proc/version > Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-26etch1) > (dannf at debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian > 4.1.1-21)) #1 SMP Thu Nov 5 16:28:13 UTC 2009 > > # smbd --version > Version 3.0.24Any chance you try with a later version? Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20091201/b0f9a361/attachment.pgp>
Volker Lendecke schrieb:>> # smbd --version >> Version 3.0.24 > > Any chance you try with a later version? >Yes! # smbd --version Version 3.2.5 ... and the problem still exists and I am still not able to get a coredump. So I assume samba actually is not crashing. What else could trigger the panic-action-script?> VolkerRalph
On Thu, Feb 18, 2010 at 09:19:10AM +0100, Ralph Kutschera wrote:> Volker Lendecke schrieb: >>> # smbd --version >>> Version 3.0.24 >> >> Any chance you try with a later version? >> > > Yes! > > # smbd --version > Version 3.2.5 > > ... and the problem still exists and I am still not able to get a > coredump. So I assume samba actually is not crashing. What else could > trigger the panic-action-script?A crash does. If possible, can you get us a debug level 10 log of smbd leading to this crash? Even better would be a valgrind trace of smbd that crashes. Thanks, Volker