The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 25021 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 25021.
It may have died unexpectedly, or you may not have permission to debug
the process.
panic action should run as root right?
log has this
[2010/05/04 08:56:44, 0] lib/fault.c:fault_report(40)
===============================================================
[2010/05/04 08:56:44, 0] lib/fault.c:fault_report(41)
INTERNAL ERROR: Signal 11 in pid 25021 (3.3.2)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2010/05/04 08:56:44, 0] lib/fault.c:fault_report(43)
I'm hesitant to attach a core publicly since this is a production system and it looks like it contains some private data like usernames and groups and my full smb.conf. can I extract anything useful from it?
now I've just getting this
The Samba 'panic action' script, /usr/share/ samba/panic- action,
was called for PID 25021 ().
This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 25021.
It may have died unexpectedly, or you may not have permission to debug
the process.
panic action should run as root right?
log has this
[2010/05/04 08:56:44, 0] lib/fault. c:fault_ report( 40) ======= ======= ======= ======= ======= ======= ======= ======= == c:fault_ report( 41) c:fault_ report( 43)
=====
[2010/05/04 08:56:44, 0] lib/fault.
INTERNAL ERROR: Signal 11 in pid 25021 (3.3.2)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2010/05/04 08:56:44, 0] lib/fault.
From: http:// www.samba. org/samba/ docs/Samba3- HOWTO.pdf c:fault_ report( 44) ======= ======= ======= ======= ======= ======= ======= ======= == c:smb_panic( 1673) c:log_stack_ trace(1777) smbd(log_ stack_trace+ 0x2d) [0xb7cb939c] smbd(smb_ panic+0x80) [0xb7cb94f9] smbd(copy_ serverinfo+ 0x6a) [0xb7cfd984] smbd(change_ to_user+ 0x3e5) [0xb7b98b95] smbd(smbd_ process+ 0xf58) [0xb7bb6dcc] smbd(main+ 0x1126) [0xb7b7e32f] i686/cmov/ libc.so. 6(__libc_ start_main+ 0xe5) [0xb7691775] c:smb_panic( 1678) samba/panic- action 25021] c:smb_panic( 1686) c:dump_ core(231) samba/cores/ smbd
[2010/05/04 08:56:44, 0] lib/fault.
=====
[2010/05/04 08:56:44, 0] lib/util.
PANIC (pid 25021): internal error
[2010/05/04 08:56:44, 0] lib/util.
BACKTRACE: 11 stack frames:
#0 /usr/sbin/
#1 /usr/sbin/
#2 /usr/sbin/smbd [0xb7ca4e9e]
#3 [0xb7aec400]
#4 /usr/sbin/
#5 /usr/sbin/
#6 /usr/sbin/smbd [0xb7bb4b78]
#7 /usr/sbin/
#8 /usr/sbin/
#9 /lib/tls/
#10 /usr/sbin/smbd [0xb7b7b0a1]
[2010/05/04 08:56:44, 0] lib/util.
smb_panic(): calling panic action [/usr/share/
[2010/05/04 08:56:45, 0] lib/util.
smb_panic(): action returned status 0
[2010/05/04 08:56:45, 0] lib/fault.
dumping core in /var/log/
I'm hesitant to attach a core publicly since this is a production system and it looks like it contains some private data like usernames and groups and my full smb.conf. can I extract anything useful from it?