Pkg Errors After Updating/Installing Packages
-
I have a NetGate 1541 running pfsense that is used on a disconnected network. In order to update and install needed bgp packages, I was able to get a primitive wireless connection working over a cellphone network as a temporary measure to apply these updates.
The dashboard said no pfsense update was needed as it was running the newest version. I was able to install the FRR package once I ran “pkg update” from the CLI console.. FRR and its dependencies seemed to install successfully as the web admin panel said success. I then saw that the factory installed IPsec and wireshark packages needed updated so I clicked the button to update those.
After that point, everything seemed to freeze. The admin web panel was unresponsive and the console was very slow as well. After waiting for a while with no change, I navigated away from that update package page. When I went back to the console, the “pkg update” command now returned an error saying libssl.so.30 cannot be found. Nothing with pkg commands worked. So I rebooted the device.
It is not back online and seems to be operating but the pkg errors persist. I would like to know how to resolve this issue before I put this device into production.
What can I do to solve this error? I’m unsure of the impact it is having at this point but don’t want to depend on the device until it’s working as expected without errors.
-
@djtech2k were you on 23.09.1? (See my sig)
“Not” or “now” back online?
Did you find https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors ?
Brute force would be to reinstall. You can get the install image from Netgate for free.
-
@SteveITS Good catch. I meant to say it IS online.
I have not read/tried that article but I will do that.
In the meantime, I unboxed a new NetGate 1541 that’s new in the box but it’s been probably 18 months or so. I’m not in the location of the one I opened this thread about so I’m messing with this one as a test. I ran repeated updates on pfsense until it said it was newest version, which I think was 23.09 IIRC.
The installed packages changed between the upgrades and I noticed they are different than what’s on my original 1541 and also different than a pfsense test vm I have running. All 3 have different installed packages from factory.
Anyway, this new 1541 is updated and I also updated the IPsec package that was installed. I went to the console and tried pkg help, and it fails with the same error as the original.
Thanks for the reference I will try it asap.
-
You will need to use
pkg-static updateif it's not on the current version because it will have updated pkg to the current version.That should not prevent the gui seeing pfSense updates or package updates though. It always uses pkg-static.
But you should upgrade to the current version, 23.09.1, before upgrading packages.
Steve
-
I am looking the problematic one right now and it shows the following:
Current Stable Version 23.09.1
Current Base system: 23.05.1
Latest Base System: 23.05.1Status: Up to Date
Why do I not have the option to upgrade from 23.05.1 to the 23.09.1?
-
When I run pkg-static upgrade, I get errors about unable to fetch package and error updating repositories.
-
That's expected if the 23.09.1 branch is selected whilst running 23.05.1 because the ABI version difference prevents it.
You should still be able to run:
pfSense-upgrade -dthough because that expects the ABI difference and allows for it.What error do you see running that?
-
I ended up figuring it out by a couple of things. I don't know why the UI was saying up to date, but after running some of the commands and I set the default gateway for the "temp" WAN connection, then the commands started working and the UI started saying update available.
There was some kind of connectivity issue resolving the DNS for the repo's and I don't know why hard setting the default gateway made it work, but thats what happened.
I was able to update to the newest version and the pkg commands work again. Thanks for the consult.
