(Solved) Error messages pfSense+ 24.03 BETA

[stephenw10]

Hmm, that should be functioning. Checking....

[Dobby_]

@JonathanLee said in Error messages pfSense+ 24.03 BETA:

@Dobby_ it’s probably close to RC and that repo is no longer active wait a couple days

Thanks this could really be! I am waiting for the RC and will see what comes.
I have no problems installing packages and/or updating packages or like
said above upgrading the pfSense itselfs, only in the console I get this
messages. But the entire system is running fine, a bit more speed like
the 22.05 or 23.09.01 as I see and feel it. More agile acting.

[Dobby_]

@stephenw10 said in Error messages pfSense+ 24.03 BETA:

Hmm, that should be functioning. Checking....

Many thanks to you for that, but if this will be only related to the BETA status
I can also wait for the RC.

[stephenw10]

Hmm, something seems to be amiss. Still digging....

[stephenw10]

Hmm if you run pfSense-upgrade -c then run pkg update does it succeed?

[Dobby_]

@stephenw10 said in Error messages pfSense+ 24.03 BETA:

Hmm if you run pfSense-upgrade -c then run pkg update does it succeed?

pfSense-upgrade -c

[24.03-BETA][root@xxx.xxx]/root: pfSense-upgrade -c
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: failed to read the installed pfSense packages
>>> Updating repositories metadata...done.
Your system is up to date

Was not running nice

pkg update

[24.03-BETA][root@xxx.xxx]/root: pkg update
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
pfSense repository is up to date.
All repositories are up to date.

But now this is running false free

[stephenw10]

Yeah OK. That's mostly what I see. There's bug there. We are looking into it.

[Dobby_]

@stephenw10 said in Error messages pfSense+ 24.03 BETA:

Yeah OK. That's mostly what I see. There's bug there. We are looking into it.

Thank you very much for the workaround, the pkg is now updated fully
but as shown above the error message is still existing if not pkg but
pfSense-upgrade is used as you can see below.

pkg update

[24.03-BETA][root@xxx.xxx]/root: pkg update
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
pfSense repository is up to date.
All repositories are up to date.

pkg upgrade

[24.03-BETA][root@xxx.xxx]/root: pkg upgrade
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   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.

pfSense-upgrade -c

[24.03-BETA][root@Dockmaster.Heimnetz]/root: pfSense-upgrade -c
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: failed to read the installed pfSense packages
>>> Updating repositories metadata...done.
Your system is up to date

[stephenw10]

What pkg versions do you have?
pkg-static info -x pfSense

[Dobby_]

@stephenw10 said in Error messages pfSense+ 24.03 BETA:

What pkg versions do you have?
pkg-static info -x pfSense

pkg-static info -x pfSense

[24.03-BETA][root@Dockmaster.Heimnetz]/root: pkg-static info -x pfSense
pfSense-24.03.b.20240322.1708
pfSense-Status_Monitoring-php83-1.8_6
pfSense-base-24.03.b.20240322.1708
pfSense-boot-24.03.b.20240322.1708
pfSense-composer-deps-0.1
pfSense-default-config-serial-24.03.b.20240322.1708
pfSense-gnid-0.19
pfSense-kernel-pfSense-24.03.b.20240322.1708
pfSense-pkg-Backup-0.6.1
pfSense-pkg-Cron-0.3.8_4
pfSense-pkg-Filer-0.60.6_8
pfSense-pkg-Lightsquid-3.0.7_4
pfSense-pkg-Notes-0.2.9_5
pfSense-pkg-RRD_Summary-2.2
pfSense-pkg-Shellcmd-1.0.5_3
pfSense-pkg-System_Patches-2.2.9_2
pfSense-pkg-Tailscale-0.1.5
pfSense-pkg-Telegraf-0.9_6
pfSense-pkg-WireGuard-0.2.2_1
pfSense-pkg-acme-0.7.6
pfSense-pkg-bandwidthd-0.7.5
pfSense-pkg-cellular-1.2.3_4
pfSense-pkg-darkstat-3.1.3_6
pfSense-pkg-freeradius3-0.15.10_2
pfSense-pkg-iperf-3.0.5
pfSense-pkg-ipsec-profile-wizard-1.2.1
pfSense-pkg-mailreport-3.6.4_2
pfSense-pkg-ntopng-0.8.13_11
pfSense-pkg-openvpn-client-export-1.9.3
pfSense-pkg-openvpn-client-import-1.2_1
pfSense-pkg-pfBlockerNG-3.2.0_9
pfSense-pkg-snort-4.1.6_16
pfSense-pkg-softflowd-1.2.6_1
pfSense-pkg-squid-0.4.47
pfSense-pkg-squidGuard-1.16.20
pfSense-pkg-stunnel-5.50_11
pfSense-pkg-sudo-0.3_8
pfSense-pkg-suricata-7.0.4_1
pfSense-pkg-syslog-ng-1.16.1
pfSense-pkg-tinc-1.0.35_3
pfSense-pkg-zeek-3.0.6_4
pfSense-repo-24.03.b.20240322.1708
pfSense-repoc-20240322
pfSense-upgrade-1.2.14
php83-pfSense-module-0.97

This is the output I got.

[Dobby_]

@stephenw10

Perhaps this has something to do with it.

[Dobby_]

Near by, it is also occurring in pfSense 2.7.2 version.

pkg upgrade

[2.7.2-RELEASE][root@xxx.xxx]/root: pkg 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.

pkg update

[2.7.2-RELEASE][root@xxx.xxx]/root: pkg update
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.

pfSense-upgrade

[2.7.2-RELEASE][root@xxx.xxx]/root: pfSense-upgrade
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
Messages:
<span style="color: blue">Your device is eligible for pfSense Plus®!</span> Select Upgrade to upgrade.
>>> 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

[stephenw10]

There are two different issues there. The message about pkgs should already be fixed in RC but is harmless, just ugly. The other one we are looking into.

[Dobby_]

@stephenw10

Well good to know!

[stephenw10]

Yup OK this s actually the expected behaviour due to the new branch naming scheme.

When coming from the version version pfSense-repoc -N then it works as expected:

[24.03-BETA][admin@5100-2.stevew.lan]/root: pfSense-repoc -N
[24.03-BETA][admin@5100-2.stevew.lan]/root: pkg update
Updating pfSense-core repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%    2 KiB   1.6kB/s    00:01    
Processing entries: 100%
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
Fetching packagesite.pkg: 100%  192 KiB 197.0kB/s    00:01    
Processing entries: 100%
pfSense repository update completed. 736 packages processed.
All repositories are up to date.

[Dobby_]

@stephenw10

pfSense-repoc -N

[24.03-BETA][root@xxx.xxx]/root: pfSense-repoc -N
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: failed to read the installed pfSense packages

Would be nice to see it here too, but it won`t run as expected.

[stephenw10]

But does that then allow pkg update to run?

[Dobby_]

@stephenw10

Yes, it does false free run through without any error message.
Both systems 24.03 BETA and 2.7.2 are now running fine without
any errors. And the best is, pkg upgrade and pkg update are running
fine again.

[Dobby_]

On 24.03 latest (202404160005) it gores more fast or agile, it produces another error but runs then, like there is no error. (feeled)

[24.03-RC][root@xxx.xxx]/root: pkg upgrade
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
[24.03-RC][root@xxx.xxx]/root: pkg update
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
[24.03-RC][root@xxx.xxx]/root: pfSense-upgrade
pfSense-repoc-static: si_get_packages: failed to run the pkg info command: /usr1
pfSense-repoc-static: failed to read the installed pfSense packages
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 5 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: ...... done
Processing entries: .......... done
pfSense repository update completed. 736 packages processed.
All repositories are up to date.
>>> Setting vital flag on pfSense...done.
Your packages are up to date