System Information | Version Status
-
I just updated to 22.05-RELEASE (amd64) and the System Information widget continues to tell me Version 22.05 is available.
System / Update / System Update screen Status shows Up to date.
-
@tac57 Someone else just posted that as well:
https://forum.netgate.com/topic/173097/netgate-6100-version-upgrade-problem-22-05-release -
If it still shows that, then part of your upgrade did not complete properly.
We have seen similar things happen for as few different reasons but no one thing has stood out as being the most common yet and though we've had a handful of reports it still only seems to affect a small number of users total.
- Some users have manually defined third party package repositories and some packages in those repositories are outdated or conflict (ntop seems to be a common problem here) -- removing the alternate repositories and re-running the upgrade from the CLI with
pfSense-upgrade
should fix this. - A package, such as squidGuard, gets hung up during the upgrade and prevents it from fully completing. -- Stopping the package service (e.g. squidGuard) manually from Status > Services should allow the remainder of the upgrade to complete, alternately, from the CLI run
killall -9 pkg
and see if it continues. Otherwise, reboot and re-run the upgrade from the CLI withpfSense-upgrade
. - Systems with multiple disks that had installations on both (e.g. device shipped with MMC but later added an SSD) may be booting from the MMC but upgrading the OS on the SSD. There are a couple different potential methods for working around this but they can be more potentially dangerous, but tl;dr is you need to erase the MMC so the SSD install can work completely.
- Something else interrupted the upgrade, such as a user pulling the plug while it was still working because they felt it was taking longer than expected. In this case, re-running the upgrade may help, but a reinstall is better.
- Some users have manually defined third party package repositories and some packages in those repositories are outdated or conflict (ntop seems to be a common problem here) -- removing the alternate repositories and re-running the upgrade from the CLI with
-
@tac57 Got same problem. Contacted support and got the right answer: from pfSense CLI run " pfSense-upgrade -d". Did fix issue in mine.
-
@jimp I ran 'pfSens-upgrade' from the Shell and the world is now safe!
Other than something in item #1, none of the other issues should have been a problem on my system. Here is what I have installed.