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

    php error after updating 24.03 20240229

    Scheduled Pinned Locked Moved Plus 24.03 Development Snapshots (Retired)
    8 Posts 4 Posters 652 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.
    • H
      High_bounce
      last edited by

      updated pfsense dev 24.03 tonight and now getting this error in system logs:

      /pkg_mgr_install.php: New alert found: PHP ERROR: Type: 1, File: /usr/local/www/pkg_mgr_install.php, Line: 102, Message: Uncaught TypeError: be_active_name(): Argument #1 ($handle) must be of type LibbeHandle, null given in /usr/local/www/pkg_mgr_install.php:102

      system update via ssh showing '/var/db/pkg': not a ZFS filesystem

      Boot Environments "this system does now support Boot Environments." also doesnt show when Environments on boot selection and in ssh only shows the active boot environment

      pkg manger shows no currently active packages but all packages installed before update are still showing in menus and active

      Crash report begins. Anonymous machine information:

      amd64
      15.0-CURRENT
      FreeBSD 15.0-CURRENT #1 plus-devel-main-n256283-eb12ba15e82: Thu Feb 29 03:22:21 UTC 2024 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/4EfTRaIr/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBS

      Crash report details:

      PHP Errors:
      [29-Feb-2024 03:28:29 US/Eastern] PHP Fatal error: Uncaught TypeError: be_active_name(): Argument #1 ($handle) must be of type LibbeHandle, null given in /usr/local/www/pkg_mgr_install.php:102
      Stack trace:
      #0 /usr/local/www/pkg_mgr_install.php(102): be_active_name(NULL)
      #1 {main}
      thrown in /usr/local/www/pkg_mgr_install.php on line 102

      No FreeBSD crash data found.

      other than that everything seems to boot and work as intended so hopefully someone can help me fix my issue either rolling back to a previous boot environment or finding a way to update the system to a future update

      cmcdonaldC 1 Reply Last reply Reply Quote 0
      • cmcdonaldC
        cmcdonald Netgate Developer @High_bounce
        last edited by cmcdonald

        @High_bounce

        A new build is cooking to fix that.

        At the loader menu you can select an alternative boot environment.

        https://docs.netgate.com/pfsense/en/latest/backup/zfsbe/loader.html

        Need help fast? https://www.netgate.com/support

        H 1 Reply Last reply Reply Quote 0
        • H
          High_bounce
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • H
            High_bounce
            last edited by

            @cmcdonald

            Thank you! I figured you guys would have it fixed soon but I can not access updates through ssh or GUI and the Boot environment menu is missing from the loader when I boot or I would hand just rolled back when it happened

            1 Reply Last reply Reply Quote 0
            • H
              High_bounce @cmcdonald
              last edited by

              @cmcdonald

              any help fixing this problem? i cant change boot environments for some reason. the option is missing from the loader and GUI and under bectl only shows the active environment the others should be on there because the space is still missing from the hard drive but are not showing. i also cant update via console or GUI

              K 1 Reply Last reply Reply Quote 0
              • K
                kprovost @High_bounce
                last edited by

                @High_bounce The easiest fix may be to manually edit /usr/local/www/pkg_mgr_install.php and comment out or delete line 102. Then upgrade again to get a fixed version.
                That's what I wound up doing when this hit me.

                H 1 Reply Last reply Reply Quote 0
                • K kprovost referenced this topic on
                • H
                  High_bounce @kprovost
                  last edited by

                  @kprovos

                  that did the trick but when i try to update from 24.03.a.20240229.0929 to 24.03.a.20240301.0357 i get a CAM timeout

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    cursixx @High_bounce
                    last edited by

                    @High_bounce yep same cam timeout error here. I tried the other boot environments and get the same message

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.