Navigation

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

    PHP Error after 2.4.4 upgrade

    Installation and Upgrades
    4
    7
    924
    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.
    • P
      Prometheus23 last edited by

      I am getting this error on my 3100 after the upgrade this morning. Any idea on how to correct it?

      PHP Errors:
      [26-Sep-2018 06:36:24 America/Chicago] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20170718/session.so' - /usr/local/lib/php/20170718/session.so: Undefined symbol "zend_empty_string" in Unknown on line 0
      [26-Sep-2018 06:36:24 America/Chicago] PHP Warning: PHP Startup: bcmath: Unable to initialize module
      Module compiled with module API=20170718
      PHP compiled with module API=20131226
      These options need to match
      in Unknown on line 0

      R 1 Reply Last reply Reply Quote 0
      • jimp
        jimp Rebel Alliance Developer Netgate last edited by

        Where are you seeing this error? If it is in a crash report on the dashboard, clear the report and then restart again. If the error doesn't come back, it was likely a harmless side effect of the upgrade. If it does come back, then some part of the upgrade did not finish completely.

        Fixing it may be as simple as running pfSense-upgrade again from an ssh or console shell. If not, see https://www.netgate.com/docs/pfsense/install/upgrade-troubleshooting.html for some suggestions.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • P
          Prometheus23 last edited by

          It is in the crash report on the dashboard, and I have cleared it and restarted a few times. It will be a few weeks before I can get into that office to try the upgrade from console. Is there a way to force it from the gui?

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

            So the crash report returned after clearing it?

            You can run the command from the console via SSH. However if you're remote from that device you might want to have a recovery plan in place before doing so.

            Steve

            1 Reply Last reply Reply Quote 0
            • P
              Prometheus23 last edited by

              Restarted again this morning and so far the php error is gone. I'll do the reinstall the next time I'm on-site and bring with the install package on usb just in case. Out of the 9 devices I updated yesterday only one (one of the newer ones, a 3100, had an issue). Even one of the older 2440's had no problems, so great job guys.

              1 Reply Last reply Reply Quote 0
              • R
                rgc @Prometheus23 last edited by

                @prometheus23 I have the very same or similar error, you can look at my post verbose regarding the issue. It looks like an API key mismatch maybe a credential key with PFsense NTP daemon 0.pfsense.pool.ntp.org did not get updated or possible maybe need to stop and reinstall the NTP daemon not sure API key mismatch is due to changes in the NTP daemon or other areas in the new 2.4.4 build it defnetly needs to be posted to the bug portal but it might already have been.

                My Netgate 3100 FW and Snort are working fine, on 2.4.4 (balanced) IPS setting for now.

                RECOMENDATIONS (I am not a Netgate engineer or pfsense eng) but this is working for me until the fix the API key.

                I believe this to be a minor error but definitely needs to be fixed.

                (2) possible workarounds:

                (1) reinstalling NTP daemon and then maybe key might match-up again.

                or

                (2) goto the General settings and delete 0.pfsense.pool.ntp.org

                add new pool: 0.us.pool.ntp.org

                Don't forget to go to error page and click delete the bug report.
                The error should NOT return as now your NTP daemon is point to a different NTP pool.

                I have logged out of pfsense and logged back in and no more error, several times to check that this works. (it does)

                so far these changes are working just fine. I hope this helps! If it works for you send me a "like" or whatever kudos we get on this blog.

                Thanks!

                P 1 Reply Last reply Reply Quote 1
                • P
                  Prometheus23 @rgc last edited by

                  @rgc Thanks, that did do the trick.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post