Upgrade Wierdness going from 2.3.4 Release to 2.4.2



  • Now this is strange… went to upgrade my SG-4860 ADI_RCCVE to 2.4.2 through the WebConfigurator and started off looking as if all was going well. The messages included: "Update Successful" and "Kernel updated" however after the reboot the version in the dashboard is still showing 2.3.4-Release-P1 but also showing Free BSD 11.1-Release-P4. Seems like the kernel and the free BSD version updated but somehow not pfsense itself - Is that possible? Would very much appreciate some guidance on this or if anyone else ran into this how did you fix it?

    Version 2.3.4-RELEASE-p1 (amd64)
    built on Fri Jul 14 14:56:00 CDT 2017
    FreeBSD 11.1-RELEASE-p4

    The system is on the latest version.

    Other things I tried:
    Before i started I uninstalled the few packages I had
    Rebooted the SG-4860 a second time - Post ugrade
    Cleared all cache and cookies and opened a fresh browser
    Checked my system logs but most if not all upgrade related entries had already been overwritten
    Logging into the GUI from a different PC (- didn't really expect that to clear anything up)

    The system seems to be working OK in other respects but short of a fresh install what else can done to fix this?



  • No known way for me fix this failed upgrade! FreeBSD showing 11.1 but still showing 2.3.4-Release-P1 as the current version/"up-to-date". I later noticed that all F/W logging had stopped so at that point the only solution was to just reinstall. I had 2.4.0 ready to go on a thumb-drive and then upgraded to 2.4.2 through the console and restored my configuration from backup. All looks fine now and happy with what appears to be a noticeably faster VPN.



  • Hey, at least it took your configuration file.

    I upgraded (from 2.3.4.p1) via the GUI and it never came back. Went to the machine and found the console barfing up PHP errors, missing files, etc, and showing about half the console choices, most of which didn't work anyway. The GUI never came up at all.

    took another backup of the config file, installed 2.4.2 from USB with the "recover a config file" option, barfed again.

    Tried installing 2.3.5 instead, in case it would be happier with my config file - installed fine, booted OK, retsored the config file through the GUI, barf-city, just like before.

    tried installing again, restoring only parts of the config info, but some parts of the config info I need seem not to be "restorable" other than by tedious cut and paste from a text editor in the xml file. The freeradius2 package was removed, and when I load freeradius3, (which has to be after the upgrade to 2.4.2 due to the package system) I still don't have the option of restoring those settings. Restoring the traffic shaper settings did not restore the limiters. Certificates are all messed up. But guaranteed, if I restore the whole settings file the machine will barf on boot, must have done that 5 times in different ways. Hours wasted, more to be wasted…

    Not a particularly delightful upgrade process. I've been at this since the early 2.0x releases at least, and while some of the upgrades have been not better than what they were "upgrades" from, none have blown up in my face quite like this.



  • @MainSail:

    No known way for me fix this failed upgrade! FreeBSD showing 11.1 but still showing 2.3.4-Release-P1 as the current version/"up-to-date". I later noticed that all F/W logging had stopped so at that point the only solution was to just reinstall. I had 2.4.0 ready to go on a thumb-drive and then upgraded to 2.4.2 through the console and restored my configuration from backup. All looks fine now and happy with what appears to be a noticeably faster VPN.

    If someone else have this issue, backup your config and try this -
    https://forum.pfsense.org/index.php?topic=135582.msg742380#msg742380


Log in to reply