Cannot open web interface after applying latest update from console



  • Hi.

    I applied the latest update from console, I also upgraded the APU (4D) bios to the latest found at manufacturers site ( FW Sept 8 2014 )

    This screenshot is what i get when I go to the web interface, otherwise the pfsense does boot just no web UI.

    It worked before the upgrade, not sure what those things mean in console.

    This is a full install on an SLC SD card not nanoBSD.

    ![Screenshot 2015-01-22 01.40.31.png](/public/imported_attachments/1/Screenshot 2015-01-22 01.40.31.png)
    ![Screenshot 2015-01-22 01.40.31.png_thumb](/public/imported_attachments/1/Screenshot 2015-01-22 01.40.31.png_thumb)



  • Also … just tried to do a factory reset, still nogo. Getting some error on top and when i try to access the webpage i get same error in console.

    ![Screenshot 2015-01-22 01.55.56.png_thumb](/public/imported_attachments/1/Screenshot 2015-01-22 01.55.56.png_thumb)
    ![Screenshot 2015-01-22 01.55.56.png](/public/imported_attachments/1/Screenshot 2015-01-22 01.55.56.png)



  • okay so i just re-imaged the SD card to a fresh install, and then upgraded again and it works fine.

    The only thing i can assume now is because i kept unplugging the router form the power the filesystem got corrupt.

    So here comes the next question … how can i prevent the Pfsense filesystem getting corrupt when the power goes out besides connecting the pfsense router to a UPS with a "graceful shutdown script" ...

    Does the nanobsd version prevent that versus the full install ? or it doesn't matter  ?



  • The nanoBSD version has the file systems on the SD card mount read-only by default. They only get switched to RW when a config change is made, then switched straight back. So in normal operation there can't be outstanding writes to the SD card. So random power failures should not corrupt anything.
    /var and /tmp are memory disks and recreated completely from scratch at boot - so no problem losing those on power fail.
    I can't imagine why you would not use nanoBSD on an APU with SD card.



  • @phil.davis:

    The nanoBSD version has the file systems on the SD card mount read-only by default. They only get switched to RW when a config change is made, then switched straight back. So in normal operation there can't be outstanding writes to the SD card. So random power failures should not corrupt anything.
    /var and /tmp are memory disks and recreated completely from scratch at boot - so no problem losing those on power fail.
    I can't imagine why you would not use nanoBSD on an APU with SD card.

    Okay that is a good explanation. I was just trying to hack because i heard some "packages" were not supported under nanoBSD, but I rather have a safe router than some extra packages to be honest.

    Thanks !



  • Packages that are not supported on nanoBSD are generally ones that would need to do a lot of writing to disk. nanoBSD is typically used for CF or CD card installs, where a lot of writing is not such a great idea.



  • You have squid3 installed? The hacks some people were using, and/or a bug in the package, were causing some services to fail (which is the root cause there, PHP is failing).

    If you have been messing with squid3 on it, especially if any changes were made at the command line as a number of people had done to work around things at the time, you're best off reinstalling the latest snapshot and restoring your config (even if it contains squid3, it shouldn't have those issues anymore).



  • @cmb:

    You have squid3 installed? The hacks some people were using, and/or a bug in the package, were causing some services to fail (which is the root cause there, PHP is failing).

    If you have been messing with squid3 on it, especially if any changes were made at the command line as a number of people had done to work around things at the time, you're best off reinstalling the latest snapshot and restoring your config (even if it contains squid3, it shouldn't have those issues anymore).

    no i didn't have any packages installed, i think that i just corrupted the FS by starting and unplugging the router too much ( i was testing a serial port over IP redirector device so i was constantly unplugging ).

    I might be right, or i might be wrong … I guess we will see if anybody else reports issues in future.



  • It's highly unlikely a power failure would result in any damage (unless it happened in the middle of an upgrade). We've always pulled the plug on all our dev/test systems routinely, and put systems on a power on/off timer that cycled its power every 5 minutes for days to weeks. Never broke anything. There are rare circumstances where the system kernel panics and corrupts files, which could be the cause if you got a crash report notification after login.



  • hmm… maybe it was a bug after all ... one thing i do remember, the first time i tried to update it went very quick, so i was worried and did another update after that, to make sure it didn't corrupt anything.

    Besides squid not working, what are the other disadvantages of running nanobsd ? Like i said I had SLC SD cards so i'm not worried about limited write cycles.


Log in to reply