pfSense 2.4.5-RELEASE-p1 Now Available
-
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.