• Not sure if this is the right area or not.

    Just had my home pfsense box restart and I'm not sure why or where to look. Below is the log showing up until the point it restarted.

    Its just a normal intel atom box with stat HD

    Smart Status checks out ok on the HD.

    I couldn't tell you how long the uptime was but it had to be over a month or so. ANy ideas?

    r 9 07:54:02	kernel: Features=0xbfe9fbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Apr 9 07:54:02	kernel: Origin = "GenuineIntel" Id = 0x106c2 Family = 6 Model = 1c Stepping = 2
    Apr 9 07:54:02	kernel: CPU: Intel(R) Atom(TM) CPU 330 @ 1.60GHz (1602.40-MHz 686-class CPU)
    Apr 9 07:54:02	kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
    Apr 9 07:54:02	kernel: root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386
    Apr 9 07:54:02	kernel: FreeBSD 8.3-RELEASE-p11 #1: Wed Sep 11 18:47:57 EDT 2013
    Apr 9 07:54:02	kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
    Apr 9 07:54:02	kernel: The Regents of the University of California. All rights reserved.
    Apr 9 07:54:02	kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    Apr 9 07:54:02	kernel: Copyright (c) 1992-2012 The FreeBSD Project.
    Apr 9 07:54:02	syslogd: kernel boot file is /boot/kernel/kernel
    Apr 9 07:50:05	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:50:05	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:48:03	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:48:03	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:45:57	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:45:57	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:43:47	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:43:47	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:41:39	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:41:39	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:39:45	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:39:45	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:37:46	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:37:46	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:35:42	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:35:42	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:33:35	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:33:35	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:31:40	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:31:40	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:29:28	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:29:28	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:27:30	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:27:30	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:25:24	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:25:24	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:23:19	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:23:19	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:21:25	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:21:25	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:19:23	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:19:23	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:17:25	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:17:25	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:15:29	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:15:29	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:13:19	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:13:19	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:11:18	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:11:18	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:09:26	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:09:26	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:07:25	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:07:25	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:05:17	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:05:17	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:03:07	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:03:07	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:00:57	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 07:00:57	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:59:03	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:59:03	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:57:05	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:57:05	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:55:00	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:55:00	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:52:53	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:52:53	dhcp6c[44737]: client6_recvadvert: XID mismatch
    Apr 9 06:51:00	dhcp6c[44737]: client6_recvadvert: XID mismatch</fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>
    
  • Netgate Administrator

    Power glitch most likely if it restarted spontaneously rather than panicked. Not much to go in that log other than the fact that you obviously have some IPv6 config issues in your network.
    Looks like you're still running 2.1, try upgrading to 2.1.1 or wait for the imminent 2.1.2 security update.

    Steve


  • Steve's right, but it might be a power supply issue too, not necessarily a power outage you would notice in your house.

    I chased one system for a good month until a new power supply stopped intermittent spontaneous reboots.  Looked at RAM speed, cooling, etc, before I swapped out the power supply.


  • I agree with the others, PSU pr even heat issues are common for causing "spontaneous" reboots.

  • Netgate Administrator

    If it was failing RAM or HD I would expect to see some error message or a kernel panic. If it was overheating you might see a message indicating that from the bios (or a beep/flashing LEDs) but it would also probably halt rather than reboot. Of course that's if it was failing gracefully and the normal over-heat prevention measures cut in. If some unexpected component is overheating then it could reboot though that's not useful behaviour.

    Steve


  • I feel bad for
    a) bumping this back to the top
    b) leaving you guys hanging.

    As it turns out it was in fact a power glitch in the room where the firewall is plugged in.

    Fixed the "problem" with a UPS.

    Thanks to all.


  • Thank your stars.  Where I live, if a week goes by and things haven't rebooted due to a power glitch, I would start to think something was wrong.

  • Netgate Administrator

    Thanks for coming back with a result, many don't.  ;)

    Steve