Unable to install packages on 23.05
-
I have just built up a pfSense box - since this is has Intel i226 interfaces on it I had to initially install 2.6 using a USB network card, then update to pfSense+ and from there to 23.05.
However I ended up with my interface names a bit mixed up, so I exported the config, swapped some of the lan and opt interfaces around, and re-imported the config.
I am now unable to use the package manager to install any packages - I get the
Another instance of pfSense-upgrade is running. Try again later
mesage.
If I run pfSense-upgrade -dc
pkg-static: No package(s) matching pfSense-pkg-* pfSense-repoc-static: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\* pfSense-repoc-static: no pfSense packages installed pfSense-repoc-static: invalid signature failed to read the repo data. failed to update the repository settings!!! failed to update the repository settings!!!
The box certainly appears to be licensed for pfSense plus - the registration info shows on the dashboard, and an attempt to use the System->Register function tells me "Your device does not require registration, we recognize it already. You may have already registered, or it may be a pre-registered Netgate appliance."
Any clues what to do, please?
Nigel.
-
@nmeth There have been a few posts like this. See if this thread helps: https://forum.netgate.com/topic/180382/solved-unable-to-install-or-upgrade-packages/
-
Thanks @SteveITS - unfortunately none of these so far have helped for me...
To summarise:-
- Can't re-register - the dialog box for the key is inactive (presumably because it thinks it is appropriately registered)
pkg-static upgrade -fy pfSense-repoc
gives a batch of errors...
And it looks like I have a reason as to why its not working...
The NDI within the
pfSense-repoc -D
output does not match the dashboard Netgate Device ID. I presumably need to do something to persuade the system its not registered (so the registration dialog becomes available again), and then register again for pfSense plus.Is there a way I can do this without having to contact support?
Nigel.
-
Try to update the repoc pkg at the CLI:
pkg upgrade pfSense-repoc
That bug has been fixed and you should still be able to access the repo from the CLI.
Steve
-
Shell Output - pkg upgrade pfSense-repoc Updating pfSense-core repository catalogue... pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-core/meta.txz: Bad Request repository pfSense-core has no meta file, using default settings pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/meta.txz: Bad Request repository pfSense has no meta file, using default settings pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories!
I see there is some info about 23.05 requiring a valid registration to be able to access the package repos, so its looking to me as though my current registration is not correct.
-
Send me your NDI in chat and I'll check it.
-
Sorry I just noticed the above output includes 'Shell Output' which implies you ran it via the GUI.
That command must be run at the CLI not via the GUI command prompt. It should succeed at the CLI and pull in the updated pkg which will fix the GUI.
-
@stephenw10 I had run it by the GUI, but have just retried with a ssh session (as root), and a console shell.
In both cases I am getting exactly the same output.
-
@nmeth I'm having the same issue on a long installed and working Netgate 8200. No packages shown.
Created topic also: https://forum.netgate.com/topic/180823/package-manager-avaliable-packages-empty -
Running on an 8200 is a slightly different case. I replied there.
-
Apologies for the delay, but having got the issue fixed I thought it would be worth adding a note as to what the problem was rather than leving it dangling.
Thanks for the help of @stephenw10 who checked the (two different) NDI (Network Device Id) that were showing up on the sytem against the pfSense registration db, and fixed the registration there to be correct.
Somehow, most likely due to me having played with the network devices in the config and then reloaded it, the pfSense plus registration did not match the device id. Once that was fixed I could get the package database and install packages again.
Nigel.