On Mon, Oct 03, 2011 at 05:15:30PM -0700, Linda W wrote: > Jeremy Allison wrote: > > On Sun, Oct 02, 2011 at 04:33:12PM -0700, Linda Walsh wrote: > > > >> ---- > >> I have a bunch of these in my log... Was wondering if anyone had seen > >> them before > >> and what the cause might be? Thanks... > >> > >> > >> Oct 1 03:31:14 Ishtar smbd[24022]: #1 /usr/sbin/smbd(smb_panic+0x55) > >> [0x7f7120093134] > >> Oct 1 03:31:14 Ishtar smbd[24164]: [2011/10/01 03:31:14, 0] > >> lib/util.c:1468(smb_panic) > >> Oct 1 03:31:14 Ishtar smbd[24164]: PANIC (pid 24164): internal error > >> Oct 1 03:31:14 Ishtar smbd[24164]: #1 /usr/sbin/smbd(smb_panic+0x55) > >> [0x7f7120093134] > >> Oct 1 03:31:17 Ishtar smbd[24165]: [2011/10/01 03:31:17, 0] > >> lib/util.c:1468(smb_panic) > >> Oct 1 03:31:17 Ishtar smbd[24165]: PANIC (pid 24165): internal error > >> Oct 1 03:31:17 Ishtar smbd[24165]: #1 /usr/sbin/smbd(smb_panic+0x55) > >> [0x7f7120093134] > >> > > > > Add the line: > > > > panic action = /bin/sleep 9999999 > > > ------ > > Is it possible to do something like a kill -SIGABRT $$ or $PPID and have > it gen a core?
Well you don't want to kill -SIGABRT until it's already crashed, which you don't know until it's already failed. Adding the "panic action" is definitely the way to go, as the gdb "bt" on a live (albeit waiting) process captures the entire callstack showing where (and often why) you got the panic. As I'm probably going to be the one looking at the backtrace, this is the way I like to work :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
