NG 1100 23.05 to 23.09 upgrade problem/question
Hello - today I upgraded my NG 1100 from 23.05.1 to 23.09. I think.
I followed the documented procedures: backup, removing packages, reboot, install upgrade.
Everything went pretty much normal, except for this: the dashboard says I'm still on 23.05, but when I click on Upgrade, it says I'm on 23.09, the current release.
I tried a reboot again, same result.
How can I be sure what version I'm on, when one screen (dashboard) says I'm not upgrade, but another (upgrade) says I am?
At the command line run:
pkg-static info -x pfSense
See which pkgs are still running 23.05.1.
In most cases you should be able to just run:
pkg-static upgradeand agree to the available upgrades. But be sure to have a backup of your config in case you have to install 23.09 clean.
@stephenw10 I have the same issue after upgrading from 23.05 (not .1) to 23.09. The update process looked normal and it ended with success.
Dash says this:
built on Mon May 22 15:04:36 UTC 2023
Version 23.09 is available.
Version information updated at Sat Dec 2 23:59:29 CET 2023
When I check your query at the command prompt I get this:
pfSense-23.05 pfSense-Status_Monitoring-php82-1.8_3 pfSense-base-23.09 pfSense-boot-23.09 pfSense-default-config-serial-23.05 pfSense-kernel-pfSense-23.09 pfSense-pkg-Avahi-2.2_4 pfSense-pkg-Service_Watchdog-1.8.7_1 pfSense-pkg-aws-wizard-0.10 pfSense-pkg-ipsec-profile-wizard-1.1_1 pfSense-pkg-openvpn-client-export-1.9_1 pfSense-pkg-pfBlockerNG-devel-3.2.0_6 pfSense-repo-23.05 pfSense-repoc-20230912 pfSense-u-boot-1100-20220428 pfSense-u-boot-2100-20210930_1 pfSense-u-boot-env-20230123 pfSense-upgrade-1.2.1 php82-pfSense-module-0.95
Ok so we have seen that a few times and most people who hit that were able to complete the upgrade by running
pkg-static upgradeand then agreeing to the offered upgrades. Do that at the real command line not via the gui command prompt. Be sure to have a backup of the config though in case you need to reinstall.
@stephenw10 Thank you. When you say "the real command line" do you mean connecting to the device via the console port (USB cable)?
Or SSH. If using Diagnostics/Command Line one can't respond to prompts so the process hangs.
Ah okay. So I could in fact do it over VPN using SSH? It's a remote site that takes an hour to drive.
Yes, you can but you should have a fall back solution if it fails to upgrade for some reason.
@stephenw10 I hear you and thanks for the warning. Well I suppose the unit will just chug along as is until I get on site again so I’ll just wait.
What does look fascinating is that some components (base, boot, kernel) appear to be on 23.09 while the system itself is on 23.05.
Yes exactly it has partially upgraded. Those components are updated before the first reboot at upgrade. It then boots into the new kernel and updates all the other packages. In this case it failed to complete the second part of that for some reason. It may be logged in /conf/upgrade_log.latest.txt
Usually just kicking the pkg upgrade again completes it.
@stephenw10 Thanks for that.
I just updated my SG-2100 main production unit to 23.09.1. See this topic where I report high RAM usage after the update.
If the 23.09.x is indeed RAM hungry, how is it even possible to run 23.09.x on the SG-1100 with 1GB RAM?
Edit: nevermind. On my 2100 it got back to 16% after a second reboot.
Yup it uses significant memory to run the upgrade. That will be freed eventually or if needed but as you found a reboot after upgrade will also free it.