Oh actually it could just be a dns issue. Try: host pkg01-atx.netgate.com

If that fails make sure Unbound is running or you have other DNS servers entered.

@stephenw10 said in Question about upgrade pfsense HA:

Ah, between different base versions that would be an issue, yes. And that does apply here.

Either way some time ago it used to be an issue and you needed to disable sync before upgrading. In any recent version though sync is disabled between incompatible versions so there is no need to do it.

hi,
Is it possible to see the status of this option, or is it in the pfSense code?

@stephenw10
Thanks Steve! I have updated and installed the packages. The error is gone. 👍

@lmoure said in after recent update:

plus-RELENG_23_05_1

Doesn't seem like it updated. Your fastest way back is probably to reinstall and restore your config file from backup. Is that a 3100?

https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/reinstall-pfsense.html
(free ticket for image)

@rb625 there was a bug in the package. :(
https://redmine.pfsense.org/issues/14596
https://redmine.pfsense.org/issues/14806

Short answer, click Save in the FreeRadius page even if you don't change anything.

@kasteensma It's a free ticket:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

You should be able to upgrade directly to 2.7.2.

@dwpace

Save yourself time and effort, gain on security.
Get yourself a fresh copy of pfSense.
You'll be skipping a lot of versions, as it's "2.7.2" now.

So. get the ISO.
In the current VM, export the config.xml file.
Shut down the VM.
Get a new VM, assign interfaces, have it boot from the ISO, and as soon as it starts and the GUI is usable, import the saved config.xml.
Let it 'cook' for a while (it will installed packages, if you had any).
Do a reboot when done.

Now, visit all the screens, check settings, take your time. You probably have same catch up to do.

@dwpace said in Upgrade not avaliable VIA gui, shell reports: ERROR: It was not possible to indentify which pfSense Kernel is installed:

but without any clear resolution

There's one, and its universal : don't stay on old versions very long, as pfSense isn't your coffee machine that isn't connected to the "dangerous" internet.

The forum is loaded with "how to get from "2.7.1 to 2.7.2" or, for that matter, how to get "2.4.5 to 2.4.5-P1" - look way back in the past forum history.
The "how to get from 2.4.5 to 2.7.2" : congratulation : you're the first 👍 That's new territory.

thanks @SteveITS, after some more troubleshooting & research found this resolved the issue - https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#repository-metadata-version-errors

@iorx

Hi again! Check the forum, though my install was unique...

This we're talking about, the remedy to a successful upgrade?
https://forum.netgate.com/topic/184661/unable-to-upgrade-from-2-7-1-to-2-7-2-unmounting-boot-efi-done-failed

Send me your NDI in chat and I'll check it. Repoc failing like that is a problem.

Steve

@reberhar So Steve, I have a question.

We use Comcast which frequently has significant latency. During the latency times I note that DNS requests backup, causing latency reports because dpinger requests get lost in the pile. Buffer bloat, of course can be a problem. I have read articles about that mentioning that our desire to maintain network requests in a linear fashion might sometimes be misplaced.

So I use priq on my shaper. Is there someway to make that queue smaller? I do note that at the time of the recent problems there is no signficant latency reflected in the gui on the WAN. The logs do reflect very recent latency however. This doesn´t seem like it can be the problem because localhost is resolving DNS requests from the Diagnostics Lookup when I do the testing. And reqular non DNS traffic does not seem to be affected. Stuff that is already in the state table continues to work.

I am just trying to think outside of the box.

@johnpoz

Yes, they replaced it for me, but it's very complicated to get the parcel sent to another country, customs problems at home, etc.
In the end, I was lucky (but also lost confidence) and got a new G3 Flex.

@jrey 23.09 to 23.09.1 on 2100 went smooth without a hitch

@etick Per https://forum.netgate.com/topic/184661/unable-to-upgrade-from-2-7-1-to-2-7-2-unmounting-boot-efi-done-failed there is a process but the safer way is to reinstall.

https://redmine.pfsense.org/issues/15081

@Gertjan I did however just fix it :) I stopped panicing for a second and started thinking laterally. I noticed that /cf/conf is actually a zfs filesystem. So I said zfs mount /pfSense/cf/conf and it insisted it was mounted. No conf directory there, so something amiss. I have nothing to lose at this point staring at a reinstall with a 4 month old backup. I simply unmounted it and remounted it, and I have my configuration back, the GUI is working and I have saved the current configuration to many places :)

Thanks for the suggestions, much appreciated :)

@LoGman said in Upgrade pfsense Netgate 6100, 23.05.1 > 23.09.1:

Do I need to worry about these error messages?

No, none of those look concerning. They look like old efi variables.

The root cause of this issue is fixed in 2.7.1/23.09. Going forward the selected repo branch is not switched when new releases are available. Updates are shown on the dashboard but the user will be required to select the new branch to upgrade.

@reynold yes as I recall it is. But as noted the default is to keep all settings during uninstall.