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

    XG-1541 broken after upgrade to 22.05

    Scheduled Pinned Locked Moved General pfSense Questions
    20 Posts 4 Posters 2.4k Views
    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.
    • getcomG
      getcom @SteveITS
      last edited by getcom

      @steveits
      I could successfully install this system after wiping the ZFS meta data with dd (first and last 512k) and restored the last config.

      Now I get this system crash report:

      *Crash report begins. Anonymous machine information:

      amd64
      14.0-CURRENT
      FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:30:29 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/VDZvZksF/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBS

      Crash report details:

      PHP Errors:
      [26-Apr-2023 23:25:14 Europe/Berlin] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/pkg_edit.php:675
      Stack trace:
      #0 {main}
      thrown in /usr/local/www/pkg_edit.php on line 675
      [26-Apr-2023 23:26:18 Europe/Berlin] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/pkg_edit.php:675
      Stack trace:
      #0 {main}
      thrown in /usr/local/www/pkg_edit.php on line 675

      No FreeBSD crash data found.*

      Additionally I cannot start pfblockerNG config. I got this error:

      Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/pkg_edit.php:675 Stack trace: #0 {main} thrown in /usr/local/www/pkg_edit.php on line 675 PHP ERROR: Type: 1, File: /usr/local/www/pkg_edit.php, Line: 675, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/pkg_edit.php:675 Stack trace: #0 {main} thrown

      Any idea?

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @getcom
        last edited by

        @getcom Three seems high for one router, but if you're a partner maybe you mean across all routers? I do not remember the OS versions off the top of my head but 2.4 to 23.01 is probably multiple FreeBSD versions.

        re: the PHP error, does it recur after restarting pfSense again? I seem to recall some Netgate posts about ignoring PHP errors on the first restart, or especially during the upgrade since those are expected as PHP is upgraded and packages are reinstalled.

        "Uncaught TypeError: Cannot access offset of type string on string" is showing up a lot on the forums lately due to the change to PHP 8, and old code that doesn't work in PHP 8. If you install the System Patches package there are quite a lot of patches available already.

        Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        getcomG 1 Reply Last reply Reply Quote 0
        • getcomG
          getcom @SteveITS
          last edited by

          Restarting or reinstalling pfblockerNG does not change anything.
          After deleting pfblockerNG and installing pfblockerNG-devel the error messages related to pfblockerNG are gone.
          As I know the code base of both versions should be identical now.
          Why I got this behavior with the pfblockerNG version and not with the pfblockerNG-devel version?
          I assume that if the system is upgrated, up & running, every package which will then be automatically or manually installed will have the correct PHP version, or I'm wrong?

          @steveits : "Three times" means overall of all routers in seven years beginning with pfSense 2.2.6, but surprisingly it is the second time for this system...
          Does it makes sense to install every available patch in "System => Patches", or only if I identify a current problem in the description of a specific patch?

          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @getcom
            last edited by

            @getcom Up to you. Usually I’ve just installed as needed but there are a huge number for 23.01 and a shiny new apply all button so…

            Pre-2.7.2/23.09: 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 restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

            1 Reply Last reply Reply Quote 1
            • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Yes, all of those patches are in 23.05 and well tested. I would also just apply all of them.

              getcomG 1 Reply Last reply Reply Quote 0
              • getcomG
                getcom @stephenw10
                last edited by getcom

                @stephenw10
                Today I checked this box again because of the 23.05 update and got this:

                f4aad3e6-3e19-446c-9559-34abbe850f47-grafik.png

                There was no hardware change on this box which means I have no clue why the Netgate ID should have been changed.
                I assume it has not been changed and this a bug. Can you fix this in your database?

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Please send me the NDI and serial from that box in chat and I'll look into it.

                  getcomG R 2 Replies Last reply Reply Quote 0
                  • getcomG
                    getcom @stephenw10
                    last edited by

                    @stephenw10
                    Thank you.

                    9cbd83bf-4bbb-4a39-b43a-7a236910355b-grafik.png

                    1 Reply Last reply Reply Quote 1
                    • R
                      rcoleman-netgate Netgate @stephenw10
                      last edited by rcoleman-netgate

                      @stephenw10 said in XG-1541 broken after upgrade to 22.05:

                      Please send me the NDI and serial from that box in chat and I'll look into it.

                      Would it be too much to ask you to drop a link to these posts (our devices with new NDIs that need Repo access) to the internal tracking doc? 10337 IIRC.

                      Ryan
                      Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                      Requesting firmware for your Netgate device? https://go.netgate.com
                      Switching: Mikrotik, Netgear, Extreme
                      Wireless: Aruba, Ubiquiti

                      stephenw10S 1 Reply Last reply Reply Quote 1
                      • stephenw10S
                        stephenw10 Netgate Administrator @rcoleman-netgate
                        last edited by

                        @rcoleman-netgate Done

                        R 1 Reply Last reply Reply Quote 1
                        • R
                          rcoleman-netgate Netgate @stephenw10
                          last edited by rcoleman-netgate

                          @stephenw10 Thank you. I know I have eyes on it now... but every entry helps.

                          Ryan
                          Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                          Requesting firmware for your Netgate device? https://go.netgate.com
                          Switching: Mikrotik, Netgear, Extreme
                          Wireless: Aruba, Ubiquiti

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.