So 24.03_1 already
-
Yep, this is not a good "experience" although nothing gets destroyed either.
The Web-UI tells me that this new _1 Update failed, so without rebooting I did it again, with the same outcome. Then I saw it had created a new boot environment already a second time. But this boot environment is only temporary...
After rebooting into it I changed it manually to be also the next boot environment.
Next I will rename it and delete the others.
-
@Bob-Dig said in So 24.03_1 already:
this is not a good "experience"
Agreed.
the 24.03 upgrade although appearing to go with no errors did not become stable until 3 reboots later, with plenty of time and coffee between each. On the third reboot it finally gave a message about verify (confirm) or whatever the actual message reads at the top of the dashboard.
after 24.03_1 - the DNS Resolver service failed to start. let it sit for 20 minutes or so before attempting to restart it manually. Nope. So I rebooted again. System came up again and everything now appears to be running.
Seems the entire update was pushed before being ready - again. Interesting that new boot environments are so much bigger and that 24.03_1 isn't really a .1, it is just the stuff that got missed in the first package.. Much like the items that got slipstreamed into 23.09 early in the release.
The only issue I'm left with is a let's encrypt certificate that is used on many systems without issue. Curl, used in pfblocker to pull some files from another internal server seems unable to locate the certificate in the local CA cert
- curl/cert works perfectly from other systems - just not the Netgate.
oh and the dashboard widgets, if collapsed show two + signs vs. the wrench and + when expanded. just a minor detail.
-
Hmm, confirmed the collapsed dashboard widget icon issue.
-
Hello. I upgraded to 24-03_1 however after upgrade is complete and at the reboot stage nothing happens. everything is up but i can't log in to GUI.
If I powered it off / on. will this cause any problems ?
It's been like this for about 20+ minutes now.
-
Read the changelog about State creation.
-
@NOCling I powered cycled it. The version is 24.03. and it is not showing 24.03_1 as an available update.
-
@mhijazi The _1 is only relevant for 64 bit ARM devices, so the 1100/2100: https://docs.netgate.com/pfsense/en/latest/releases/24-03.html#minor-revision so you can ignore it unless that’s the case.
-
Yes, you can just run
pkg upgradeto reach 24.03_1 from 24.03 if you are running x86 hardware. -
If there is a arm64 device it will show it up in the update tab, as available but not
the amd64 ones, only over console you will see it, and later I mean after the
update I saw also not on the WebGui, in System > Update and in the boot
environment name should be after update ...1738, but it isn´t, it is only
shown in the console (8) over the shell.[24.03-RELEASE][root@xxx.xxx]/root: pkg info pfSense pfSense-24.03_1 Name : pfSense Version : 24.03_1 Installed on : Wed Apr 24 20:57:08 2024 CEST Origin : security/pfSense Architecture : FreeBSD:15:amd64 Prefix : /usr/local Categories : security kld -
Unfortunately it will still show up for adm64 devices even though it is a no-op there. That's why you can just
pkg upgradeto it though. -
Looks like it was upgraded but will not show in GUI. from console it is showing the correct version:
pfSense-24.03_1
Name : pfSense
Version : 24.03_1
Installed on : Sun Apr 28 11:30:46 2024 +03
Origin : security/pfSense
Architecture : FreeBSD:15:aarch64
Prefix : /usr/local
Categories : security kldFYI my device is netgate 2100
thanks @Dobby_
-
Yes the dashboard will still show as 24.03 but it will no longer show 24.03_1 available. You can check the pkg version:
pkg info pfSensethat will show 24.03_1 is installed. -
@mhijazi said in So 24.03_1 already:
FYI my device is netgate 2100
System > Update and look there, it should be shown there then if you have
a aarch64 (arm) based device. -
I will try to uninstall and then install it via "pkg upgrade" again.
