@stephenw10 said in 24.0 Goes GA...:

Yes the patch version there doesn't change the displayed version after the update.

You can check the pkg version:

[24.03-RELEASE][root@4100-3.stevew.lan]/root: pkg info pfSense pfSense-24.03_1 Name : pfSense Version : 24.03_1 Installed on : Wed Apr 24 19:46:04 2024 BST Origin : security/pfSense

I’m going to start uninstalling Suricata and pfBlockerNG from now on for any subsequent upgrades. It’s still taking about 10 minutes to timeout on my 6100 MAX which started with the first RC release. Not a big deal and at least we know what’s happening now!

@graphene Details for a System Patch can be found here: https://forum.netgate.com/post/1164566

Interesting that it's been around that long and hadn't been removed/cleaned up.

The code should absolutely handle that situation better, though. I opened https://redmine.pfsense.org/issues/15423 so we can address that for the next release.

Hmm, interesting. Where it stops there is at the EFI framebuffer which is something I'd only expect when it boots UEFI.

@johnpoz epic I bet squid 6 supports it too

Yes it's possible it's now working correctly and was broken before. There have been a bunch of fixes in pf that might have done that, potentially.

@marcosm After Release I'll do a new install from scratch and test again. Seems like a minor/non-issue otherwise.

@mikey_s Check if you have the same error msg (unbound) in the system log as in the first post of this thread 24.03-BETA to 24.03-RC update hiccup. Unbound did not start => DNS not working.

I too had to reboot once more after the update reboot.

Yup unclear why the hostname is initially omitted but it's only temporary and really only cosmetic.

So this was fixed in the Beta and obviously carried over to the RC. It never showed up for me prior to the Beta. Thank you for taking your time to explain this. I appreciate it.

@jaltman Hit this issue today, different BE. Destroy did the trick.

Thanks!
Ted

@marcosm re-added the first screenshot which was gone.

Because in the new ZFS/BE upgrade system all the packages are installed/updated into the new BE before rebooting. That reduces the down time significantly for most installs. But it does mean that packages with installs scripts end up being run differently as we've seen. There's a good chance this can be patched before 24.07 IMO.

@DefenderLLC Sorry mis-quoted/referenced your post with the OPs. It was such a week ;)

It's fixed in the updated pfSense-upgrade package (1.2.20). https://redmine.pfsense.org/issues/15407

@JonathanLee said in Squid 6.6 DEV 24 Issues:

@stephenw10

A lot of my images for posts got deleted as of today is something else going on with the website?

The images are back now...

Great, thanks. Had one report of a reboot failure on an 1100 but I'd guess it was the specific UPS configured.

Ok, looks like it logs only critical errors.