• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

First Ever crash

Scheduled Pinned Locked Moved General pfSense Questions
6 Posts 4 Posters 722 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    troyborg
    last edited by Dec 18, 2017, 5:01 PM

    Yesterday (Dec. 17th 2017 around midnight) my pfsense router randomly crashed.

    I was playing my Xbox One, when it happened, I noticed the game couldn't communicate with the servers, then I heard my PC say it lost connection to my teamspeak server.  Then a few seconds later I hear the pfsense PC do its POST beep.

    I submitted the crash report, was wondering what caused it?

    After it came back up I noticed 2.4.2 was available so I had it update to that.

    https://pcpartpicker.com/b/YfXH99

    1 Reply Last reply Reply Quote 0
    • K
      kejianshi
      last edited by Dec 18, 2017, 5:08 PM

      So…  Have you been running it for an hour or 5 years?

      1 Reply Last reply Reply Quote 0
      • N
        NollipfSense
        last edited by Dec 18, 2017, 5:11 PM

        Have you checked syslog to learn what caused the crash…that should have been your first step before posting!

        pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
        pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

        1 Reply Last reply Reply Quote 0
        • T
          troyborg
          last edited by Dec 18, 2017, 10:38 PM Dec 18, 2017, 10:31 PM

          Been running it since March 12, 2016.
          If you're wondering about 2.4.2    I've been running that no issues for like 25 days.

          I checked the system.log and all I see is this…

          Dec 18 16:20:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver)
          Dec 18 16:21:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service clamd stopped. Restarting clamd (ClamAV Antivirus)
          Dec 18 16:21:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service squid stopped. Restarting squid (Squid Proxy Server Service)
          Dec 18 16:21:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service c-icap stopped. Restarting c-icap (ICAP Inteface for Squid and ClamAV integration)
          Dec 18 16:21:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service snort stopped. Restarting snort (Snort IDS/IPS Daemon)
          Dec 18 16:21:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver)
          Dec 18 16:22:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service clamd stopped. Restarting clamd (ClamAV Antivirus)
          Dec 18 16:22:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service squid stopped. Restarting squid (Squid Proxy Server Service)
          Dec 18 16:22:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service c-icap stopped. Restarting c-icap (ICAP Inteface for Squid and ClamAV integration)
          Dec 18 16:22:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service snort stopped. Restarting snort (Snort IDS/IPS Daemon)
          Dec 18 16:22:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver)
          Dec 18 16:23:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service clamd stopped. Restarting clamd (ClamAV Antivirus)
          Dec 18 16:23:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service squid stopped. Restarting squid (Squid Proxy Server Service)
          Dec 18 16:23:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service c-icap stopped. Restarting c-icap (ICAP Inteface for Squid and ClamAV integration)
          Dec 18 16:23:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service snort stopped. Restarting snort (Snort IDS/IPS Daemon)
          Dec 18 16:23:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver)
          Dec 18 16:24:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service clamd stopped. Restarting clamd (ClamAV Antivirus)
          Dec 18 16:24:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service squid stopped. Restarting squid (Squid Proxy Server Service)
          Dec 18 16:24:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service c-icap stopped. Restarting c-icap (ICAP Inteface for Squid and ClamAV integration)
          Dec 18 16:24:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service snort stopped. Restarting snort (Snort IDS/IPS Daemon)
          Dec 18 16:24:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service unbound stopped. Restarting unbound (DNS Resolver)
          Dec 18 16:25:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service clamd stopped. Restarting clamd (ClamAV Antivirus)
          Dec 18 16:25:00 pfSense php-cgi: servicewatchdog_cron.php: Service Watchdog detected service squid stopped. Restarting squid (Squid Proxy Server Service)
          
          

          I was hoping to get something like this, where they could see my report I submitted via my IP.

          https://pcpartpicker.com/b/YfXH99

          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by Dec 19, 2017, 3:34 AM

            No idea.  I generally don't even worry about reboots unless they are chronic.

            I have never had any computer of any kind that didn't reboot ever in 6 months or a years time.  It would be nice though.

            1 Reply Last reply Reply Quote 0
            • V
              Visseroth
              last edited by Dec 19, 2017, 5:37 AM

              Nice run time!
              Last machine I ran updates on had 102 days on it, but then had to reboot it for the update  :'(

              1 Reply Last reply Reply Quote 0
              6 out of 6
              • First post
                6/6
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received