Just want to say I resolved the issue for those who might be experiencing the same thing.

I deleted the limiters I had from before the upgrade, recreated them and it fixed the issue.

https://www.reddit.com/r/PFSENSE/comments/vqhbzw/psa_i_had_to_delete_and_recreate_traffic_limiters/
Apparently people had issues with bringing limiters through the upgrade.

Thank you all and @BBcan177 for the simple patch, because I was about to make a long post looking for help, and the little edit to line 4139 solved my CPU load issues with 22.05 completely.

I think this fix should be made more prominent - I am not using a 22.05 development snapshot, but rather 22.05 final, and I found this thread via a search and not via a browse of the forums. I feel lucky to have found it.

Leave a note on https://redmine.pfsense.org/issues/13228 that the fix works for you.

It's still something I plan on changing for the next release it just hasn't happened yet.

Thanks for the post. I have checked the repos and no third party - it seems like something went wrong with the install like netblues above. I do have squidguard installed.

In the end, I basically did what was described above (with some detail in case it helps someone else):

Connected WAN to a wifi hotspot (which was a little more painful than I hoped). This was helpful: https://www.youtube.com/watch?v=qRyXAFD94lI

Used pkg upgrade -y mpd5 in Diagnostics/Command Prompt to force the upgrade of the package

Confirmed upgraded with pkg info | grep mpd5

Changed WAN back to PPPoE connection

Hopefully this is a limited issue. Was a bit painful but learnt some stuff along the way so not all bad.

The permission denied error is from the NUT package trying to send notifications from an unprivileged user.

See https://redmine.pfsense.org/issues/12281

Those errors are almost certainly not related directly, but may be indirectly related. By that I mean some power/UPS event triggered those failed notifications -- that event may be the cause of your problem, not the notification errors.

@netblues said in Dashboard update widget always prompts for new version:

I have manually upgraded to ntopng Community v.5.3.220511
using the instructions found here in the forum.
Nothing else.
Could that cause all this havoc?

Yes, that is likely your whole problem. Don't do that.

@jimp said in unable to update 22.01 to 22.05rc:

ps uxawwd

I found these:

root 14248 0.0 0.0 11244 2496 0 S+ 09:48 0:00.00 | -- grep upgr root 50870 0.0 0.0 11704 3072 - I 14:45 0:00.00 |-- /bin/sh /usr/local/sbin/pfSense-upgrade -y -l /cf/conf/upgrade_log.txt -p /tmp/pfSense-upgrade.sock root 58743 0.0 0.0 10588 2068 - I 14:45 0:00.00 | -- /usr/bin/lockf -s -t 5 /tmp/pfSense-upgrade.lock /usr/local/libexec/pfSense-upgrade -y -l /cf/conf/upgrade_log.txt -p /tmp/pfSense-upgrade.sock
root 58811 0.0 0.0 12472 3356 - S 14:45 0:29.41 | -- /bin/sh /usr/local/libexec/pfSense-upgrade -y -l /cf/conf/upgrade_log.txt -p /tmp/pfSense-upgrade.sock root 39126 0.0 0.0 11164 2132 - I 14:46 0:00.00 | -- nc -lU /tmp/pfSense-upgrade.sock

I killed them and restarted the upgrade via GUI and it is now starting....

Thanks all!

Hmm, well that would be a lesser used feature. Let us know if it surfaces again.

That is possible. We have seen that a few times internally. Always because of internal build testing though. That should never happen against the public pkg repos.

Steve

@stephenw10 said in 22.05 snaps paused?:

So it doubled after running the upgrade and went back to the previous use after rebooting a second time?

Yes. I am just mentioning it again because there might be installations where this is troublesome? But from now on I will be silent about the RAM usage just after upgrading. In the end, RAM is there to be used anyway. 😉

It is. If you don't see the branch Next Stable Version (22.05 then first select the stable branch (22.01) and refresh. You should then see 22.05 offered as next which is 22.05-RC.

Steve

@jimp said in 22.05 - DCO and OpenVPN problems?:

It's not clear how that might have happened without seeing the upgrade log and console output. It could have been interrupted partway through, for example.

If you go to the console and try running pfSense-upgrade -d it may pick up and complete the remaining items. You may also be able to run pkg update -f; pkg upgrade -y which would update the remaining items that are out of date.

If you are running pfSense Plus software on Netgate hardware you can request installation media from TAC. If it's an installation you upgraded from CE to Plus you'd need to reinstall CE, upgrade to Plus 22.01, then upgrade to Plus 22.05 from there. Once 22.05 is officially released (and not an RC) then it will be possible to move from CE to Plus 22.05 directly.

@jimp You absolute gem. The "pfSense-upgrade -d" via console did the trick and everything booted up just right. About 13 packages was updated. I have no idea why they were left in limbo during the last update via the GUI.

@stephenw10
I can only confirm that no traps anymore. Thank you.

You are posting in the category for 22.05 development snapshots, which is intended to be for reporting issues found while running a 22.05 development snapshot.

The log issue is definitely fixed on 22.05, not sure about the other problem you mentioned but if you want to raise that issue I suggest you start a fresh thread in a more appropriate category and ask about it there.

@bnetworker Thank you!

@swixo Try changing your ACB time to happen 5-10 minutes after the hour, or do so only when there's a change to the system.

The default setting on ACB is every hour and it is often not migrated away from.

DCO is SHA256 only right now. When you enable it at either end it forces that bit if you have older clients with existing config it will then become mismatched.

Steve