[SOLVED] 23.05-RELEASE package manager and pkg upgrade issues
-
Version 23.05-RELEASE was working well except something broke. This morning I got a notifiction that a new version of a package was available:
pfSense-repoc: 20230512_1 -> 20230523 [pfSense]
I ran pkg upgrade without issues.
This evening I tried running the package manager which seemed to work but the log contains:
/pkg_mgr_installed.php: The command '/usr/local/sbin/pfSense-repo-setup' returned exit code '1', the output was 'pfSense-repoc-static: invalid signature failed to read the repo data. failed to update the repository settings!!!'
I then ran pkg upgrade again and now I receive the following output:
Updating pfSense-core repository catalogue... pkg: https://pfsense-plus-pkg00.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-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-core/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg00.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-pkg00.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-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.pkg: Bad Request pkg: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_amd64-pfSense_plus_v23_05/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories!
Any ideas what is going on, and how to fix it?
-
@pst Similar issues here with the update (cannot post due to flagged as spam - ×
Post content was flagged as spam by Akismet.com) but Certification verification fails>>> 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-pkg01.atx.netgate.com 544518144:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/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-pkg01.atx.netgate.com 544518144:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921: 544518144:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBSD-src-plus-devel-main/crypto/openssl/ssl/statem/statem_clnt.c:1921: pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_armv7-pfSense_plus_v23_05/packagesite.txz: Authentication error Unable to update repository pfSense Error updating repositories! ERROR: It was not possible to determine pfSense-upgrade remote version ERROR: It was not possible to determine pfSense-upgrade remote version >>> Upgrading pfSense-upgrade... failed.
-
@matsan Yours is a slightly difference scenario, relating to the upgrade. Mine is after the successful upgrade, with a warning triggered by running the "package manager GUI" and CLI command "pkg upgrade" (not pfsense-upgrade)
-
webgui dashboard
system > update > update settings
Check "create boot environment.... and click save*
wait a while, a moment like 5 minutes
Connect via console and try out option (13)
have a look now if this be running fine again. -
@Dobby_ said in 23.05-RELEASE package manager and pkg upgrade issues:
Check "create boot environment"
There is no such option on the setting page. Only selection of branch, and "Disable the Dashboard auto-update check"
-
@pst said in 23.05-RELEASE package manager and pkg upgrade issues:
@Dobby_ said in 23.05-RELEASE package manager and pkg upgrade issues:
Check "create boot environment"
There is no such option on the setting page. Only selection of branch, and "Disable the Dashboard auto-update check"
-
@Dobby_ As I said, I have no such option, and I can't see how it would have any bearing on my problem anyway...
and you don't seem to run pfSense Plus based on that screenshots?
-
@pst said in 23.05-RELEASE package manager and pkg upgrade issues:
and you don't seem to run pfSense Plus based on that screenshots?
As I said, I have no such option, and I can't see how it would have any bearing on my problem anyway...
If you click the "save" button the cert will be new
saved also to your installation, you go then to the
console and type in "13" for using option (13)
after some time let us say 5 minutes and then
it should all fine for you again and you will be
able to update/upgrade again. -
@Dobby_ I followed your suggestion but it made no difference. If you check my initial post you will see that there were no issues with certificates, it looks more like a server misconfiguration. Don't confuse my issue with what @matsan reported.
Your screenshot states "Choose pfSence Plus Upgrade to upgrade to pfSense Plus", which naturally lead me to the conclusion that the screenshot was not from a pfSense Plus software release.
-
This post is deleted! -
today "pkg upgrade" worked but the package manager still generates an error:
-
@pst The Boot Environments menu is only available if running Plus and the file system is ZFS. If upgraded from UFS then a reinstall is necessary to get ZFS.
I know this is the upgrade page but you could try
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors“If the upgrade is still not offered, refresh the repository configuration and upgrade script by running the following commands from the console or shell:
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
”
(My emphasis)I had a similar error when upgrading (maybe their servers are busy?). I resolved mine by going to System/Update/Settings and saving the page without making changes. Others have changed to Previous branch and back to Current again. Others used the above command.
-
@SteveITS I didn't have any problems upgrading, I am on 23.05-RELEASE and the only remaining problem is when I go to the Package Manager (in the GUI) it triggers an error in the log (see image in my previous post).
I ran your commands but the issue still remains.
-
After running around in circles for almost a week, trying all suggestions on the forum I finally got it working. The solution? Using the console and
13) Update from console