Error messages from pfSense-repoc in
-
@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.
-
@stephenw10 said in Error messages from pfSense-repoc in:
In 2.7.2?
pfSense CE 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.
Till now (October 1, 2024) no any fixes.
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
Please take attention at this string in output:
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
IMPORTANT NOTE:
After totally fresh installation on the same bare metal server, this issues not exist.
But after restoring from backup conf.xml (and cold restart) the issue come back and still. -
Right but that should be cosmetic only. It shouldn't prevent seeing or installing packages or updates.
-
@stephenw10 said in Error messages from pfSense-repoc in:
Right but that should be cosmetic only. It shouldn't prevent seeing or installing packages or updates.
Ok, understand. Thank You!
P.S.
But I have a little bored that Netgate spray out the resources on much new features in state when there are a lot of small (but annoying) unresolved bugs (according bugtracker). -
It's already fixed though, just waiting for the next release.