Unable to Upgrade Again to 22.05
-
The original upgrade to 22.05 caused a very high CPU load, to avoid further overheating of the system we used ZFS Boot Environments to revert back to 22.01. The system now runs stable again, all packages are working but there are some issues:
-
The dashboard now shows that there are no packages installed:
-
An upgrade back to 22.05 isn't possible anymore. Neither in the GUI:
Nor in the CLI:
Has anyone experienced the same issue? And is there a way to correct this situation?
-
-
@kuschi What output do you get from
pkg-static info -x pfSense-upgrade -
[22.01-RELEASE][admin@LabServer.mgk.lab]/root: pkg-static info -x pfSense-upgrade
pkg-static: No package(s) matching pfSense-upgradeOr did I do something incorrect?
-
@kuschi I've seen this happen from time to time on systems.
Is this a Netgate device or a whitebox CE install that was upgraded to Plus?
-
It happened on my lab device, an AMD GX-412TC SOC-powered system from PC Engine, as well as on my "whitebox CE install that was upgraded to Plus". I.e. it is not a one-off issue, I believe.
-
@kuschi All I can direct you to is here: https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html
Typically I would recommend a reinstallation - however in the CE->Plus world that means 2.6->22.01->22.05, there is no direct reinstallation option for CE->Plus at this time (nor a 2.6->22.05 path)
-
At the moment I would anyway hold off from upgrading to 22.05. Do I have to purchase token(s) again or can I use the existing ones I have for the Plus upgrade?
-
@kuschi Once you have a token it is good for the life of either associated TAC Subscription (Pro or Enterprise) or indefinitely (Home/Lab) as I understand it.
The only thing that will invalidate the token automatically is changing of the NDI - adding or removing NICs is the most likely cause of an NDI change.
Reinstalling 2.6CE should not change the NDI unless you've already had it change on you.
Exception: building a new VM would cause new NICs, reusing a VM would not. -
Thanks. I should be safe, they are still the same physical boxes.
However, how can I find out what caused the high CPU usage? As packages, next to some other minor packages, I have pfBlockerNG and Suricata in use. I read that pfBlockerNG may cause issues after the upgrade but in diagnostics, I could only identify the kernel{if_io_tqg_x}] process was very high.
-
@kuschi There's a known issue with pfBlockerNG and they have a patch. Check out the Forum channel or Subreddit
-
I am unable to upgrade from 22.01 to 22.05 on my SG5100. As the lyrics in Proud Mary say, "big wheel keeps on turning" yet no update. It appears to be stuck in a loop. Any suggestions?
-
@munson In these cases we'd generally suggest opening a ticket and requesting the current release image, back up your config, restore from the new image and then import your config backup.
See the URL in my signature to open a ticket.
-
@rcoleman-netgate weird, after 90-120 minutes the upgrade completed. Initial testing seemed to work. Thank you.
-
@rcoleman-netgate
Good morning,Isn't it a general bug that you can use the newly implemented ZFS snap-shot feature in 22.05 to revert back to 22.01 but cannot come back because the menu in 22.01 is missing? I.e. switch back to "default"? Respectively, the kernel is still 22.05 and now the system is "confused"?
-
@rcoleman-netgate
Now, this is somewhat of a disaster. I was able to reinstall to 2.60 and recover my configuration. However, now I cannot upgrade back to 22.01:
Activation is not possible either. Apparently, the my device is already recognized:
Any ideas anyone?
-