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

    8200 max updated to 23.01, crashes

    Scheduled Pinned Locked Moved General pfSense Questions
    12 Posts 3 Posters 714 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      It shouldn't happen though. Did the upgrade appear to complete correctly?

      You might check the upgrade log in /conf.

      Steve

      M 1 Reply Last reply Reply Quote 1
      • M
        manilx @stephenw10
        last edited by manilx

        @stephenw10 Yes, it did its thing and then rebooted.

        /conf/upgrade_log.txt shows:

        Updating repositories metadata... done.
        Your system is up to date

        Netgate 8200max

        M 1 Reply Last reply Reply Quote 0
        • M
          manilx @manilx
          last edited by

          @manilx /cf/conf/upgrade_log.latest.txt shows a lot of errors. too long to post here

          Netgate 8200max

          M 1 Reply Last reply Reply Quote 0
          • M
            manilx @manilx
            last edited by

            @manilx upgrade_log.latest.txt

            Netgate 8200max

            M 1 Reply Last reply Reply Quote 0
            • M
              manilx @manilx
              last edited by

              @manilx Should I revert to 22.05 snapshot?

              Netgate 8200max

              M 1 Reply Last reply Reply Quote 0
              • M
                manilx @manilx
                last edited by

                @manilx Actually after a reboot all seems normal and working.

                Netgate 8200max

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

                  Most of the errors in that log are expected due to the PHP version upgrade. The only part that isn't is the pfBlocker errors:

                  Removing pfBlockerNG...
                  Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/pfblockerng/pfblockerng.inc:1013
                  Stack trace:
                  #0 /usr/local/pkg/pfblockerng/pfblockerng.inc(6478): pfb_build_if_list(true, false)
                  #1 /usr/local/pkg/pfblockerng/pfblockerng.inc(9820): sync_package_pfblockerng()
                  #2 /etc/inc/pkg-utils.inc(781) : eval()'d code(1): pfblockerng_php_pre_deinstall_command()
                  #3 /etc/inc/pkg-utils.inc(781): eval()
                  #4 /etc/inc/pkg-utils.inc(1093): eval_once('pfblockerng_php...')
                  #5 /etc/rc.packages(80): delete_package_xml('pfBlockerNG-dev...', 'deinstall')
                  #6 {main}
                    thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 1013
                  PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 1013, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/pfblockerng/pfblockerng.inc:1013
                  Stack trace:
                  #0 /usr/local/pkg/pfblockerng/pfblockerng.inc(6478): pfb_build_if_list(true, false)
                  #1 /usr/local/pkg/pfblockerng/pfblockerng.inc(9820): sync_package_pfblockerng()
                  #2 /etc/inc/pkg-utils.inc(781) : eval()'d code(1): pfblockerng_php_pre_deinstall_command()
                  #3 /etc/inc/pkg-utils.inc(781): eval()
                  #4 /etc/inc/pkg-utils.inc(1093): eval_once('pfblockerng_php...')
                  #5 /etc/rc.packages(80): delete_package_xml('pfBlockerNG-dev...', 'deinstall')
                  #6 {main}
                    thrownpkg-static: DEINSTALL script failed
                  

                  Those are also caused by the PHP change but unlike the others are more than just cosmetic.

                  Reinstalling pfBlocker should resolve it though if anyone else is seeing this.

                  Steve

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    manilx @stephenw10
                    last edited by

                    @stephenw10 Thx!

                    I did uninstalled pfblockerng-dev and install pfblockerng release, which now is the same.

                    Did a reboot and no errors, seems working OK.

                    I have the 22.0.5.1 snapshot, which I can rollback to, uninstall pfblockerng before the update and then update again if need be.

                    Netgate 8200max

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

                      You should be OK from there. It's the uninstall script that fails because of the php change. Installing again after the php upgrade is complete works as expected and restores the correct files/settings.

                      https://redmine.pfsense.org/issues/13680

                      Steve

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        manilx @stephenw10
                        last edited by

                        @stephenw10 Thanks a lot Steve!!!!

                        Netgate 8200max

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