Package Manager/Avaliable packages empty

manilx

Hi

Out of the blue the Package Manager/Available Packages is completely empty. Nothing was changed since the last time I checked.

DNS is working fine.

Pls help.

manilx

@manilx Tried update repo:

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!

stephenw10

At the command line first run pfSense-repoc to update the cert then run pkg upgrade pfSense-repoc to check for updates there.

manilx

@stephenw10 root: pfSense-repoc
Segmentation fault (core dumped)

stephenw10

Hmm, this happened after you had upgraded to 23.05?

What does pkg-static info pfSense-repoc show?

manilx

@stephenw10 said in Package Manager/Avaliable packages empty:

Hmm, this happened after you had upgraded to 23.05?

What does pkg-static info pfSense-repoc show?

I updated a while ago so I can't tell if it was right after 23.05 (but I don't think so).

pkg-static info pfSense-repoc
pfSense-repoc-20230530
Name : pfSense-repoc
Version : 20230530
Installed on : Tue May 30 20:22:52 2023 WEST
Origin : sysutils/pfSense-repoc
Architecture : FreeBSD:14:amd64
Prefix : /usr/local
Categories : sysutils
Licenses :
Maintainer : luiz@netgate.com
WWW : https://gitlab.com/pfSense/repoc/
Comment : pfSense dynamic repository client
Shared Libs required:
libucl.so.5
Annotations :
FreeBSD_version: 1400085
build_timestamp: 2023-05-30T18:39:35+0000
built_by : poudriere-git-3.3.99.20220831
port_checkout_unclean: no
port_git_hash : 7fcf06634ef2
ports_top_checkout_unclean: yes
ports_top_git_hash: 7fcf06634ef2
repo_type : binary
repository : pfSense
Flat size : 16.7MiB
Description :
pfSense dynamic repositories client.

WWW: https://gitlab.com/pfSense/repoc/

manilx

@manilx Really hope we get this working!

stephenw10

Ok, yes that's the old pkg version.

Try running: pfSense-repoc-static.

If that runs try to update the pkg.

manilx

@stephenw10 said in Package Manager/Avaliable packages empty:

Ok, yes that's the old pkg version.

Try running: pfSense-repoc-static.

If that runs try to update the pkg.

Got this:

pfSense-repoc-static
pfSense-repoc-static: failed to fetch the repo data
failed to read the repo data.

stephenw10

Ok, just to be clear you're running those at the CLI directly not via Diag > Command Prompt in the GUI?

Try running: pfSense-upgrade -dc

manilx

@stephenw10 said in Package Manager/Avaliable packages empty:

Ok, just to be clear you're running those at the CLI directly not via Diag > Command Prompt in the GUI?

Try running: pfSense-upgrade -dc

Yes, running from SSH/CLI.

Got this:

pfSense-upgrade -dc
pfSense-repoc-static: failed to fetch the repo data
failed to read the repo data.
failed to update the repository settings!!!
failed to update the repository settings!!!

manilx

@manilx For what it's worth: Fixed by reflashing and restoring saved backup.

BTW: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-8200/reinstall-pfsense.html states that

"If there is an existing installation on this device, the Recover config.xml option will attempt to mount the existing installation drive and copy the previous configuration, including SSH keys. Choose that option first, then proceed through the install as usual."

Did not happen, it just installed as factory default. Had to reassign interfaces/IP's to get access to the web console an then restore backup.

After that smooth sailing.

Took me 15min, a lot less time than fiddling around trying to fix/locate the issue.