pfSense 2.4.5-RELEASE-p1 Now Available
-
Netgate is pleased to announce the release of pfSense software version 2.4.5-p1, now available for new installations and upgrades!
pfSense software version 2.4.5-p1 is a maintenance release that brings several important stability and bug fixes for issues present in pfSense 2.4.5-RELEASE. pfSense 2.4.5-RELEASE-p1 updates and installation images are available now! To see a complete detailed list of changes, see the Release Notes.
Always take a backup of the firewall configuration prior to any major change to the firewall, such as an upgrade.
Do not update packages before upgrading pfSense! Either remove all packages or do not update packages before running the upgrade.
The upgrade will take several minutes to complete. The exact time varies based on download speed, hardware speed, and other factors such as installed packages. Be patient during the upgrade and allow the firewall enough time to complete the entire process. After the update packages finish downloading it could take 10-20 minutes or more until the upgrade process ends. The firewall may reboot several times during the upgrade process. Monitor the upgrade from the firewall console for the most accurate view. If the update check fails, or the update does not complete, run 'pkg install -y pfSense-upgrade' to ensure that 'pfSense-upgrade' is present.
Consult the Upgrade Guide for additional information about performing upgrades to pfSense software.
-
I hope its good, this time.
-
Updated and all went fine.
Except I cant enable more than 1 CPU in VmWare....
Currently running 16 cores and only 1 is showing.
I have deleted the kernel.smp.disabled in system tunables.
-
Upgraded successfully a SG-3100 from 2.4.5 to 2.4.5-p1.
Thanks pfsense team, everything working. -
Upgraded successfully to 2.4.5-RELEASE-p1 (amd64). So far working fine.
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz -
@Cool_Corona said in pfSense 2.4.5-RELEASE-p1 Now Available:
I have deleted the kernel.smp.disabled in system tunables.
Did you reboot after changing that?
-
@jimp said in pfSense 2.4.5-RELEASE-p1 Now Available:
@Cool_Corona said in pfSense 2.4.5-RELEASE-p1 Now Available:
I have deleted the kernel.smp.disabled in system tunables.
Did you reboot after changing that?
Yes. I had to remove it manually from boot/loader.conf.
Currently rebooting and I will let you know in 2 minutes how it goes.
-
That worked
-
Just upgraded my sg4860 to p1, went very smooth... My wife didn't even loose her picture on the show she is watching off my plex that pfsense routes between the vlans.. Must of had enough buffered to last through the upgrade - nice ;)
As typical smooth easy update process.. thanks!!!
-
Problem free (2.4.5-RELEASE-p1)
Supermicro Epyc 3151
APU4d4THX
-
Updated on two instances, one VPS (KVM) and one physical machine, booth went smooth and seem to work fine.
-
SG-3100 all fine, reboot 2min
SG-1100 all fine, reboot 5minGood job, thanks!
-
FYI - SG-1100 Sitting on "Please wait while the update system initializes" for over 10 minutes.
Will continue to wait. Still have active internet.
-
@costanzo Update completed. Took a while, but is back online and reporting it has been upgraded.
-
Smooth upgrade here as well on a Super Micro C2758. Thank you!
-
The update seems to go well, the only issue i have found is updating the service watchdog package, which sits on "Please wait while the update system initializes" on a number of my boxes. Other packages seem to be updating okay.
-
Upgrade went smooth, all seems to be well. Thank you!
-
Smooth upgrade on SG-4860-1U.
Only issue I had was DNS Resolver didn't start on its own but I could've been my config. -
Updated my windows 2019 hyper-v server from 2.4.5 and there were no problems at all.
-
I just upgraded from 2.4.4.p3 to 2.4.5 p1. It took a long time but it working okay so far. I noticed that ram usage is high than before.
-
Update from 2.4.5. to 2.4.5_p1 went smooth and without issues here.
-
Hi
Updated all okay on PC Engines APU2 from 2.4.5 to 2.4.5p1. Wasn't having issues before and all seems good on the new version. However memory usage went from 25% to 35% after the upgrade although that might be due to the upgrade processes still hanging around so will reboot when I'm not going to disturb others.
Regards
Phil
-
I updated a XG-7100 from 2.4.5 to 2.4.5-p1. The only issue I observed was that the pfSense-coreboot package said it got upgraded during the update, but after the update the package still showed it was the old version. Attempts to update it post-update hung at "Please wait while the update system initializes". This issue is quite similar to the one Mr_JinX reported in this thread. On the CLI I found a seemingly hung instance of pfSense-upgrade running.
I let it run for more then an hour and it never completed whatever it was doing, but the firewall was otherwise working fine. I killed it and tried the package upgrade again and it worked normally.
I suspect this problem might be related to the way our firewall comes up. We are using FRR and OSPF on the WAN side of this device, and after the boot is completed and the LAN side is reachable, it takes ~30 sec or so for OSPF to come up and the device to have internet access on the WAN side of things.
-
@hpxca said in pfSense 2.4.5-RELEASE-p1 Now Available:
I suspect this problem might be related to the way our firewall comes up. We are using FRR [...]
It's possible the package upgrade was hung up by this: https://redmine.pfsense.org/issues/10610
-
Hi
Replying to my own post. I've now been able to reboot after the upgrade and memory usage back to 25%, so it seems after an upgrade where it restarts and extracts and install packages that leaves some extra stuff in memory until another reboot.
So if anyone sees more memory used after the upgrade, just reboot to get a clean start.
Regards
Phil
-
No problem on custom router (QOTOM-Q355G4) tool under 5 min
Great job thx ! -
@jimp No frr package installed here, but the package manager gets stuck nearly after every package update. It's a mess as it needs a reboot every time to get out of this.
-
@jacotec Same issue here. Thought I messed up and restored a config. Package reinstallation is completely fubared. This is the second time I fell for the quick upgrade. Will never do that again.
-
Any command to restart the stuck PM process or a workaround would be great to avoid a full reboot (which brings a lot of stuff down)
-
Just tried complete reinstall. Upon restoring config from GUI, pkg-static is hanging during install of squid. I will let it sit, nothing I can do before someone more knowledgeable than I responds.
-
Not sure if this is the place to post this, but it might be related to the upgrade.
After upgrading to 2.4.5-p1 successfully, I found three packages needing updates.
haproxy-devel updated successfully; however, two didn't
Both Snort and pfBlockerNG-devel. I restarted the SG-1100 and tried again. Was eventually successful after retrying.
Again, not sure if this is related to the 2.4.5-p1 upgrade or the package upgrade. Thought I would post that info hear incase other's had similar issues.
-
I also upgraded pfBlockerNG-devel, cron and snort after 2.4.5 p1 without any problems and very quickly
-
@revengineer said in pfSense 2.4.5-RELEASE-p1 Now Available:
Just tried complete reinstall. Upon restoring config from GUI, pkg-static is hanging during install of squid. I will let it sit, nothing I can do before someone more knowledgeable than I responds.
I fixed this by issuing command "killall pkg-static" after giving each affected package ample time to install. It turns out the packages are installed, the pkg-static command just does not exit. Everything is working again but something is not right here.
-
@chudak Thanks! Are you using a SG-1100 by chance? SG-1100 is a great deice, but I am wondering if its limited memory play in to updates.
My issue got resolved after rebooting and retrying, so I am all set.
-
@costanzo said in pfSense 2.4.5-RELEASE-p1 Now Available:
@chudak Thanks! Are you using a SG-1100 by chance? SG-1100 is a great deice, but I am wondering if its limited memory play in to updates.
My issue got resolved after rebooting and retrying, so I am all set.
No as I mentioned above ‘ custom router (QOTOM-Q355G4)’
-
Hello!
I upgraded several routers yesterday to 2.4.5.1 - a variety of sg-1100's, sg-3100's, and oddballs. All had extra packages installed (snort, pfb, cron, etc...) that the main upgrade screen said were being upgraded.
On the first router, after the upgrade completed, I went to the Package Manager and noticed that packages were still listed as needing upgrades. After clicking on one of the update package links I got the "Please wait while the update system initializes" message.
I discovered that, at least in my case, you do not need to manually install the package updates.
Once my router rebooted from the main upgrade, it started installing package upgrades in the background. There was no indication that it was doing this other than tailing the system log. It eventually completed the background package updates and all was fine.
I verified this on subsequent router upgrades. The lesson for me was to wait a good 10-15 minutes after the initial reboot to let the packages upgrade in the background while also checking the system log. After waiting, the Package Manager correctly showed no upgrades required.
In general, the upgrade process was rock solid. I did a few remote long distance upgrades last as wasnt even nervous....okay, maybe just a little... :)
John
-
@revengineer said in pfSense 2.4.5-RELEASE-p1 Now Available:
killall pkg-static
That indeed gets the stuck process out of jail and you can retry to update one by one without rebooting the whole box.
But the package manager definitely has a problem in 2.4.5p1!
-
Just did the upgrade 2.4.5 to 2.4.5-p1 for my home pfSense.
This also automatically triggered pfBlockerNG-devel upgrade 2.2.5_32 > 2.2.5_33
Smooth as silk, took about 5 Minutes total, thanks Netgate /pfSense team!-Rico
-
I had an Openvpn client from pfsense to PIA a few months ago, but I removed it yesterday.
Removed it completely, deleted the gateway, removed the interface, nat rules, certificate, everything related to that VPN connection.
I was checking my xml configuration file, and noticed that the dnsgw3 and dnsgw4 were still pointing to the PIA gateway.
Searched, and it seems that this is related to Bug #8922 (https://redmine.pfsense.org/issues/8922)
I've fixed by manually editing the XML file, and now it seems that everything is properly removed.
-
re: upgrading with packages installed:
https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide.html#packages
