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.
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.
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'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.
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.
@gabacho4 What happens when you set both Child SA actions to default and disconnect both sides, then on one side click the connect P1+P2 button in the UI. Do both P1/P2 come up or is it still only P1 that will show? Does the 22.05 side show other behavior then 22.01 with that button? Did you set ChildSA actions on both sides or only on one?
I found the issue, if anything is placed in the "bypass traffic for these destinations" it will disable WPAD, keep in mind I have Xbox one running on port 443 and 80 to anywhere however inverted to not let other devices work like this. This is what resolved this issue for me. All other static IP addresses can not use that port only 80 to the firewall.