Hi, Thanks, that's what I thought. Is there a way to know which daily periodic script was running when my server crashed ?
Cheers, Mickaël On Tue, 2011-03-22 at 08:46 -0400, Gary Palmer wrote: > On Tue, Mar 22, 2011 at 11:53:14AM +0100, Micka?l Can?vet wrote: > > Hi, > > > > I have a redundant NAS made of FreeBSD + HAST + ZFS and 24TB of disks. > > > > This morning my primary node crashed around 4:20am. > > > > On the console I can see: > > > > Fatal double fault > > rip = 0xffffffff805e78b8 > > rsp = 0xffffff8485d43fc0 > > rbp = 0xffffff8485d44010 > > cpuid = 1; apic id = 12 > > panic: double fault > > cpuid = 1 > > KDB: stack backstrace: > > #0 0xffffffff805f4e0e at kdb_backtrace+0x5e > > #1 0xffffffff805c2d07 at panic+0x187 > > #2 0xffffffff808ac366 at dblfault_handler+0x96 > > #3 0xffffffff808950bd at Xdblfault+0xad > > Uptime: 4d14h7m5s > > Cannot sump, Device not defined or unavailable. > > > > The only thing I can see on my munin graphs is a strange IO activity > > (disk and network over my HAST link) that starts at 3am every morning > > and last about 1 hour and a half (and so until crash this morning). I > > double checked my scheduled scripts and I do not do anything at that > > time. So I suspect a system script to be responsible of this activity. > > I'm not sure that this IO activity results in the crash, but that the > > only track I have. > > 3am is when the scripts in /etc/periodic/daily fire > > # grep daily /etc/crontab > # Perform daily/weekly/monthly maintenance. > 1 3 * * * root periodic daily > > > Regards, > > Gary >
signature.asc
Description: This is a digitally signed message part
