pkg-static update only updates the available packages. The only thing that could get upgraded there is pkg itself. That can show that libssl error but not for pkg-static which is what pfSense upgrade uses.

@stephenw10 Ok thanks, have done.

@stephenw10 Yes, that was it! I have managed to upgrade it directly from 2.7.0 to 2.7.2 without any apparent issue. Thank you Stephen for you help!

@stephenw10 said in Fail upgrade but...: Yes I would reinstall 23.09.1 to be sure you have a clean system. Thanks I am not very experienced, the idea of reinstalling scares me a bit. This morning I couldn't access the administration web page, I had a 502 bad gateway. I managed to connect with the serial port, ran pkg-static info -x pfSense and saw that some packages were 23.09.1 and some 23.05.1. I upgraded with pkg-static upgrade and everything seems to be fine at the moment. Thank you very much

@SteveITS Thanks, the first was spot-on. Unfortunately, updating now fails with the EFI-space-problem - on a 500G SSD, yeah sure. However, I reinstalled all my 2.7.0 packages an the FW works again (at 2.7.0). The EFI-problem will have to wait for another day. Thanks for a non-sleepless night :).

@stephenw10 Thanks for the pointer on passing the -y flag. Prior to seeing this, I was able to install the sudo package and run the command in an SSH shell. After the "missing" packages were installed, things seem to be correct now. It is troubling that there was not an explicit notification from pfSense warning that the original upgrade had failed. This seems like a significant omission to me. When using the CLI available from the GUI (System / Command Prompt), I could not figure out a way for it to accept interactive input. I see that the documentation seems to be consistent with this behavior: "Interactive commands, such as vi will fail similarly, or may exit due to other issues with the terminal being non-interactive." Thanks again for your help!

What upgrades is it offering you? You might have to do it in several steps. If you really are running 2.4.0 though I would reinstall. Steve

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.