Hangs after reboot after latest 2.0 RC1 upgrade (4/18)



  • I've been using 2.0 since January and have been upgrading it at least once a week without any issues until day.

    Today when i invoked the auto upgrade from the GUI everything seemed to go normal and then it went down to reboot.  After it didn't come back in a while, I connected the pfsense box to a monitor to see what was going on and saw it hung up after "exiting due to repeated, frequent failures".  These failures seem to all be related to trying to start squid, "squid[333]: Squid Parent: child process 379 started pid 379 (squid), uid 62: exited on signal 6".  So I tried rebooting it again and seeing what happens from the start.  Below is an overview of what's happening.

    Seems to boot up normally
    Then has repeated errors "exited on signal 6" for squid[333], then exits "due to repeated, frequent failures"
    Then has repeated errors "exited on signal 6" for squid[415], then exits "due to repeated, frequent failures"
    Then my one interface (bge0) link state changes to UP
    Then my other interface (re0) link state changes to UP
    Then when I hit enter I get the following error "Fatal error: Call to undefined function preg_match() in /etc/inc/interfaces.inc on line 3517"
    Then pfsense menu comes up

    I also tried rebooting and trying to started via safe mode, but that hangs with the following on the screen "IPsec: Initialized Security Association Processing."

    Any ideas on how to get around this?  Now the weird part is that I didn't even have squid running when I performed this latest upgrade.  I did have it active in the past, but I deactivated it a few weeks ago.

    I also have a backup config saved from about a month ago so it shouldn't be a huge deal for me to reinstall it from scratch and then just load that config, but I'd like to avoid that if possible.

    Any ideas or suggestions would be appreciated!

    Thanks!


  • Rebel Alliance Developer Netgate

    Not enough info there to say anything for sure. i386 or amd64? What was the exact snapshot time?

    I have a couple VMs running the latest snapshot and haven't had any problems myself.



  • It's on an amd64.  As for the snapshot time, I'm not exactly sure. It would have been whatever the latest was that was available around 8 EDT on 4/18 since that's around the time I did the upgrade from the GUI.  It was a build from earlier that day (11am or 1pm maybe).

    One other thing I forgot to mention was that just before doing the upgrade I just started having it report to a syslog server.  That was the first time I tried upgrading since activating the syslog server.

    @jimp:

    Not enough info there to say anything for sure. i386 or amd64? What was the exact snapshot time?

    I have a couple VMs running the latest snapshot and haven't had any problems myself.


Locked