Problem after upgrading to 24.11-RC

m.d.frederiksen · Nov 15, 2024, 6:17 PM

Running on fairly new NetGate 4200 MAX hardware.

Having either packages "pfBlockerNG" or "Zeek" installed triggers this :

Uninstalling both packages removes the problem ..
Re-installing either package will return the error.

Tried reset to factory, re-install everything but the error still returns if either package is installed.

No symptoms of the error observed in the running system, apart from the error-message itself.

Any wizard here that can guide me to a diagnosis / solution ? :-)

stephenw10 · Nov 15, 2024, 9:41 PM

Hmm, so to be clear everything actually runs OK. You just see that error checking for upgrades?

That was a known bug a while back but should be fixed.

If you run pfSense-upgrade -c at the command line do you see the same error?

Or in fact if you run pfSense-repoc -N ?

Steve

stephenw10 · Nov 15, 2024, 9:45 PM

Can't replicate there here so far on other 24.11 installs. Did you see any errors at upgrade?

m.d.frederiksen · Nov 15, 2024, 9:53 PM

@stephenw10

'

m.d.frederiksen · Nov 15, 2024, 9:57 PM

@stephenw10

The upgrade process seems to go smooth, but at next visit to the System->Upgrade menu after upgrade-reboot, it looks like this :

PS: Remote access to happily granted (to your staff, if you feel like researching :-)

stephenw10 · Nov 15, 2024, 10:00 PM

Hmm, OK. Do you see any additional errors if you run that directly?:
pkg-static info -R --raw-format json-compact pfSense-pkg-\*

m.d.frederiksen · Nov 15, 2024, 10:06 PM

@stephenw10

pfSense 24.11 packages.txt

(List too big to quote directly .. Had to upload as attachment).

And no .. I recognize no errors in that list ..

stephenw10 · Nov 15, 2024, 10:10 PM

Hmm, you should probably run that at the real command line. Running through the webgui prompt is not exactly the same.

No errors shown there. I'd expect at least the same errors that repoc hits.

m.d.frederiksen · Nov 15, 2024, 10:14 PM

@stephenw10

It actually WAS from the CLI .. Just "grabbed" to text-file ..

Here is the same thing in the actual CLI :

Not really helpful .. as only the last third is seen, and its formatted like crap.

Thus the prior nicely formatted text-file :-)

stephenw10 · Nov 15, 2024, 10:22 PM

Hmm, still no error though interesting....

m.d.frederiksen · Nov 15, 2024, 10:36 PM

@stephenw10

Agree .. most interesting.

Have spend 5-6 hours working this issue. My ADHD wont let it go :-)

A full restore from USB -- Everything OK

Full upgrade from USB-installation to current online version -- Everything OK

Restoring my backup-XML-file -- Everything OK
(pfSense install all packages, and my setup)

Reboot happens as part of the XML-restore

(Wait for all packages to complete installation as indicated by GUI .. zzz)

Now visit System->Upgrade .. Error is displayed instantly.

BUT .. as mentioned .. The error-message itself is the only indication of a problem.
Everything seems to be working as expected (I am no expert user).

stephenw10 · Nov 15, 2024, 10:41 PM

Check the version of repoc you have. I wonder if it's somehow not upgrading it or pulling in an older version:

[24.11-RC][admin@4860.stevew.lan]/root: pkg info -x pfSense
pfSense-24.11.r.20241112.1813
pfSense-Status_Monitoring-php83-1.8_8
pfSense-base-24.11.r.20241112.1813
pfSense-boot-24.11.r.20241112.1813
pfSense-composer-deps-0.1
pfSense-default-config-serial-24.11.r.20241112.1813
pfSense-gnid-0.20
pfSense-kernel-pfSense-24.11.r.20241112.1813
pfSense-mim-24.11.r.20241112.1813
pfSense-pkg-Netgate_Firmware_Upgrade-23.05.01
pfSense-pkg-System_Patches-2.2.18
pfSense-pkg-WireGuard-0.2.9
pfSense-pkg-aws-wizard-0.12
pfSense-pkg-frr-2.0.2_6
pfSense-pkg-ipsec-profile-wizard-1.2.4
pfSense-pkg-zeek-3.0.6_6
pfSense-repo-24.11.r.20241112.1813
pfSense-repoc-20241031
pfSense-upgrade-1.2.29
php83-pfSense-module-0.99

m.d.frederiksen · Nov 15, 2024, 10:44 PM

@stephenw10

[24.11-RC][admin@bearwall.bearcave.lan]/root: pkg info -x pfSense
pfSense-24.11.r.20241112.1813
pfSense-Status_Monitoring-php83-1.8_8
pfSense-base-24.11.r.20241112.1813
pfSense-boot-24.11.r.20241112.1813
pfSense-composer-deps-0.1
pfSense-default-config-serial-24.11.r.20241112.1813
pfSense-gnid-0.20
pfSense-kernel-pfSense-24.11.r.20241112.1813
pfSense-mim-24.11.r.20241112.1813
pfSense-pkg-Avahi-2.2_6
pfSense-pkg-Backup-0.6.3
pfSense-pkg-Cron-0.3.8_5
pfSense-pkg-Notes-0.2.9_5
pfSense-pkg-Open-VM-Tools-10.1.0_5,1
pfSense-pkg-Service_Watchdog-1.8.7_4
pfSense-pkg-Shellcmd-1.0.5_4
pfSense-pkg-Status_Traffic_Totals-2.3.2_7
pfSense-pkg-System_Patches-2.2.18
pfSense-pkg-Tailscale-0.1.8
pfSense-pkg-Telegraf-0.9_8
pfSense-pkg-WireGuard-0.2.9
pfSense-pkg-acme-0.8_5
pfSense-pkg-bandwidthd-0.7.7
pfSense-pkg-bind-9.18_2
pfSense-pkg-darkstat-3.1.4
pfSense-pkg-haproxy-0.63_9
pfSense-pkg-iperf-3.0.5
pfSense-pkg-nmap-1.4.4_8
pfSense-pkg-node_exporter-0.18.1_5
pfSense-pkg-ntopng-5.6.0_1
pfSense-pkg-nut-2.8.2_4
pfSense-pkg-openvpn-client-import-1.2_3
pfSense-pkg-pfBlockerNG-devel-3.2.1_20
pfSense-pkg-snort-4.1.6_22
pfSense-pkg-softflowd-1.2.6_2
pfSense-pkg-squid-0.5
pfSense-pkg-squidGuard-1.16.23
pfSense-pkg-sudo-0.3_10
pfSense-pkg-suricata-7.0.7_5
pfSense-pkg-syslog-ng-1.16.2
pfSense-pkg-udpbroadcastrelay-1.2.4
pfSense-pkg-zeek-3.0.6_6
pfSense-repo-24.11.r.20241112.1813
pfSense-repoc-20241031
pfSense-upgrade-1.2.29
php83-pfSense-module-0.99
[24.11-RC][admin@bearwall.bearcave.lan]/root:

stephenw10 · Nov 15, 2024, 10:46 PM

Hmm, seems fine too.

I'll keep trying to replicate it.

Are there any other errors shown in the logs?

m.d.frederiksen · Nov 16, 2024, 2:03 AM

@stephenw10

What other log ?

Specifics (cli commands) ?

Can it be my XML-backup that corrupts the system somehow when restoring it ?
I would really hate to have to re-build my setup from scratch :-(

Oh .. and an interesting observation is, that removal of both fpBlockerNG and Zeek fixes the problem.

But .. if ANY other package is installed at a later point - the error returns.

stephenw10 · Nov 16, 2024, 2:03 AM

@m-d-frederiksen said in Problem after upgrading to 24.11-RC:

if ANY other package is installed at a later point - the error returns.

Hmm, that's interesting.

By logs I mean in the main system logs when that command is run. Or when you install a pkg etc.

m.d.frederiksen · Nov 16, 2024, 11:19 AM

@stephenw10

Have looked through all logs available under Status-> System Logs

Nothing pertaining to the issue was found.

And absolutely no malfunctions found anywhere.
Its almost like a “false flag” error-status - if it was an antivirus-product, if you know what I mean ..

EXCEPT .. Checking for updates from CLI (13) fails while error-status is present.

This might be an issue

Thanks for your time.

stephenw10 · Nov 16, 2024, 2:07 PM

Oh how does it fail with menu option 13?

m.d.frederiksen · Nov 16, 2024, 2:13 PM

@stephenw10

I imagine it will have a hard time upgrading packages it cannot retrieve a list for ?!

stephenw10 · Nov 16, 2024, 2:34 PM

Not really, that shouldn't prevent it updating. It should still report you are up to date below that?

It's only failing to compile the list of installed packages for repoc. pkg itself should still work fine.

When we saw this before it was just an ugly artifact. It looks like it is here too.