check_upgrade: "Updating repositories metadata" returned error code 1
-
The recent kea DHCP server supported fully automated DNS hist name integration into local pfSense DNS system, 'unbound'.
This is a new solution to a very old problem.
New solutions are often most not perfect the first time, so ... why do you want to deal with the issues known to 2.8.0 when the way better 2.8.1 is available (since a couple of months now) ? My advise : easy : get the latest version.
I'm using myself the 2.8.1 equivalent, 25.07.1, and it works fine for me."unbound" is by nature a resolver, but you can tell it to 'forward'. That will be like doing your daily shoppings with a Ferrari, but why not, you decide ^^ And I get it, you have another 'DNS' device, the pi-hole.
You can also consider disabling unbound, and activate the original 'ancient' forwarder that came with pfSense, also called dnsmasq :
and forward this forwader to your LAN pi-hilo.
This forwarder can't do 'DHCP host name integration' though ... -
@Gertjan I think you misread my post or didn't read it fully.
I was providing historical information when I was on 2.8.0. I updated to 2.8.1 next day it came out.
I used to use DNS Forwarder, then for the reasons given I switched to DNS Resolver and then switched back to DNS Forwarder. Contrary to what I also believed KEA DHCP Server does register DHCP leases with DNS Forwarder just like ISC did. It's all good now. No errors and local DNS is working.
-
@pfpv said in check_upgrade: "Updating repositories metadata" returned error code 1:
misread my post
This post ? is what I see/have.
-
Hi,
since today 21.11.2025 I get this error too:
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-11-21 12:10:06
-
Like repeatedly? Only at boot? Can you see packages?
-
@stephenw10 said in check_upgrade: "Updating repositories metadata" returned error code 1:
Like repeatedly? Only at boot? Can you see packages?
Repeatedly, in normal running mode, yes - packages are visible!
-
@stephenw10 On my side, repeatedly over 4000 entries in the log, in normal running mode.
Packages installed: There are no packages currently installed.
Packages available: Unable to retrieve package information. -
It started again today 340
check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-11-21 08:21:34
-
After not having any since my last post, I started seeing a few come through last night and this morning I’ve woken up to a few hundred of them. Version 2.8.1 and I can see packages.
-
Are you still seeing them now if you clear the existing alerts?
-
@stephenw10 After I cleared them and checked for updates manually, no.
But the same happened yesterday: I cleared around 1500, and it looked like no more were coming, then today I found over 4500. -
@stephenw10 said in check_upgrade: "Updating repositories metadata" returned error code 1:
Are you still seeing them now if you clear the existing alerts?
At the moment Nov 21 13:12:33 (CEST), No!
-
@stephenw10 My last one was at 1132 GMT, so circa 45 mins ago.
-
Ok thanks. It looks like there was a backend change. Digging....
-
Ok reverted whilst we did into the root cause. You shouldn't see any further alerts.
-
Looks like I am another user of the same problem on a few of our firewalls, one says the license is expired which is confusing since it doesn't expire for another two months. it says Community support now instead of PFSense + even though its clearly still on Plus.
If I review the rest of the fleet and find this same issue its going to be the nail in the coffin for us.
-
@stephenw10 said in check_upgrade: "Updating repositories metadata" returned error code 1:
Ok reverted whilst we did into the root cause. You shouldn't see any further alerts.
I have to add me to the choir. Had the same problem some time ago, then was silent until today. Now I'm getting a message every time the system does an update check or package check etc.
System shows it's registered, so no license issue (latest plus is on) and package manager shows packages to install.
System Update flip/flops between unable to check and no updates available, but every time something with "pkg" in the background is done, the counter hops up:
Every click in the package manager adds another one etc.
Opened the WebGUI to 1421 messages -.-
Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!
If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.
-
@stevo11811 said in check_upgrade: "Updating repositories metadata" returned error code 1:
one says the license is expired
OK that's a different symptom. Send me your NDI in chat and I'll check it.
I'll note that 'Community Support' is still valid in Plus though. It just means you don't have Pro or Ent support.
-
@stephenw10 Think I found the culprit:
pkg-2.2.2_2 Package managerPKG has over-updated itself again. So the non-static binary now throws ELF errors around again :(
That was already a problem multiple times. Someone done a repository change/update again?Fixing it with
pkg-staticalso seems not to work (by using install -f pkg) as pkg-static throws unknown errors:pkg-static install -f pkg Updating pfSense-core repository catalogue... pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error repository pfSense-core has no meta file, using default settings pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error repository pfSense has no meta file, using default settings pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error pkg-static: An error occurred while fetching package: Unknown error Unable to update repository pfSense Error updating repositories! -
@JeGr said in check_upgrade: "Updating repositories metadata" returned error code 1:
Every click in the package manager adds another one etc.
Opened the WebGUI to 1421 messages -.-
Yikes! I wouldn't expect that many update checks even if it is failing every time.
But try running:
pfSense-repoc -NDandpkg-static -d updateand see what errors are shown.If it's failing every time like that it may have lost the repo conf data or by trying to use invalid data.
