Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
Hi, I only have GELI encrypted zfs filesystems on that system, so not easily. But I’ll try to create a VM and replicate the crash as soon as I have time. But for now I’ll probably switch to ipfw if pf+VIMAGE is unstable. Thanks, Philipp On 27 Mar 2014, at 16:32, John Baldwin wrote: > Can you get a crashdump when it crashes? Also, I thought that > VIMAGE + pf is known to be unstable? > > -- > John Baldwin > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" signature.asc Description: Message signed with OpenPGP using GPGMail
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
I'm not sure it's the same issue. I use neither vmimage nor pf. Also, as I mentioned in http://lists.freebsd.org/pipermail/freebsd-current/2014-March/048939.html r258000, from 11 Nov 2013, works fine. I haven't received any hint as to what might have caused this panic between 258000 and 260689. So, when I have the time, I'll do a binary search. Perhaps this offending change was MFC'd to 10-stable, which is why you are seeing it now. Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thursday, March 27, 2014 11:08:10 am Philipp Schmid wrote: > Hello, > > I have the same problem on a HP Microserver N54L with FreeBSD 10 release. > > If a jail is running and the jail executes > > /etc/periodic/daily/450.status-security > > the server crashes. This happens every night at 4:03 CET. > > If I run > > /etc/periodic/daily/450.status-security > > manually in the jail, the server also crashes immediately. > > Now I wanted to try to same as Anton and run each script in > > /etc/periodic/security > > manually, but I also get: > > ASSERTION FAILED: Unexpected value for $PERIODIC: ‘' > > I then ran: > > setenv PERIODIC "security daily” > > which allowed me to run each security script separately. > > If I run: > > root@jail:/etc/periodic/security # ./520.pfdenied > > the machine immediately reboots. > > Looking at 520.pfdenied I tried running the command: > > root@jail:~ # pfctl -sr -v > > directly, which also crashes the host immediately. > > > All the best, > > Philipp > > PS: I have a custom kernel with VIMAGE which I use with the jail Can you get a crashdump when it crashes? Also, I thought that VIMAGE + pf is known to be unstable? -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
Hello, the problem seems to exist for a few years now: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/160496 All the best, Philipp --- OpenResearch Software Development OG Geschäftsführer (CEO) & Co-Founder Gumpendorfer Straße 132/9 1060 Vienna, Austria +43 699 17246437 philipp.sch...@openresearch.com http://www.openresearch.com On 27 Mar 2014, at 16:08, Philipp Schmid wrote: > Hello, > > I have the same problem on a HP Microserver N54L with FreeBSD 10 release. > > If a jail is running and the jail executes > > /etc/periodic/daily/450.status-security > > the server crashes. This happens every night at 4:03 CET. > > If I run > > /etc/periodic/daily/450.status-security > > manually in the jail, the server also crashes immediately. > > Now I wanted to try to same as Anton and run each script in > > /etc/periodic/security > > manually, but I also get: > > ASSERTION FAILED: Unexpected value for $PERIODIC: ‘' > > I then ran: > > setenv PERIODIC "security daily” > > which allowed me to run each security script separately. > > If I run: > > root@jail:/etc/periodic/security # ./520.pfdenied > > the machine immediately reboots. > > Looking at 520.pfdenied I tried running the command: > > root@jail:~ # pfctl -sr -v > > directly, which also crashes the host immediately. > > > All the best, > > Philipp > > PS: I have a custom kernel with VIMAGE which I use with the jail > > --- > OpenResearch Software Development OG > Geschäftsführer (CEO) & Co-Founder > Gumpendorfer Straße 132/9 > 1060 Vienna, Austria > > +43 699 17246437 > > philipp.sch...@openresearch.com > http://www.openresearch.com > signature.asc Description: Message signed with OpenPGP using GPGMail
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
Hello, I have the same problem on a HP Microserver N54L with FreeBSD 10 release. If a jail is running and the jail executes /etc/periodic/daily/450.status-security the server crashes. This happens every night at 4:03 CET. If I run /etc/periodic/daily/450.status-security manually in the jail, the server also crashes immediately. Now I wanted to try to same as Anton and run each script in /etc/periodic/security manually, but I also get: ASSERTION FAILED: Unexpected value for $PERIODIC: ‘' I then ran: setenv PERIODIC "security daily” which allowed me to run each security script separately. If I run: root@jail:/etc/periodic/security # ./520.pfdenied the machine immediately reboots. Looking at 520.pfdenied I tried running the command: root@jail:~ # pfctl -sr -v directly, which also crashes the host immediately. All the best, Philipp PS: I have a custom kernel with VIMAGE which I use with the jail --- OpenResearch Software Development OG Geschäftsführer (CEO) & Co-Founder Gumpendorfer Straße 132/9 1060 Vienna, Austria +43 699 17246437 philipp.sch...@openresearch.com http://www.openresearch.com signature.asc Description: Message signed with OpenPGP using GPGMail
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
I've spent a lot of time on this. At some point I started suspecting disk failures, based on dd errors and smartmontools reports. So I replaced the disks, and then replaced the whole box for another nominally identical SunBlade 1500. The panics persisted. I now think that multiple cold reboots might have damaged disks, not the other way round. In the end I had to conclude that this is not a hardware problem, but the OS issue, perhaps triggered by some heavy disk I/O. Various frequent panics exist at least from r260689 to r263096: r260689: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/186760 r260914: http://www.freebsd.org/cgi/query-pr.cgi?pr=187219 r261798: http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 r263096: http://www.freebsd.org/cgi/query-pr.cgi?pr=187527 I now reverted as far back as r258000, and the system seems stable, but I probably need few more days to be sure. If the system is indeed stable at r258000, when I have the time, I'll try to narrow down the problem revision. But I'd appreciate any hint that might save time. Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From b...@0x20.net Thu Mar 6 22:02:56 2014 > >On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote: >> In my initial PR (sparc64 r261798), >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 >> >> I said that rsync was triggering this panic. >> While true, I now see that there's more to it. >> I disabled the rsync, and the cron jobs. >> Still I get exactly the same panic every >> night at 03:02: >> >> # grep Dumptime /var/crash/* >> /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 >> /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 >> /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 >> /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 >> /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 >> /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 >> /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 >> /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 >> # >> >> This is likely triggered by one of >> the daily periodic scipts, >> after about 1 min from start: >> >> # grep daily /etc/crontab >> # Perform daily/weekly/monthly maintenance. >> 1 3 * * * rootperiodic daily >> # >> >> but which one? > >Some time ago I had a similar problem with 8.x. Setting > >vm.kmem_size="512M" >vm.kmem_size_max="512M" > >in loader.conf helped. It's just a wild guess but might help. This didn't make any difference. However, I noticed that the panics were happening more and more often. I started suspecting a disk failure, so decided to do a full integrity check with dd, got: 17054+0 records in 17054+0 records out 17882415104 bytes transferred in 1035.889679 secs (17262857 bytes/sec) (ada1:ata2:0:1:0): READ_DMA. ACB: c8 00 80 93 9c 42 00 00 00 00 00 00 (ada1:ata2:0:1:0): CAM status: ATA Status Error (ada1:ata2:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) (ada1:ata2:0:1:0): RES: 51 40 21 94 9c 02 02 00 00 00 00 (ada1:ata2:0:1:0): Retrying command (ada1:ata2:0:1:0): READ_DMA. ACB: c8 00 80 93 9c 42 00 00 00 00 00 00 (ada1:ata2:0:1:0): CAM status: ATA Status Error (ada1:ata2:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) (ada1:ata2:0:1:0): RES: 51 40 21 94 9c 02 02 00 00 00 00 (ada1:ata2:0:1:0): Retrying command (ada1:ata2:0:1:0): READ_DMA. ACB: c8 00 80 93 9c 42 00 00 00 00 00 00 (ada1:ata2:0:1:0): CAM status: ATA Status Error (ada1:ata2:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) (ada1:ata2:0:1:0): RES: 51 40 21 94 9c 02 02 00 00 00 00 (ada1:ata2:0:1:0): Retrying command (ada1:ata2:0:1:0): READ_DMA. ACB: c8 00 80 93 9c 42 00 00 00 00 00 00 (ada1:ata2:0:1:0): CAM status: ATA Status Error (ada1:ata2:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) (ada1:ata2:0:1:0): RES: 51 40 21 94 9c 02 02 00 00 00 00 (ada1:ata2:0:1:0): Retrying command (ada1:ata2:0:1:0): READ_DMA. ACB: c8 00 80 93 9c 42 00 00 00 00 00 00 (ada1:ata2:0:1:0): CAM status: ATA Status Error (ada1:ata2:0:1:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) (ada1:ata2:0:1:0): RES: 51 40 21 94 9c 02 02 00 00 00 00 (ada1:ata2:0:1:0): Error 5, Retries exhausted dd: /dev/ada1b: Input/output error I guess the disk is fucked, right? Given that it's about 10 years old, this is not surprising. Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From b...@0x20.net Thu Mar 6 22:02:56 2014 > >On Thu, Mar 06, 2014 at 12:59:14AM -0800, Anton Shterenlikht wrote: >> In my initial PR (sparc64 r261798), >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 >> >> I said that rsync was triggering this panic. >> While true, I now see that there's more to it. >> I disabled the rsync, and the cron jobs. >> Still I get exactly the same panic every >> night at 03:02: >> >> # grep Dumptime /var/crash/* >> /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 >> /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 >> /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 >> /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 >> /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 >> /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 >> /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 >> /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 >> # >> >> This is likely triggered by one of >> the daily periodic scipts, >> after about 1 min from start: >> >> # grep daily /etc/crontab >> # Perform daily/weekly/monthly maintenance. >> 1 3 * * * rootperiodic daily >> # >> >> but which one? > >Some time ago I had a similar problem with 8.x. Setting > >vm.kmem_size="512M" >vm.kmem_size_max="512M" > >in loader.conf helped. It's just a wild guess but might help. >-- >Bjoern Engels Was it also on sparc64? How did you find this out? I mean what lead you to this discovery? Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 6, 2014, at 11:28, Lowell Gilbert wrote: > Glen Barber writes: > > > On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: > >> >Can you go into /etc/periodic/daily and execute those scripts one by > >> >one? You should be able to narrow down which one is the culprit. > >> > >> unfortunately I cannot reproduce the panic > >> this way. What I did was: > >> > >> # cd /etc/periodic/daily > >> # for file in `ls` > >> do > >> echo $file > >> ./$file > >> done > >> > >> I run it twice, I could see all scripts > >> executing one after another, > >> but no panic. > >> Perhaps something else is happening at > >> the same time as daily scripts? > >> But I cannot find what. > >> > > > > It can also be one of the scripts in /etc/periodic/security. > > > > Can you retry your test in that directory, as well? > > "periodic daily" would be a slightly better test... > That won't help him narrow down the exact periodic script causing it, which is what he's trying to do. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
Glen Barber writes: > On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: >> >Can you go into /etc/periodic/daily and execute those scripts one by >> >one? You should be able to narrow down which one is the culprit. >> >> unfortunately I cannot reproduce the panic >> this way. What I did was: >> >> # cd /etc/periodic/daily >> # for file in `ls` >> do >> echo $file >> ./$file >> done >> >> I run it twice, I could see all scripts >> executing one after another, >> but no panic. >> Perhaps something else is happening at >> the same time as daily scripts? >> But I cannot find what. >> > > It can also be one of the scripts in /etc/periodic/security. > > Can you retry your test in that directory, as well? "periodic daily" would be a slightly better test... ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 06, 2014 at 08:07:14AM -0800, Anton Shterenlikht wrote: > >>From g...@freebsd.org Thu Mar 6 15:58:51 2014 > > > >On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: > >> >Can you go into /etc/periodic/daily and execute those scripts one by > >> >one? You should be able to narrow down which one is the culprit. > >>=20 > >> unfortunately I cannot reproduce the panic > >> this way. What I did was: > >>=20 > >> # cd /etc/periodic/daily > >> # for file in `ls` > >> do > >> echo $file > >> ./$file > >> done > >>=20 > >> I run it twice, I could see all scripts > >> executing one after another, > >> but no panic. > >> Perhaps something else is happening at > >> the same time as daily scripts? > >> But I cannot find what. > >>=20 > > > >It can also be one of the scripts in /etc/periodic/security. > > > >Can you retry your test in that directory, as well? > > > >Glen > > # pwd > /etc/periodic/security > # for file in `ls` > do > echo $file > ./$file > done > 100.chksetuid > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 110.neggrpperm > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 200.chkmounts > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 300.chkuid0 > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 400.passwdless > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 410.logincheck > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 460.chkportsum > > Checking for ports with mismatched checksums: > 500.ipfwdenied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 510.ipfdenied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 520.pfdenied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 550.ipfwlimit > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 610.ipf6denied > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 700.kernelmsg > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 800.loginfail > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > 900.tcpwrap > ASSERTION FAILED: Unexpected value for $PERIODIC: '' > security.functions > # > > Perhaps these scripts cannot be simply > executed from the command line? > Sigh. It looks like someone "fixed" something... I'm certain this used to work when run directly. Glen pgpZuQTNUAyFB.pgp Description: PGP signature
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From g...@freebsd.org Thu Mar 6 15:58:51 2014 > >On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: >> >Can you go into /etc/periodic/daily and execute those scripts one by >> >one? You should be able to narrow down which one is the culprit. >>=20 >> unfortunately I cannot reproduce the panic >> this way. What I did was: >>=20 >> # cd /etc/periodic/daily >> # for file in `ls` >> do >> echo $file >> ./$file >> done >>=20 >> I run it twice, I could see all scripts >> executing one after another, >> but no panic. >> Perhaps something else is happening at >> the same time as daily scripts? >> But I cannot find what. >>=20 > >It can also be one of the scripts in /etc/periodic/security. > >Can you retry your test in that directory, as well? > >Glen # pwd /etc/periodic/security # for file in `ls` do echo $file ./$file done 100.chksetuid ASSERTION FAILED: Unexpected value for $PERIODIC: '' 110.neggrpperm ASSERTION FAILED: Unexpected value for $PERIODIC: '' 200.chkmounts ASSERTION FAILED: Unexpected value for $PERIODIC: '' 300.chkuid0 ASSERTION FAILED: Unexpected value for $PERIODIC: '' 400.passwdless ASSERTION FAILED: Unexpected value for $PERIODIC: '' 410.logincheck ASSERTION FAILED: Unexpected value for $PERIODIC: '' 460.chkportsum Checking for ports with mismatched checksums: 500.ipfwdenied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 510.ipfdenied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 520.pfdenied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 550.ipfwlimit ASSERTION FAILED: Unexpected value for $PERIODIC: '' 610.ipf6denied ASSERTION FAILED: Unexpected value for $PERIODIC: '' 700.kernelmsg ASSERTION FAILED: Unexpected value for $PERIODIC: '' 800.loginfail ASSERTION FAILED: Unexpected value for $PERIODIC: '' 900.tcpwrap ASSERTION FAILED: Unexpected value for $PERIODIC: '' security.functions # Perhaps these scripts cannot be simply executed from the command line? Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: > >Can you go into /etc/periodic/daily and execute those scripts one by > >one? You should be able to narrow down which one is the culprit. > > unfortunately I cannot reproduce the panic > this way. What I did was: > > # cd /etc/periodic/daily > # for file in `ls` > do > echo $file > ./$file > done > > I run it twice, I could see all scripts > executing one after another, > but no panic. > Perhaps something else is happening at > the same time as daily scripts? > But I cannot find what. > It can also be one of the scripts in /etc/periodic/security. Can you retry your test in that directory, as well? Glen pgptKuJTtZEyT.pgp Description: PGP signature
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
>From: Mark Felder > >On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote: >> In my initial PR (sparc64 r261798), >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 >> >> I said that rsync was triggering this panic. >> While true, I now see that there's more to it. >> I disabled the rsync, and the cron jobs. >> Still I get exactly the same panic every >> night at 03:02: >> >> # grep Dumptime /var/crash/* >> /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 >> /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 >> /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 >> /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 >> /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 >> /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 >> /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 >> /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 >> # >> >> This is likely triggered by one of >> the daily periodic scipts, >> after about 1 min from start: >> >> # grep daily /etc/crontab >> # Perform daily/weekly/monthly maintenance. >> 1 3 * * * rootperiodic daily >> # >> >> but which one? >> > >Can you go into /etc/periodic/daily and execute those scripts one by >one? You should be able to narrow down which one is the culprit. unfortunately I cannot reproduce the panic this way. What I did was: # cd /etc/periodic/daily # for file in `ls` do echo $file ./$file done I run it twice, I could see all scripts executing one after another, but no panic. Perhaps something else is happening at the same time as daily scripts? But I cannot find what. Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
On Thu, Mar 6, 2014, at 2:59, Anton Shterenlikht wrote: > In my initial PR (sparc64 r261798), > > http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 > > I said that rsync was triggering this panic. > While true, I now see that there's more to it. > I disabled the rsync, and the cron jobs. > Still I get exactly the same panic every > night at 03:02: > > # grep Dumptime /var/crash/* > /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 > /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 > /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 > /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 > /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 > /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 > /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 > /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 > # > > This is likely triggered by one of > the daily periodic scipts, > after about 1 min from start: > > # grep daily /etc/crontab > # Perform daily/weekly/monthly maintenance. > 1 3 * * * rootperiodic daily > # > > but which one? > Can you go into /etc/periodic/daily and execute those scripts one by one? You should be able to narrow down which one is the culprit. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
In my initial PR (sparc64 r261798), http://www.freebsd.org/cgi/query-pr.cgi?pr=187080 I said that rsync was triggering this panic. While true, I now see that there's more to it. I disabled the rsync, and the cron jobs. Still I get exactly the same panic every night at 03:02: # grep Dumptime /var/crash/* /var/crash/info.0: Dumptime: Wed Feb 26 10:10:51 2014 /var/crash/info.1: Dumptime: Thu Feb 27 03:02:14 2014 /var/crash/info.2: Dumptime: Fri Feb 28 03:02:29 2014 /var/crash/info.3: Dumptime: Sat Mar 1 03:02:25 2014 /var/crash/info.4: Dumptime: Tue Mar 4 03:02:01 2014 /var/crash/info.5: Dumptime: Wed Mar 5 03:02:05 2014 /var/crash/info.6: Dumptime: Thu Mar 6 03:02:11 2014 /var/crash/info.last: Dumptime: Thu Mar 6 03:02:11 2014 # This is likely triggered by one of the daily periodic scipts, after about 1 min from start: # grep daily /etc/crontab # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily # but which one? Please help Thanks Anton ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
