Unable to check for updates | Unable to retrieve package information. 2.3.3-RELEASE-p1
-
Hello,
I'm encountering an issue with my pfSense installation, and I've tried several troubleshooting steps without success. I'm hoping someone in the community can provide some guidance or solutions.
I'm currently running pfSense version 2.3.3-RELEASE-p1, and my attempts to update to a more recent version have been unsuccessful. I've encountered issues related to trusted public keys and repositories not updating.
I've tried the following steps:
Checked DNS Resolution: DNS resolution appears to be working as I can ping external hosts and resolve other domains. However, I'm unable to fetch data from pkg.pfsense.org.
Configuration Checks: I've reviewed my system's TLS and firewall configurations to ensure they are not blocking outgoing connections to the pfSense repositories.
Manual Key Fetching: I attempted to manually fetch the keys using fetch, but this also returned a "No address record" error for pkg.pfsense.org.
Repository Adjustments: I've adjusted the repository configuration files in /usr/local/etc/pkg/repos to point to the latest repository URLs.
Despite these efforts, I've been unable to resolve the issue, and I'm unable to perform the necessary updates for my pfSense installation.
If anyone has encountered a similar issue or has suggestions for resolving this issue, your assistance would be greatly appreciated.
Thank you in advance for your help.
Best regards,
Shedfx
-
@SuccessRed said in Unable to check for updates | Unable to retrieve package information. 2.3.3-RELEASE-p1:
2.3.3-RELEASE-p1
Way to old.
But not really an issue.
Get an USB drive ready ..... download the latest and greatest.Read at least this : do the etcher thing.
Export your current "config.xml".
Now, zap the install : over write everything, chose the ZFS file system doing so. Assign interfaces, access the GUI, import the saved config. Enjoy.
-
@SuccessRed said in Unable to check for updates | Unable to retrieve package information. 2.3.3-RELEASE-p1:
2.3.3-RELEASE-p1
Way to old.
But not really an issue.
Get an USB drive ready ..... download the latest and greatest.Read at least this : do the etcher thing.
Export your current "config.xml".
Now, zap the install : over write everything,. Assign interfaces, access the GUI, import the saved config. Enjoy.
-
@Gertjan
Thanks for the response but I think I have resolved many issues and I think the last one is :
pkg-static: repository pfSense contains packages for wrong OS version: FreeBSD:11:amd64 -
@Gertjan
I think i have to fix this first :
Shared object "libelf.so.2" not found, required by "pkg" -
@SuccessRed
Reminder : according to every update/upgrade notice of pfSense :
"Never ever upgrade packages before you've upgraded pfSense, if a pfSEnse update is available".Because : packages are based upon - or, as they say : compiled against, the latest pfSense version, and pfSense uses the entire FreeBSD kernel and source tree.
More clear : based upon the latest FreeBSD version, and all the related FreeBSD libraries.Your 2.3.3 is probably a FreeBSD 12.x (old) kernel, and thus using older libraries.
See for example : https://www.netgate.com/blog/pfsense-2.7.0-and-23.05 and read what has been written after "Upgrading pfSense CE software".
So, ok to keep an old pfSense version. But don't upgrade packages any more as soon as a new pfSense comes out.
That's the price you pay when you want to keep an old version active.Like : you cant' install a pure Windows 11 application on a Windows 95 system.
The first is 64 bits, the latter is 16/32 bits. Forcing the install will break the system - you'll created a DLL-hell.@SuccessRed said in Unable to check for updates | Unable to retrieve package information. 2.3.3-RELEASE-p1:
Shared object "libelf.so.2" not found, required by "pkg"
That's what I mean with "DLL-hell" : you've seen the start. It will never end.
Many have tried ....... no one came back to tell about it. They all di..... -
@Gertjan so the solution is to erase everything and switch to the latest versions , with a backup made beforehand
-
That would solve the problem, yes. It's probably easier than the multiple upgrade steps that would be required to upgrade from 2.3.3 anyway.
However one thing to be aware of here is that 2.3.3 supported 32bit hardware and 2.7 does not. So check that whatever you're running on is 64bit capable.
Steve
