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:25:15 Ishtar smbd[23925]: [2011/10/01 03:25:15, 0] > lib/util.c:1468(smb_panic) > Oct 1 03:25:15 Ishtar smbd[23925]: PANIC (pid 23925): internal error > Oct 1 03:25:15 Ishtar smbd[23925]: #1 /usr/sbin/smbd(smb_panic+0x55) > [0x7f7120093134] > Oct 1 03:25:15 Ishtar smbd[23926]: [2011/10/01 03:25:15, 0] > lib/util.c:1468(smb_panic) > Oct 1 03:25:15 Ishtar smbd[23926]: PANIC (pid 23926): internal error > Oct 1 03:25:15 Ishtar smbd[23926]: #1 /usr/sbin/smbd(smb_panic+0x55) > [0x7f7120093134] > Oct 1 03:29:49 Ishtar smbd[23927]: [2011/10/01 03:29:49, 0] > lib/util.c:1468(smb_panic) > Oct 1 03:29:49 Ishtar smbd[23927]: PANIC (pid 23927): internal error > Oct 1 03:29:49 Ishtar smbd[23927]: #1 /usr/sbin/smbd(smb_panic+0x55) > [0x7f7120093134] > Oct 1 03:29:49 Ishtar smbd[24021]: [2011/10/01 03:29:49, 0] > lib/util.c:1468(smb_panic) > Oct 1 03:29:49 Ishtar smbd[24021]: PANIC (pid 24021): internal error > Oct 1 03:29:49 Ishtar smbd[24021]: #1 /usr/sbin/smbd(smb_panic+0x55) > [0x7f7120093134] > Oct 1 03:31:14 Ishtar smbd[24022]: [2011/10/01 03:31:14, 0] > lib/util.c:1468(smb_panic) > Oct 1 03:31:14 Ishtar smbd[24022]: PANIC (pid 24022): internal error > 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 to the [global] section of your smb.conf. Restart Samba. When it panics again you'll be left with a sleep process whose parent is the crashed smbd. Attach to this with gdb and get (and post) a backtrace. That'll help us track this down and fix it (if it isn't already fixed). Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
