"Unable to check for updates" in GUI, update in CLI working fine

fireodo

@sprocktech said in "Unable to check for updates" in GUI, update in CLI working fine:

@stephenw10 I have a 3100 with the same problem as @kepak where updating from the GUI doesn't work but via SSH does. I was on 22.01 and just updated to 22.05 via SSH. Still says "Unable to check for updates" in the GUI after rebooting.

After a Power failure I had this problem too - in my case this helped:

pkg-static upgrade -f

SprockTech

@fireodo Thanks for the suggestion. Unfortunately that didn't help either. I haven't done the full backup/reset/restore procedure yet. I'll update this thread later if that works for me.

stephenw10

Try running pkg -d update at the command line and see what errors it shows.

SprockTech

@stephenw10 I ran that before and don't recall seeing any errors. I just ran it again and still don't see any errors. Also, when I ran the command that @fireodo suggested, I don't recall seeing any errors there either.

[22.05-RELEASE][admin@firewall.home.local]/root: pkg -d update
DBG(1)[7090]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[7090]> PkgRepo: verifying update for pfSense-core
DBG(1)[7090]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[7090]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-core/meta.conf
DBG(1)[7090]> opening libfetch fetcher
DBG(1)[7090]> Fetch > libfetch: connecting
DBG(1)[7090]> Fetch: fetching from: https://pkg01-atx.netgate.com/pkg/pfSense_plus-v22_05_armv7-core/meta.conf with opts "i"
DBG(1)[7090]> Fetch: fetcher chosen: https
DBG(1)[7090]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-core/packagesite.pkg
DBG(1)[7090]> opening libfetch fetcher
DBG(1)[7090]> Fetch > libfetch: connecting
DBG(1)[7090]> Fetch: fetching from: https://pkg01-atx.netgate.com/pkg/pfSense_plus-v22_05_armv7-core/packagesite.pkg with opts "i"
DBG(1)[7090]> Fetch: fetcher chosen: https
DBG(1)[7090]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-core/packagesite.txz
DBG(1)[7090]> opening libfetch fetcher
DBG(1)[7090]> Fetch > libfetch: connecting
DBG(1)[7090]> Fetch: fetching from: https://pkg01-atx.netgate.com/pkg/pfSense_plus-v22_05_armv7-core/packagesite.txz with opts "i"
DBG(1)[7090]> Fetch: fetcher chosen: https
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[7090]> PkgRepo: verifying update for pfSense
DBG(1)[7090]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[7090]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05/meta.conf
DBG(1)[7090]> opening libfetch fetcher
DBG(1)[7090]> Fetch > libfetch: connecting
DBG(1)[7090]> Fetch: fetching from: https://pkg00-atx.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05/meta.conf with opts "i"
DBG(1)[7090]> Fetch: fetcher chosen: https
DBG(1)[7090]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05/packagesite.pkg
DBG(1)[7090]> opening libfetch fetcher
DBG(1)[7090]> Fetch > libfetch: connecting
DBG(1)[7090]> Fetch: fetching from: https://pkg00-atx.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05/packagesite.pkg with opts "i"
DBG(1)[7090]> Fetch: fetcher chosen: https
DBG(1)[7090]> Request to fetch pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05/packagesite.txz
DBG(1)[7090]> opening libfetch fetcher
DBG(1)[7090]> Fetch > libfetch: connecting
DBG(1)[7090]> Fetch: fetching from: https://pkg00-atx.netgate.com/pkg/pfSense_plus-v22_05_armv7-pfSense_plus_v22_05/packagesite.txz with opts "i"
DBG(1)[7090]> Fetch: fetcher chosen: https
pfSense repository is up to date.
All repositories are up to date.

SprockTech

@stephenw10 I have a suspicion that this is could be a DNS issue. Does the GUI handle DNS lookups differently than when updating via the command line?

stephenw10

No it doesn't.
Try pkg-static -d update instead. That's what the GUI actually runs. It should be identical but...

SprockTech

@stephenw10 Yes, identical output with that command. Are there logs that correspond with the update checking?

SprockTech

@stephenw10 I've tried several things, still no luck.

Removed an old OpenVPN S2S interface that I wasn't using
Added IPv6 DNS servers under General Setup
Removed pfBlockerNG

So far nothing has helped. Any other idea besides resetting to factory defaults?

FYI, I've got several VLANs and I'm using Avahi, Wireguard and Suricata.

stephenw10

Are you able to see packages available in the Package Manager?

SprockTech

@stephenw10 Yes, I can see a full list of available packages. And even though this might make things more confusing, I will note that I actually saw a message like "your system is up to date" on the firmware update one time just now. I've tried refreshing the page multiple times after that and it goes back to saying "unable to check for updates". But refreshing the list of available packages loads every time.

stephenw10

Hmm, odd.

I would probably try switching the update branch in System > Update. Wait a few minutes then switch it back again and recheck. That will force it reinstall the repo pkg.

Or do that manually using the command shown here:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

SprockTech

@stephenw10 Thanks for the continued suggestions. Unfortunately the update branch switch trick didn't work. I got the DEV branch to give me a response once, but that's it. Every other time I tried switching I got nothing. Also, I ran the manual command from the link and rebooted, still no update status is showing in the GUI.

stephenw10

Hmm, very odd. Well you could try one of the more drastic options further down on that trouble shooting doc.

As a last resort you can always reinstall 22.05 clean and restore your config into it. Doing that is relatively quick if you already have console access. Open a ticket with us to get the image:
https://www.netgate.com/tac-support-request

Steve

SprockTech

@stephenw10 Thanks. I can go through with the re-image. But before I do that I'd like to look at debug logs. Where should I look for logged information related to the update check?

stephenw10

The only thing that is stored regularly are two files in /conf. Those detail the last successful upgrade and the output of the last check. But I'd expect that to show as successful since it does at the CLI.

Otherwise errors would be in the main system log or potentially in the DNS logs if it was failing to resolve something.

Steve

kepak

@sprocktech @stephenw10 I don't reply cause I was waiting to have a opportunity for make fresh install and restore a backup. I have done this right now, and I didn't help. I have idea, if this could be DNS issue, maybe it's because I'm using Named package with custom config?

Diver 0

Hello,

Novice user here.

Orange square flashing.
Netgate 6100
Current Ver 22.05
Internet is up.
Previous updates leading up to 22.05 were successful.
I did not diddle with anything afterwards.

GUI:
Rebooting System didn't help.

Status ---> Dashboard --->
Netgate Services and Support --->
"Retrieving Support Information" is orange
text, and is not retrieving.

System ---> Update ---> Retrieving
"Unable to check for updates"

A website says I am supposed to use Package Manager.
Accordingly,
System ---> Package Manager ---> Available Packages
it says,
" * Unable to retrieve package information"

Search engine search results tell me to
"Update URL" at "System:Firmware:Settings"
Unable to locate this menu option, or I
need new eyeglasses.

Upon console in

Option 13 returned error
"ERROR: It was not possible to identify which pfSense kernel is installed"

I have no idea how to fix the above error.

Tried, Option 8, then typed pkg -d update
Error was returned
"pkg: invalid url: /pfsense_plus-v22_05_amd64-core
pkg: Cannot parse configuration file!"

I did not try "pkg-static upgrade -f"
and I did not try "pkg-static -d update"
'cause I don't know if doing that will break things.

Advice will be most highly appreciated.
Thanks very much
Jack

stephenw10

Running pkg-static -d update will not break anything. The system runs that every time you connect to the dashboard. It will show you any errors that may be preventing it update.

bingo600

@diver-0

Seems like you have been hit by the "Bad repos update"

See here:

https://forum.netgate.com/topic/174768/unable-to-check-for-updates/12

This is Netgates Official fix (guide)
https://forum.netgate.com/post/1062052

Or this one, if a CLI doesn't scare you
https://forum.netgate.com/post/1062026

/Bingo

stephenw10

The pkg is fixed now so there's no need to manually enter anything.

If you're still seeing it, because the firewall pulled in the bad pkg, then switching the update branch to development and then back to latest stable will pull in the fixed pkg.

Doing that you will see logged:

Sep 17 15:36:45 	pkg-static 	13430 	pfSense-repo upgraded: 22.05_5 -> 22.09.a.20220802.0600
Sep 17 15:37:19 	pkg-static 	22387 	pfSense-repo downgraded: 22.09.a.20220802.0600 -> 22.05_9

Steve