Error messages from pfSense-repoc in
-
Hi pfSense Gurus!
Recently I see error messages from pfSense-repoc in System \ System Update menu:
Messages
pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\* 2>&1 pfSense-repoc: no pfSense packages installed
Need to mention that:
Current Base System
2.7.1
Latest Base System
2.7.1
Status
Up to date.How to resolve this issue?
and
What is the root of a problem? -
Try running
pfSense-repoc
at the command line.Also try running
pkg-static -d update
and see if that throws any errors. -
@stephenw10 said in Error messages from pfSense-repoc in:
Try running
pfSense-repoc
at the command line.pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\* 2>&1 pfSense-repoc: no pfSense packages installed
Also try running
pkg-static -d update
and see if that throws any errors.DBG(1)[26024]> pkg initialized Updating pfSense-core repository catalogue... DBG(1)[26024]> PkgRepo: verifying update for pfSense-core DBG(1)[26024]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite' DBG(1)[26024]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/meta.conf DBG(1)[26024]> curl_open DBG(1)[26024]> Fetch: fetcher used: pkg+https DBG(1)[26024]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/meta.conf DBG(1)[26024]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Mar 21 00:00:00 2023 GMT * expire date: Apr 20 23:59:59 2024 GMT * subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * using HTTP/1.1 > GET /pfSense_v2_7_1_amd64-core/meta.conf HTTP/1.1 Host: pkg00-atx.netgate.com User-Agent: pkg/1.20.8 Accept: */* If-Modified-Since: Wed, 15 Nov 2023 18:20:04 GMT < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Thu, 30 Nov 2023 11:23:00 GMT < Content-Type: application/octet-stream < Content-Length: 163 < Last-Modified: Wed, 15 Nov 2023 18:20:03 GMT < Connection: keep-alive < ETag: "65550bd3-a3" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection DBG(1)[26024]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/packagesite.pkg DBG(1)[26024]> curl_open DBG(1)[26024]> Fetch: fetcher used: pkg+https DBG(1)[26024]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-core/packagesite.pkg DBG(1)[26024]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults * Hostname pkg00-atx.netgate.com was found in DNS cache * Trying 208.123.73.207:443... * Connected to pkg00-atx.netgate.com (208.123.73.207) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Mar 21 00:00:00 2023 GMT * expire date: Apr 20 23:59:59 2024 GMT * subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * using HTTP/1.1 > GET /pfSense_v2_7_1_amd64-core/packagesite.pkg HTTP/1.1 Host: pkg00-atx.netgate.com User-Agent: pkg/1.20.8 Accept: */* If-Modified-Since: Wed, 15 Nov 2023 18:20:04 GMT < HTTP/1.1 200 OK Fetching packagesite.pkg: < Server: nginx < Date: Thu, 30 Nov 2023 11:23:01 GMT < Content-Type: application/octet-stream < Content-Length: 1492 < Last-Modified: Wed, 15 Nov 2023 18:20:04 GMT < Connection: keep-alive < ETag: "65550bd4-5d4" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection pfSense-core repository is up to date. Updating pfSense repository catalogue... DBG(1)[26024]> PkgRepo: verifying update for pfSense DBG(1)[26024]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite' DBG(1)[26024]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf DBG(1)[26024]> curl_open DBG(1)[26024]> Fetch: fetcher used: pkg+https DBG(1)[26024]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf DBG(1)[26024]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults * Trying 208.123.73.209:443... * Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Mar 21 00:00:00 2023 GMT * expire date: Apr 20 23:59:59 2024 GMT * subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * using HTTP/1.1 > GET /pfSense_v2_7_1_amd64-pfSense_v2_7_1/meta.conf HTTP/1.1 Host: pkg01-atx.netgate.com User-Agent: pkg/1.20.8 Accept: */* If-Modified-Since: Wed, 29 Nov 2023 20:22:44 GMT < HTTP/1.1 200 OK Fetching meta.conf: < Server: nginx < Date: Thu, 30 Nov 2023 11:23:01 GMT < Content-Type: application/octet-stream < Content-Length: 163 < Last-Modified: Wed, 29 Nov 2023 20:22:44 GMT < Connection: keep-alive < ETag: "65679d94-a3" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection DBG(1)[26024]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg DBG(1)[26024]> curl_open DBG(1)[26024]> Fetch: fetcher used: pkg+https DBG(1)[26024]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg DBG(1)[26024]> CURL> attempting to fetch from , left retry 3 * Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults * Hostname pkg01-atx.netgate.com was found in DNS cache * Trying 208.123.73.209:443... * Connected to pkg01-atx.netgate.com (208.123.73.209) port 443 * ALPN: curl offers http/1.1 * CAfile: none * CApath: /etc/ssl/certs/ * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.netgate.com * start date: Mar 21 00:00:00 2023 GMT * expire date: Apr 20 23:59:59 2024 GMT * subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * using HTTP/1.1 > GET /pfSense_v2_7_1_amd64-pfSense_v2_7_1/packagesite.pkg HTTP/1.1 Host: pkg01-atx.netgate.com User-Agent: pkg/1.20.8 Accept: */* If-Modified-Since: Wed, 29 Nov 2023 20:22:44 GMT < HTTP/1.1 200 OK Fetching packagesite.pkg: < Server: nginx < Date: Thu, 30 Nov 2023 11:23:02 GMT < Content-Type: application/octet-stream < Content-Length: 160540 < Last-Modified: Wed, 29 Nov 2023 20:22:44 GMT < Connection: keep-alive < ETag: "65679d94-2731c" < Strict-Transport-Security: max-age=31536000; preload < X-Content-Type-Options: nosniff < X-XSS-Protection: 1; mode=block < X-Robots-Tag: all < X-Download-Options: noopen < X-Permitted-Cross-Domain-Policies: none < Accept-Ranges: bytes < * The requested document is not new enough * Simulate an HTTP 304 response * Closing connection pfSense repository is up to date. All repositories are up to date.
PING and TRACERT to 208.123.73.209 and 208.123.73.207 (takes from debug output above) -> OK.
Also GUI browsing to pkg00-atx.netgate.com -> OK
So….? :)
-
Hmm, interesting maybe it just doesn't have a current repoc version.
If you run:
pkg-static upgrade pfSense-repoc
does it offer you an update to pfSense-repoc?If it does try just
pkg-static upgrade
and see what else might have failed to upgrade. -
@stephenw10 said in Error messages from pfSense-repoc in:
Hmm, interesting maybe it just doesn't have a current repoc version.
I have the same tough…
If you run:
pkg-static upgrade pfSense-repoc
does it offer you an update to pfSense-repoc?root: pkg-static upgrade pfSense-repoc ��������Updating pfSense-core repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) Your packages are up to date.
If it does try just
pkg-static upgrade
and see what else might have failed to upgrade.Updating pfSense-core repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense repository is up to date. All repositories are up to date. Checking for upgrades (8 candidates): 100% 8 B 0.0kB/s 00:01 Processing candidates (8 candidates): 100% 8 B 0.0kB/s 00:01 The following 8 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: frr9: 9.0.1 -> 9.0.1_1 [pfSense] frr9-pythontools: 9.0.1 -> 9.0.1_1 [pfSense] isc-dhcp44-relay: 4.4.3P1_3 -> 4.4.3P1_4 [pfSense] isc-dhcp44-server: 4.4.3P1_3 -> 4.4.3P1_4 [pfSense] libyang2: 2.1.111 -> 2.1.128 [pfSense] openvpn: 2.6.7 -> 2.6.8_1 [pfSense] pfSense-pkg-pfBlockerNG-devel: 3.2.0_6 -> 3.2.0_7 [pfSense] tailscale: 1.50.1 -> 1.54.0 [pfSense] Number of packages to be upgraded: 8 The process will require 1 MiB more space. 18 MiB to be downloaded. Proceed with this action? [y/N]:
So…?
-
@stephenw10 said in Error messages from pfSense-repoc in:
If it does try just
pkg-static upgrade
and see what else might have failed to upgrade.After several “upgrades”, output show “all ok”…
pkg-static upgrade Updating pfSense-core repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.conf: 0% Fetching packagesite.pkg: 0% pfSense repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% 0 B 0.0kB/s 00:01 Processing candidates (0 candidates): 100% 0 B 0.0kB/s 00:01 Checking integrity... done (0 conflicting) Your packages are up to date.
-
But
pfSense-repoc
still shows that error? -
@stephenw10 said in Error messages from pfSense-repoc in:
But
pfSense-repoc
still shows that error?Yes, the same
pfSense-repoc: si_get_packages: failed to run the pkg info command: /usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\* 2>&1 pfSense-repoc: no pfSense packages installed
-
Need to note that after pfSense server hardware restart, the BACKUP ERROR message appears:
General An error occurred while uploading the encrypted pfSense configuration to https://acb.netgate.com/save ( Unable to resolve acb.netgate.com )
-
Hmm, do you see the same output here:
[2.7.1-RELEASE][admin@t70.stevew.lan]/root: pkg info -x pfSense pfSense-2.7.1 pfSense-Status_Monitoring-php82-1.8_3 pfSense-base-2.7.1 pfSense-boot-2.7.1 pfSense-composer-deps-0.1 pfSense-default-config-serial-2.7.1 pfSense-kernel-pfSense-2.7.1 pfSense-pkg-Cron-0.3.8_3 pfSense-pkg-System_Patches-2.2.7_2 pfSense-pkg-nmap-1.4.4_7 pfSense-pkg-openvpn-client-export-1.9.2 pfSense-pkg-pfBlockerNG-devel-3.2.0_6 pfSense-pkg-suricata-7.0.2 pfSense-pkg-syslog-ng-1.16 pfSense-pkg-tftpd-0.1.3_4 pfSense-repo-2.7.1 pfSense-repoc-20230912 pfSense-upgrade-1.2.1 php82-pfSense-module-0.95
-
Does it show an error if you run that pkg command manually?
/usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\*
-
@stephenw10 said in Error messages from pfSense-repoc in:
Hmm, do you see the same output here:
[2.7.1-RELEASE][admin@t70.stevew.lan]/root: pkg info -x pfSense pfSense-2.7.1 pfSense-Status_Monitoring-php82-1.8_3 pfSense-base-2.7.1 pfSense-boot-2.7.1 pfSense-composer-deps-0.1 pfSense-default-config-serial-2.7.1 pfSense-kernel-pfSense-2.7.1 pfSense-pkg-Cron-0.3.8_3 pfSense-pkg-System_Patches-2.2.7_2 pfSense-pkg-nmap-1.4.4_7 pfSense-pkg-openvpn-client-export-1.9.2 pfSense-pkg-pfBlockerNG-devel-3.2.0_6 pfSense-pkg-suricata-7.0.2 pfSense-pkg-syslog-ng-1.16 pfSense-pkg-tftpd-0.1.3_4 pfSense-repo-2.7.1 pfSense-repoc-20230912 pfSense-upgrade-1.2.1 php82-pfSense-module-0.95
IDENTICALLY, but only
pfSense-pkg-pfBlockerNG-devel-3.2.0_7 ….. pfSense-pkg-suricata-7.0.2_1
-
@stephenw10 said in Error messages from pfSense-repoc in:
Does it show an error if you run that pkg command manually?
/usr/local/sbin/pkg-static info -R --raw-format json-compact pfSense-pkg-\*
No errors, output filling terminal screen.
-
-
@stephenw10 This helped me with moving from 2.7.0 to 2.7.1. I was seeing
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php"
And calling
pkg-static upgrade pfSense-repoc
a couple of times until all was upgraded, I finally was able to move to 2.7.1 without further error. Thanks.
-
Even after installing on bare metal and then restore from old /backup/config.xml file, the error still exist:
(the result of option “13” from Main dumb menu on terminal:
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-\* 2>&1 pfSense-repoc-static: no pfSense packages installed >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ...... done Processing entries: .......... done pfSense repository update completed. 550 packages processed. All repositories are up to date. Your packages are up to date
-
In 2.7.2?
That will be fixed in 24.03 (and 2.8) but it's only cosmetic. It shouldn't prevent accessing the repo at all.