Segmentation fault when attempting to upgrade 2.5.2 -> 2.6.0

[mfld]

A small percentage of instances are failing to update.

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 7 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .......... done
Processing entries:
Processing entries............. done
pfSense repository update completed. 511 packages processed.
All repositories are up to date.

**Child process pid=40870 terminated abnormally: Segmentation fault**

**** WARNING ****
Reboot will be required!!

🔒 Log in to view

Rebooting and doing

pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

Did not help. Instance has dual stack IPv4 and IPv6 and DNS resolution is working and unfiltered. Instance is in London so might pull from FRA mirror if that matters.

[mfld]

For anyone finding this:

The instances that failed had zabbix-agent52 installed.

🔒 Log in to view

Manually upgrading to zabbix-agent54 then allowed the 2.5.2 -> 2.6.0 upgrade to proceed and not segfault.

Will file in redmine.

[stephenw10]

Hmm, interesting. They are all coming from 2.5.2?

Do you know what version of the package was installed? The ! there indicates there is an issue with the current install beyond just being out of date. Or was that after the update?

Steve

[SteveITS]

The screenshot shows "zabbix-agent52" not "zabbix-agent54." I think I have seen that ! before when the package isn't available, and it isn't if I look at zabbix packages.

That brings up a process question...we have generally followed the instructions/recommendation to uninstall packages like pfBlocker and Suricata, before upgrading pfSense. The new upgrade process is, "When upgrading to pfSense Plus 22.01 and later versions, the pfSense-upgrade process will forcefully reinstall all operating system packages." If a package isn't available, e.g. "suricata4" was removed from the 3100 package list once "suricata" became available again, will the upgrade know to install/migrate to suricata or fail to install suricata4? Or fail the upgrade because it knows the package isn't available on the new version?

[stephenw10]

Ok, we've replicated that locally and are investigating.

The error shown in the manager is because Zabbix Agent 52 is no longer available.

[mfld]

@steveits well spotted. I'm on mobile. Will edit my OP. I mean to say if you have 2.5.2 and zabbix-agent52 (as in the screenshot) the upgrade to 2.6.0 will segfault.

It's in Redmine now - Bug #12796

[mfld]

@stephenw10 it was before the update.

I upgraded a bunch of instances 2.5.2 -> 2.6.0

The two that failed had one thing in common: they still had zabbix-agent52 whereas the others that upgraded fine already had zabbix-agent54.

As soon as I upgraded zabbix-agent52 to zabbix-agent54 the upgrade to 2.6.0 would proceed and not segfault

Issue now filed.

• Bug #12796

[mfld]

@stephenw10 so much love. Netgate is our Valentine today y'all good people!

[bingo600]

@stephenw10
I'm still on Zabbix server version : Zabbix 5.0.20
As it's LTS.

My pfSense Zabbix agent (2.5.2 CE) is 5.0.11

🔒 Log in to view

I have the possibility of installing Zabbix Agent 5.2 or 5.4 too

🔒 Log in to view

But does the Zabbix agent version relate to the Zabbix server version (i assumed that) ?
Then it's not just a "blind update" to Agent 5.4

/Bingo

[mfld]

@bingo600 you may not encounter the segfault because zabbix-agent5 does exist in the 2.6.0 repo. I think the issue is specific to 2.5.2 with zabbix-agent52

[stephenw10]

Yes, it's only 5.2 that is no longer supported upstream and was removed. The expected behaviour is that the package would simply be removed at upgrade. But that is not the case currently.

So if you have zabbix_agent52 installed it should be removed before upgrading until we get a fix in.

Steve