Error messages from pfSense-repoc in
-
@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.