pfSense 2.4.5-RELEASE-p1 Now Available

mcury

Upgraded successfully a SG-3100 from 2.4.5 to 2.4.5-p1.
Thanks pfsense team, everything working.

johnsa

Upgraded successfully to 2.4.5-RELEASE-p1 (amd64). So far working fine.
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz

jimp

@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?

Cool_Corona

@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.

Cool_Corona

That worked

johnpoz

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!!!

DaddyGo

Problem free (2.4.5-RELEASE-p1)
Supermicro Epyc 3151
APU4d4

THX

wickeren

Updated on two instances, one VPS (KVM) and one physical machine, booth went smooth and seem to work fine.

NOCling

SG-3100 all fine, reboot 2min
SG-1100 all fine, reboot 5min

Good job, thanks!

costanzo

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

@costanzo Update completed. Took a while, but is back online and reporting it has been upgraded.

Yamabushi

Smooth upgrade here as well on a Super Micro C2758. Thank you!

Mr_JinX

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.

revengineer

Upgrade went smooth, all seems to be well. Thank you!

whoami TM

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.

bimmerdriver

Updated my windows 2019 hyper-v server from 2.4.5 and there were no problems at all.

emammadov

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.

fireodo

Update from 2.4.5. to 2.4.5_p1 went smooth and without issues here.

A Former User

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

hpxca

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.