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

SprockTech · Aug 22, 2022, 10:27 PM

@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 · Aug 22, 2022, 10:36 PM

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 · Sep 17, 2022, 10:12 AM

@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 · Sep 17, 2022, 3:06 PM

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 · Sep 17, 2022, 3:12 PM

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 · Sep 17, 2022, 3:12 PM

@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 · Sep 17, 2022, 3:19 PM

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

Diver 0 · Sep 17, 2022, 4:07 PM

Thank you, Bingo600,
The diagnostics --> Edit File with new URL line worked.
Looks to me like the old URL,
"/pfSense_plus-v22_05_amd64-core"
got replaced.

Perhaps I should be ready to change that edit again in the future.

After all was done, Update returned a Status up to date, and 22.05 is still current. The square orange lamp is no longer flashing.

Dumb question: What does the acronym "repos" mean?

Thanks again,
Jack

MoonKnight · Sep 17, 2022, 4:26 PM

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

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

That did the trick :)

Sep 17 18:24:15	pkg-static	29389	pfSense-repo downgraded: 22.09.a.20220802.0600 -> 22.05_9
Sep 17 18:24:05	check_reload_status	448	Syncing firewall
Sep 17 18:24:05	php-fpm	22895	/pkg_mgr_install.php: Configuration Change: XXXX@XXXXXXXXX (Local Database): Saved firmware branch setting.
Sep 17 18:24:01	pkg-static	71353	pfSense-repo upgraded: 22.05_5 -> 22.09.a.20220802.0600
Sep 17 18:23:45	pkg-static	19568	pkg upgraded: 1.17.5_2 -> 1.18.3

bingo600 · Sep 17, 2022, 4:49 PM

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

Thank you, Bingo600,
The diagnostics --> Edit File with new URL line worked.

Dumb question: What does the acronym "repos" mean?

Thanks again,
Jack

Repos ... Shorthand for Repository , as in pfSense package repository

/Bingo