check_upgrade: "Updating repositories metadata" returned error code 1
-
I did a fresh install of 2.8.0 and do not get the error anymore.
-
im on 2.8.0 and i also had no problems
Shell Output - pkg update -f
Updating ntop repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: . done
Processing entries: . done
ntop repository update completed. 6 packages processed.
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 4 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching data.pkg: ......... done
Processing entries: .......... done
pfSense repository update completed. 541 packages processed.
All repositories are up to date. -
Same problem here, i'm running 2.8.0 updated from 2.7.2. It also takes much longer to login to dashboard than in previous version.
-
I am also encountering the (check_upgrade: "Updating repositories metadata" returned error code 1) Upgrade Notice after updating from 2.8.0 => 2.8.1
The notice timestamp updates on every reboot even with the dashboard auto-update check disabled. Even if I wait 10 minutes after the reboot before logging into the gui, the notice timestamp is when the system rebooted and not at time of log in.
Also, no repository errors when checking from the cli or the System Update gui. Other than the notice message, everything seems fine.
-
Yup the check that fails is during boot. The alert should be there however long you wait to login. But, yes, it's just ugly. It shouldn't actually be a problem.
-
fwiw, after checking a few other systems I am seeing this exact notice on several other 2.8.0 systems. Now I am geussing the above system had the notice before upgrading to 2.8.1.
-
This post is deleted! -
@SuperTypeGuy said in check_upgrade: "Updating repositories metadata" returned error code 1:
Also, no repository errors when checking from the cli or the System Update gui. Other than the notice message, everything seems fine.
Just chiming in. I came here to report this "check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-10-01 17:41:46" which is reported on each boot This was for a new host, installed fresh via USB. The config was then updated from backup of the (failed) host it was replacing.
Everything works...but we get this message on every reboot.
-
Point of interest: This may be related to my other issue/unbound. It seems that unbound is taking an inordinately long time to load now on v2.8.1 (1-2 minutes). @Gertjan pointed out that I am running an archaic config with pfBlocker in unbound mode and should update that to "python mode" for speed...
Is there something new with 2.8.2 / unbound / pfBlocker that causes DNS to take too long and therefore isn't available to "pkg update" when it is first run?
-
Hmm, it would certainly hit an error if it's unable to resolve.
Do you have the DNS behaviour set to local DNS only in System > General Setup?
-
@stephenw10 The slow-boot issue I fixed. Not interesting. I fat-fingered an entry in DNS TLS resolver names while working on other issue...
The "check_upgrade" errors on boot persist. However, I've tested every aspect of package management and can identify zero functional issues. Since the firewalls get rebooted on average of once a year, I'll just click "Mark as Read" and call it good.
-
Just for reference do you have DNS set to local only or can it fall back to external?
-
I'm experiencing this as well since installing a fresh copy of 2.8.1 and restoring a configuration backup from 2.7.2.
-
Only at boot?
-
@stephenw10 The error is showing up continuously throughout the day.
-
I am facing this error too after I reboot. Noticed it in the last two days.
My version is 25.07.1
-
Ok if you see it only at boot then it's a harmless ordering error we are looking into.
If you see it continuously then you probably have a connectivity issue. Try running:
pfSense-repoc -NDandpkg -d update. See what errors are shown. -
@stephenw10 said in check_upgrade: "Updating repositories metadata" returned error code 1:
Ok if you see it only at boot then it's a harmless ordering error we are looking into.
If you see it continuously then you probably have a connectivity issue. Try running:
pfSense-repoc -NDandpkg -d update. See what errors are shown.No errors on -repoc that I can see and a few bits towards the end of the second command:
- The requested document is not new enough
- Simulate an HTTP 304 response
- Closing connection
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[65728]> PkgRepo: verifying update for pfSense
Waiting for another process to update repository pfSense
All repositories are up to date. -
Those are normal output from pkg update.
Try:
pfSense-upgrade -dcThat's what's actually run that generates that error.
If that completes without error then it must be something intermittent. In which case I would check the system logs for errors when that alert is triggered.
-
[2.8.1-RELEASE][root@pfSense.lab.local]/root: pfSense-upgrade -dc >>> Updating repositories metadata... 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 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 pkg-static: An error occured while fetching package pkg-static: An error occured while fetching package Unable to update repository pfSense Error updating repositories! Your system is up to date
