check_upgrade: "Updating repositories metadata" returned error code 1
-
I think you need some reputation to see it. Try again now
-
@stephenw10 thanks
-
I want to add that I had this problem when I updated to 2.8.0 and changed DHCP server to KEA, and I switched from the DNS Forwarder to DNS Resolver.
I switched from the DNS Forwarder to DNS Resolver only because the new KEA settings state: "DNS Registration. When checked, DHCP leases will automatically be registered with the DNS Resolver." So, I thought if I kept using the DNS Forwarder I'd lose DHCP lease registration. I wanted to use KEA but didn't want to lose DHCP lease registration and I wanted to use my pi-holes on my LAN that run unbound anyway. I used the forward-zone:
setting in pfSense's unbound to forward all DNS queries to my pi-hole(s).With this setup I had the aforementioned error frequently. I have to say that I had had it before I made the changes in the unbound settings, i.e., when unbound was running without predefined upstream resolver.
When I realized that my DHCP leases will still be registered when I use the DNS Forwarder I switched to it and haven't seen this error ever since. So,
- This error has something to do with unbound. I think the culprit has already been found (some kind of a race condition).
- Please change the description in the DHCP Server settings from "When checked, DHCP leases will automatically be registered with the DNS Resolver" to "When checked, DHCP leases will automatically be registered with the DNS Resolver or Forwarder."
-
Hmm, so you hit it even using Unbound in forwarding mode?
-
@stephenw10 Yes, that is correct. I thought maybe because I pointed to IPs on my LAN but it should work.
-
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.
