• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Segmentation fault when attempting to upgrade 2.5.2 -> 2.6.0

Scheduled Pinned Locked Moved General pfSense Questions
11 Posts 4 Posters 1.7k Views 3 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    mfld LAYER 8 @mfld
    last edited by mfld Feb 14, 2022, 5:59 PM Feb 14, 2022, 4:46 PM

    For anyone finding this:

    The instances that failed had zabbix-agent52 installed.

    segf3.JPG

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

    Will file in redmine.

    1 Reply Last reply Reply Quote 0
    • S Offline
      stephenw10 Netgate Administrator
      last edited by stephenw10 Feb 14, 2022, 5:10 PM Feb 14, 2022, 5:08 PM

      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

      S M 2 Replies Last reply Feb 14, 2022, 5:50 PM Reply Quote 0
      • S Offline
        SteveITS Rebel Alliance @stephenw10
        last edited by Feb 14, 2022, 5:50 PM

        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?

        Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
        Upvote 👍 helpful posts!

        M 1 Reply Last reply Feb 14, 2022, 5:58 PM Reply Quote 0
        • S Offline
          stephenw10 Netgate Administrator
          last edited by Feb 14, 2022, 5:57 PM

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

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

          M 1 Reply Last reply Feb 14, 2022, 6:03 PM Reply Quote 1
          • M Offline
            mfld LAYER 8 @SteveITS
            last edited by Feb 14, 2022, 5:58 PM

            @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

            1 Reply Last reply Reply Quote 1
            • M Offline
              mfld LAYER 8 @stephenw10
              last edited by Feb 14, 2022, 6:02 PM

              @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
              1 Reply Last reply Reply Quote 1
              • M Offline
                mfld LAYER 8 @stephenw10
                last edited by Feb 14, 2022, 6:03 PM

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

                1 Reply Last reply Reply Quote 0
                • B Offline
                  bingo600
                  last edited by Feb 14, 2022, 6:20 PM

                  @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

                  0e30f16c-5afc-4679-b76f-7f45ed88108a-image.png

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

                  39f950d5-d011-41c4-9f78-c3ec86c49f22-image.png

                  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

                  If you find my answer useful - Please give the post a 👍 - "thumbs up"

                  pfSense+ 23.05.1 (ZFS)

                  QOTOM-Q355G4 Quad Lan.
                  CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                  LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                  M 1 Reply Last reply Feb 14, 2022, 6:22 PM Reply Quote 0
                  • M Offline
                    mfld LAYER 8 @bingo600
                    last edited by Feb 14, 2022, 6:22 PM

                    @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

                    1 Reply Last reply Reply Quote 1
                    • S Offline
                      stephenw10 Netgate Administrator
                      last edited by stephenw10 Feb 14, 2022, 7:10 PM Feb 14, 2022, 7:08 PM

                      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

                      1 Reply Last reply Reply Quote 1
                      • S SteveITS referenced this topic on Feb 14, 2022, 8:36 PM
                      • S SteveITS referenced this topic on Feb 14, 2022, 8:36 PM
                      11 out of 11
                      • First post
                        11/11
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                        This community forum collects and processes your personal information.
                        consent.not_received