Unable to check for updates from dashboard

Nibblet · Jul 5, 2023, 3:17 AM

Well, that paste didnt work, let me remove the quoting doo-dads)

[2.6.0-RELEASE][admin@pfSense-firewall]/root: pfSense-upgrade -d -c
Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
2.7.0 version of pfSense is available

stephenw10 · Jul 5, 2023, 1:32 PM

You also see that in System > Update?

Try resaving the update branch in System > Update > Update Settings.
If that doesn't work try chnaging the branch to 2.6 (Previous) and then back to 2.7 (Current Stable).

Nibblet · Jul 6, 2023, 4:10 AM

@stephenw10 After doing that I end up with the same "Unable to check for updates"

This all seems to respond very quickly, like it isn't reaching out to anything across the network to come to the conclusion that it is unable to check for updates.

On a firewall I have on my home network that IS working, the update checks seem to take seconds, and a small gear cog is spinning while this happens, on these 'internal' firewalls the 'unable to check for updates' is near on immediate.

Is there something other than the SRV records that it would be trying to check for? Keeping in mind, the cli pkg-static is working fine and can happily download data, and updating packages from the GUI also works as expected - it is just the OS checks that are failing to detect a new version available, and only then partially, as the branch availability shows "Previous stable version (2.6.0 DEPRECIATED)" as well as "Current Stable Release (2.7.0-RELEASE)"

One thing I did notice though, was using pkg rather than pkg-static results in a library failure..
[2.6.0-RELEASE][admin@pfSense-firewall]/root: pkg
ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/sbin/pkg not found
[2.6.0-RELEASE][admin@pfSense-firewall]/root:

Could the widget be using pkg rather than pkg-static?

Nibblet · Jul 6, 2023, 4:10 AM

OK, that wasn't the case either - deciding that pkg was broken I renamed it then symlinked pkg-static to /usr/sbin/pkg and still get the same behaviour.
If I were to try to look through the sources of this widget, would anyone know where to start? (I.e - is it a separate package maybe? or is it part of the core build..?)

stephenw10 · Jul 6, 2023, 1:01 PM

Does it upgrade to 2.7 as expected if you just run pfSense-upgrade -d ?

Nibblet · Jul 7, 2023, 1:53 AM

@stephenw10 I can confirm that running the pfSense-upgrade -d from the CLI does indeed work :-)
To be fair, this is probably good enough for me - as I have other methods that do work to let me know there is a new version pending

Nibblet · Jul 7, 2023, 8:20 AM

Also to add - version 2.7.0 also seems to have the same problem - package management works, CLI package stuff works, but the update widget immediately fails with no indication as to why.

stephenw10 · Jul 7, 2023, 2:09 PM

And also on the System > Update page?

Nibblet · Jul 9, 2023, 2:05 AM

@stephenw10 That is correct, post upgrade neither the dashboard or system -> updates completes an update check and shows the same error message.

stephenw10 · Jul 10, 2023, 3:27 PM

Check the version of repoc you have:

pkg info -x pfsense

Nibblet · Jul 17, 2023, 12:26 AM

@stephenw10
[2.7.0-RELEASE][admin@pfSense]/root: pkg info -x pfsense
pfSense-2.7.0
pfSense-Status_Monitoring-php82-1.8_3
pfSense-base-2.7.0
pfSense-boot-2.7.0
pfSense-default-config-2.7.0
pfSense-kernel-pfSense-2.7.0
pfSense-pkg-API-1.6
pfSense-pkg-Open-VM-Tools-10.1.0_5,1
pfSense-pkg-openvpn-client-export-1.8
pfSense-pkg-pfBlockerNG-3.2.0_5
pfSense-pkg-squid-0.4.46
pfSense-rc-2.7.0
pfSense-repo-2.7.0_2
pfSense-repoc-20230616
pfSense-upgrade-1.0_33
php82-pfSense-module-0.95

(Sorry it took a while, work got busy)

callinectes · Jul 21, 2023, 1:55 PM

@stephenw10 I am having the same problem. Upgrade response was working fine a few weeks ago - before 2.7.0 came out. Now, if I run pkg info -x pfsense I get: ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"

If I run pkg-static info -x pfSense-upgrade I get: pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
pfSense-upgrade-1.0_15

If I run pfSense-upgrade -d -c I get:

Updating repositories metadata...
pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!
Upgrading pkg...
pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense-core has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
repository pfSense has no meta file, using default settings
pkg-static: An error occured while fetching package
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!

Any ideas? This is happening on two separate systems - one running 2.6.0 and one running 2.7.0-devel.

Gertjan · Jul 21, 2023, 1:55 PM

@callinectes said in Unable to check for updates from dashboard:

If I run pfSense-upgrade -d -c I get:

Updating repositories metadata...
pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended

Can you tell us what happens when you executed the recommend action ?

callinectes · Jul 21, 2023, 2:02 PM

@Gertjan Thanks for the response. I assume you mean running "pkg bootstrap -f"? I cannot do that right now but will attempt later and post back.

SteveITS · Jul 21, 2023, 2:14 PM

@callinectes said in Unable to check for updates from dashboard:

Shared object "libssl.so.30" not found, required by "pkg"

That error often means you have tried to install or update a package with the update branch set to a later pfSense version. (it defaults to Current) That tries to update any required libraries.

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

There are a couple suggestions in that redmine but otherwise one can reinstall and restore from backup.

stephenw10 · Jul 24, 2023, 8:23 PM

Seeing that lib error usually only means the version of pkg has been updated. That's normal as it checks for a new version every time it looks for pfSense updates.
It shouldn't be a problem since the pfSense pkg commands all use pkg-static.

@callinectes said in Unable to check for updates from dashboard:

Updating repositories metadata...
pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
Updating pfSense-core repository catalogue...
pkg-static: An error occured while fetching package

Seeing that I would try running pkg-static -d update to see what error is shown there.

callinectes · Jul 25, 2023, 12:43 PM

@stephenw10 Thanks for the suggestion. I received a lot of the following (too many similar entries to paste in but happy to if it would help:

Hostname pkg00-atx.netgate.com was found in DNS cache
Trying 208.123.73.207:443...
Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 (#9)
ALPN: offers http/1.1
CAfile: none
CApath: /etc/ssl/certs/
SSL certificate problem: self-signed certificate in certificate chain
Closing connection 9
DBG(1)[86277]> CURL> attempting to fetch from , left retry 2
Hostname pkg01-atx.netgate.com was found in DNS cache
Trying 208.123.73.209:443...
Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 (#10)
ALPN: offers http/1.1
CAfile: none
CApath: /etc/ssl/certs/
SSL certificate problem: self-signed certificate in certificate chain
Closing connection 10
DBG(1)[86277]> CURL> attempting to fetch from , left retry 1
Hostname pkg00-atx.netgate.com was found in DNS cache
Trying 208.123.73.207:443...
Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 (#11)
ALPN: offers http/1.1
CAfile: none
CApath: /etc/ssl/certs/
SSL certificate problem: self-signed certificate in certificate chain
Closing connection 11
pkg-static: An error occured while fetching package
Unable to update repository pfSense
Error updating repositories!

stephenw10 · Jul 25, 2023, 1:15 PM

Ah, what pfSense version are you running? That output is from the new development pkg version.

callinectes · Jul 25, 2023, 1:15 PM

@stephenw10 Per the dashboard "Version 2.6.0-RELEASE (amd64)"

But it was set to watch the 2.7.0 devel versions

Gertjan · Jul 25, 2023, 1:34 PM

@callinectes said in Unable to check for updates from dashboard:

watch the 2.7.0 devel versions

Strange.
That version doesn't exist any more since the end of June, as 'dev' became 'Release'.
On the other hand, if it can't update any more, it also can't update the list with available versions.

What about the the easy way out :
Get an USB drive, goto pfsense download - download your version 2.7.0.
Build teh USB drive.
Export the current config.
Boot the pfSEnse device from USB, install pfSense, 'all clean'.
When it reboot ... check that it shows a 'future version' (or ancient 2.6.0)
Check that the available package list populates.
Now, import your config.
Reboot.
Be very patient, as packages get installed in the background.
When you are sure it's done, do a reboot for good manners.
After reboot : test and check most needed and important system functionalities.

Make a post-it, and paste it on the pfSense box : "stay away from bleeding edge technology".