No available packages
-
@stephenw10 said in No available packages:
Did you resave the stable repo settings?
Yes I did. It also shows me the latest stable version 23.01
Current Base System23.01
Latest Base System23.01
StatusUp to date. -
Send me your NDI in chat and I'll check it.
That error means it's trying to authenticate the repo using the wrong cert. Resaving the repo should set the correct line in the config file so it then uses the correct cert.
Steve
-
@p1erre You need to do the following in order to save as instructed by Steve:
System > Update > Update Settings > Save
This is what worked for me when I had similar issues to yours.
Ted Quade
-
@tedquade Thanks Ted, but I already did it. Issue still there. I also did
mkdir /root/backup && cp -r /usr/local/etc/pfSense/pkg/repos /root/backup/ && rm -rf /usr/local/etc/pfSense/pkg/repos && pfSense-upgrade -c -das suggested in another thread. Still getting
pfSense-upgrade -c -d ......ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com 34942701568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921: Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com ... 34942701568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921: Certificate verification failed for /C=US/ST=Texas/L=Austin/O=Rubicon Communications, LLC (Netgate)/OU=pfSense Plus/CN=pfsense-plus-pkg00.atx.netgate.com 34942701568:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/statem/statem_clnt.c:1921: pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Authentication error Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense remote version ERROR: It was not possible to determine pfSense-base remote version ERROR: It was not possible to determine pfSense-kernel-pfSense remote version Your system is up to date -
P p1erre referenced this topic on
-
P p1erre referenced this topic on
-
I too am unable to see any packages. I believe I switched to pfSense+ but cannot remember. I have followed all the steps in this thread and the bug report and no progress. I also see the following, even though I have registered (and now reregistered) it with pfSense+
Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription at the <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a> to receive future updates. ERROR: It was not possible to determine pkg remote version >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/meta.txz: Bad Request repository pfSense-core has no meta file, using default settings pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.pkg: Bad Request pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/meta.txz: Bad Request repository pfSense has no meta file, using default settings pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.pkg: Bad Request pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense remote version ERROR: It was not possible to determine pfSense-base remote version ERROR: It was not possible to determine pfSense-kernel-pfSense remote version Your system is up to date -
Most likely your NDI changed since you first registered it. Send it to me in chat and I can check.
-
P p1erre referenced this topic on
-
P p1erre referenced this topic on
-
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 usbrecoverymethod, when I had experienced a couple of catastrophic update failures with other pfSense installations I manage.
-
What do you see if you run
pkg -d updateat the command line?Steve
-
@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?
-
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? -
[23.01-RELEASE][admin@smiley.ahs.selfip.net]/root: pfSense-upgrade-dc pfSense-upgrade-dc: Command not found. -
Sorry typo'd. Try:
pfSense-upgrade -dc -
[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.
-
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.
-
@stephenw10: What would I search for in the list of running processes?
-
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. -
@stephenw10: System Activity shows nothing like that.
-
Hmm, try:
ps -aux | grep pfSense-upgradeOr:
ps -aux | grep pkg-staticBoth will show the grep process itself but should also show any stuck processes.
-
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.
-
Huh, and it's still showing 'another process is running' when you run pfSense-upgrade -dc ?
