check_upgrade: "Updating repositories metadata" returned error code 1
-
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: Fetching data.pkg: pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: Fetching data.pkg: pfSense repository is up to date. All repositories are up to date. Your system is up to date -
OK that seems fine. You might try:
pkg-static -d updateBut I would expect pfSense-upgrade to throw an error if that does.
-
It seems to be fixed this morning on all firewalls I was having trouble with.
-
Ah good to hear.
-
@stephenw10 said in check_upgrade: "Updating repositories metadata" returned error code 1:
Do you have the output error shown by lldpd?
It's likely the same as
pkgitself, an elf error because of ld.so mismatch due to wrong version of a library. I think it was either libc.so.7 or libssl.so.30 or one among those lines. It'd surely be easy to reproduce when you have a 25.07 VM and manually upgrade pkg to 2.x.x instead of 1.12.5.Edit:
[25.07.1-RELEASE][admin@pfs-plus-2507.lab.test]/root: pkg info ld-elf.so.1: Shared object "libutil.so.10" not found, required by "pkg" [25.07.1-RELEASE][admin@pfs-plus-2507.lab.test]/root: lldpd ld-elf.so.1: Shared object "libutil.so.10" not found, required by "libpkg.so.4"after manually force-down installing pkg to 1.12.5 again, the errors also stopped.
Cheers
-
But those libs are not updated when pkg gets upgraded. That;s why the new pkg fails to run unless it's run with statically linked libs. So I wouldn't expect anything else to be affected unless that was also upgraded. But, yes, let me confirm....
-
Hmm, OK. Let me try to replicate that....
-
@stephenw10 said in check_upgrade: "Updating repositories metadata" returned error code 1:
Hmm, OK. Let me try to replicate that....
I did that 5min ago, so it does indeed hang on libutil or some other it seems ;)
Anyway it's one of the dependency libs that PKG and LLDPd share that seems to be borked whenever pkg is "over-updating" itself.
lddshows a LOT they have in common. I forgot to make a ldd-run before and after, that should have shown some light into it. -
Ok I can see how this would break it but, for some reason, I'm now failing to replicate it. Digging....
-
@stephenw10 I did it this way:
- used a 25.07.1 VM
- set update path to 25.11
- forced install of pkg with
pkg install -f pkg - --> pkg 2.3.x installed
- immediatly afterwards, running of
pkgfails because of dependencies - lldpd now also fails with the same reasons
Yes I know, normally one wouldn't force pkg to install a new version but that's what now has happened to various systems twice. Once in a beta build or when the first RC came out? and once now at the beginning of that thread. Every time we checked, pkg has updated itself to a new 2.x.x version and thus threw errors and lldpd died. So something seems to have triggered a pkg upgrade to a newer version even if 25.07 was selected fixed as install path.
Cheers :)
-
Ah, yes that would do it! I was trying to replicate the unexpected update which I've so far been unable to. I suspect this was entirely down to the backend changes last week which have since been corrected. I'll keep monitoring it.
