No available packages

stephenw10

Most likely your NDI changed since you first registered it. Send it to me in chat and I can check.

DominikHoffmann

I was sent here by @p1erre (Thanks!) from an original thread I had posted: No available packages. My hardware is a Netgate 2100 that had never been on the CE of pfSense. About three weeks ago I updated it from 22.05 to 23.01 using the

run usbrecovery

method, when I had experienced a couple of catastrophic update failures with other pfSense installations I manage.

stephenw10

What do you see if you run pkg -d update at the command line?

Steve

DominikHoffmann

@stephenw10: This is the output

[23.01-RELEASE][admin@***.***]/root: pkg -d update
DBG(1)[80971]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[80971]> PkgRepo: verifying update for pfSense-core
DBG(1)[80971]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-core/meta.conf
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/meta.conf with opts "i"
DBG(1)[80971]> Fetch: fetcher chosen: https
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.pkg
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.pkg with opts "i"
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.txz
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_aarch64-core/packagesite.txz with opts "i"
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[80971]> PkgRepo: verifying update for pfSense
DBG(1)[80971]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/meta.conf
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/meta.conf with opts "i"
DBG(1)[80971]> Fetch: fetcher chosen: https
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.pkg
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.pkg with opts "i"
DBG(1)[80971]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.txz
DBG(1)[80971]> opening libfetch fetcher
DBG(1)[80971]> Fetch > libfetch: connecting
DBG(1)[80971]> Fetch: fetching from: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_aarch64-pfSense_plus_v23_01/packagesite.txz with opts "i"
pfSense repository is up to date.
All repositories are up to date.

Doesn’t that contradict the fact that the Avahi package is not on the latest version?
Screenshot 2023-04-05 at 10.59.51 AM.png

stephenw10

Hmm, that fact it can see it's not on the latest version means it's able to see the pkg repo. That output all looks good so I'd expect a firmware update to also be fine.

What do you see from pfSense-upgrade-dc?

DominikHoffmann

@stephenw10

[23.01-RELEASE][admin@smiley.ahs.selfip.net]/root: pfSense-upgrade-dc
pfSense-upgrade-dc: Command not found.

stephenw10

Sorry typo'd. Try: pfSense-upgrade -dc

DominikHoffmann

@stephenw10

[23.01-RELEASE][admin@smiley.ahs.selfip.net]/root: pfSense-upgrade -dc
Another instance is already running... Aborting!

Unfortunately, I will have to check with the client, whether rebooting the appliance is okay, if that is one of the troubleshooting steps for this.

stephenw10

Ok that would explain why the gui update is also failing.

You can probably find that process and kill it. Or wait for it to timeout.

DominikHoffmann

@stephenw10: What would I search for in the list of running processes?

stephenw10

I would look for pkg-static. You might have soimething stuck if it was reinstalling a package after the upgrade. If it hasn't been rebooting since.

DominikHoffmann

@stephenw10: System Activity shows nothing like that.

stephenw10

Hmm, try: ps -aux | grep pfSense-upgrade

Or: ps -aux | grep pkg-static

Both will show the grep process itself but should also show any stuck processes.

DominikHoffmann

@stephenw10

I tried

[23.01-RELEASE][admin@***.***]/root: top -aSH | grep pkg
[23.01-RELEASE][admin@***.***]/root: top -aSH | grep static
[23.01-RELEASE][admin@***.***]/root:

Now trying your last suggestion:

[23.01-RELEASE][admin@***.***]/root: ps -aux | grep pkg-static
root     1664   0.0  0.1  12660  2356  0  S+   11:57     0:00.01 grep pkg-static
[23.01-RELEASE][admin@***.***]/root: ps -aux | grep pfSense-upgrade
root    59374   0.0  0.1  12660  2348  0  S+   11:59     0:00.01 grep pfSense-upgrade
[23.01-RELEASE][admin@***.***]/root:

Nothing there, either.

stephenw10

Huh, and it's still showing 'another process is running' when you run pfSense-upgrade -dc ?

DominikHoffmann

@stephenw10 said in No available packages:

pfSense-upgrade -dc

Now I get

[23.01-RELEASE][admin@smiley.ahs.selfip.net]/root: pfSense-upgrade -dc
>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Your system is up to date

… and I now see this:
Screenshot 2023-04-05 at 12.12.49 PM.png

This means that the problem resolved itself. Thanks a bunch!

stephenw10

Yeah that all looks good. I'd guess there was a pkg process running that timed out since you first checked.

planedrop

Ran into this issue today after doing some maintenance on our HA setup and rebooting both nodes.

I removed some interfaces from our units (needed to install that CPIC card on a pair of 1541s), packages no longer showed after this, but I figured the NDI changed and I needed to re-register, so got 2 TAC Lite licenses and did this on each node.

So far, the primary works perfectly, no issues at all and I can view packages.

But the secondary/failover unit still can't see packages but can ping the outside world and resolve DNS.

However, another error is showing up that maybe would help a bit, multiple things are claiming a "Gateway, NONE AVAILABLE" error but only on this secondary node.

stephenw10

Try running pkg -d update and pfSense-upgrade -c at the command line. See what errors you're getting.

planedrop

@stephenw10 Yeah so I was getting the authentication errors when doing that (I was the one that DMed you about this shortly after this post), rebooted 2 more times and everything is back to normal. I'll be watching this secondary node closely though to see if any other abnormal things arise from it.