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

    Getting crash reports after updating to 2.4.4

    Scheduled Pinned Locked Moved General pfSense Questions
    38 Posts 10 Posters 8.0k 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.
    • nesenseN
      nesense
      last edited by

      I already reinstalled.

      1 Reply Last reply Reply Quote 0
      • W
        wdup
        last edited by wdup

        Experiencing the same issue - had pfBlockerNG-devel installed prior to upgrade from 2.4.3-p1 to 2.4.4. Didn't appear to have any problems during upgrade. Have since uninstalled pfBlockerNG-devel, issue remains.

        R 1 Reply Last reply Reply Quote 0
        • T
          TheNarc
          last edited by

          Same issue here, exact same set of error messages. Output from php -v:

          PHP 7.2.10 (cli) (built: Sep 14 2018 11:32:18) ( NTS )
          Copyright (c) 1997-2018 The PHP Group
          Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
              with Zend OPcache v7.2.10, Copyright (c) 1999-2018, by Zend Technologies
          

          I too had pfBlockerNG-devel installed prior to the upgrade. I haven't tried uninstalling it, but I have noticed that the pfb_filter service isn't running, and if I attempt to start it manually, I can provoke the crash report.

          R 1 Reply Last reply Reply Quote 0
          • nesenseN
            nesense
            last edited by

            I had pfblockerng-devel installed before but I uninstalled it and reinstalled the stable package before updating.

            1 Reply Last reply Reply Quote 0
            • R
              REM
              last edited by

              I have same issue0_1537985459724_pfsence.txt

              jimpJ 1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate @REM
                last edited by

                @rem said in Getting crash reports after updating to 2.4.4:

                I have same issue0_1537985459724_pfsence.txt

                Your upgrade did not complete. It's still referencing old PHP 5.6 items. If you have WAN connectivity, go to an ssh or console shell and run pfSense-upgrade again.

                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!

                R 1 Reply Last reply Reply Quote 0
                • R
                  REM
                  last edited by

                  Thank you, this message after first reboot, if in console i have:
                  Updating pfSense-core repository catalogue...
                  pfSense-core repository is up to date.
                  Updating pfSense repository catalogue...
                  pfSense repository is up to date.
                  All repositories are up to date.
                  Your packages are up to date

                  all ok, safety use?

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

                    If you still receive those errors after a reboot, then something must not be OK. If they went away, then it's fine.

                    If you still have problems, go through some of the suggestions here: https://www.netgate.com/docs/pfsense/install/upgrade-troubleshooting.html

                    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!

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      Ramosel @wdup
                      last edited by

                      @wdupreez said in Getting crash reports after updating to 2.4.4:

                      Experiencing the same issue - had pfBlockerNG-devel installed prior to upgrade from 2.4.3-p1 to 2.4.4. Didn't appear to have any problems during upgrade. Have since uninstalled pfBlockerNG-devel, issue remains.

                      Seeing the EXACT same thing as you. Working with Anthony but it seems to go deeper than pfBNG.

                      1 Reply Last reply Reply Quote 0
                      • R
                        Ramosel @TheNarc
                        last edited by stephenw10

                        @thenarc said in Getting crash reports after updating to 2.4.4:

                        Same issue here, exact same set of error messages. Output from php -v:

                        PHP 7.2.10 (cli) (built: Sep 14 2018 11:32:18) ( NTS )
                        Copyright (c) 1997-2018 The PHP Group
                        Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
                            with Zend OPcache v7.2.10, Copyright (c) 1999-2018, by Zend Technologies
                        

                        I too had pfBlockerNG-devel installed prior to the upgrade. I haven't tried uninstalling it, but I have noticed that the pfb_filter service isn't running, and if I attempt to start it manually, I can provoke the crash report.

                        Same issue here.

                        1 Reply Last reply Reply Quote 0
                        • R
                          Ramosel @jimp
                          last edited by

                          @jimp said in Getting crash reports after updating to 2.4.4:

                          @rem said in Getting crash reports after updating to 2.4.4:

                          I have same issue0_1537985459724_pfsence.txt

                          Your upgrade did not complete. It's still referencing old PHP 5.6 items. If you have WAN connectivity, go to an ssh or console shell and run pfSense-upgrade again.

                          Jim,
                          I too am seeing the same errors. I uninstalled all packages rebooted, then did the "pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade" from the link you sent. System came up clean reinstalled packages as well as the pfBlockerNG devel from Anthony and as soon as I try to start pfb_filter service it provokes a crash report full of PHP errors.

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

                            Does it work as long as you don't install pfBlockerNG? There were a couple changes just merged for it, but I'm not sure it would help what you are seeing. If it works OK until you install pfBlocker, that's probably a topic for a different thread.

                            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!

                            R 1 Reply Last reply Reply Quote 0
                            • R
                              REM @jimp
                              last edited by

                              @jimp i reboot 1 more time, all ok, no this messages.

                              1 Reply Last reply Reply Quote 0
                              • R
                                Ramosel @jimp
                                last edited by

                                @jimp said in Getting crash reports after updating to 2.4.4:

                                Does it work as long as you don't install pfBlockerNG? There were a couple changes just merged for it, but I'm not sure it would help what you are seeing. If it works OK until you install pfBlocker, that's probably a topic for a different thread.

                                Yes, but...
                                I am running his devel code and to the best of my knowledge that is unchanged since before 2.4.4. Worked fine on 2.4.3.

                                1 Reply Last reply Reply Quote 0
                                • BBcan177B
                                  BBcan177 Moderator
                                  last edited by BBcan177

                                  For those on pfBlockerNG-devel, can you confirm the output of these two commands (They should both match):

                                  php -v
                                  
                                  php_pfb -v
                                  

                                  If they don't match:

                                  rm -f /usr/local/bin/php_pfb
                                  ln -s /usr/local/bin/php /usr/local/bin/php_pfb
                                  

                                  And confirm that the two versions match.

                                  "Experience is something you don't get until just after you need it."

                                  Website: http://pfBlockerNG.com
                                  Twitter: @BBcan177ย  #pfBlockerNG
                                  Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                                  W 1 Reply Last reply Reply Quote 1
                                  • T
                                    TheNarc
                                    last edited by

                                    He's done it again! Thanks BBCan. I can confirm that my two versions were different (php_pfb was back at v5.6.31) and after removing it and adding the link, they match. I was also able to start the pfb_filter service, and no more PHP errors.

                                    R 1 Reply Last reply Reply Quote 1
                                    • BBcan177B
                                      BBcan177 Moderator
                                      last edited by

                                      @thenarc said in Getting crash reports after updating to 2.4.4:

                                      He's done it again! Thanks BBCan. I can confirm that my two versions were different (php_pfb was back at v5.6.31) and after removing it and adding the link, they match. I was also able to start the pfb_filter service, and no more PHP errors.

                                      Thanks, but this fix might only be for my beta testers (who use my private package repo) and yes you are one of them ;)

                                      I am curious tho how these versions are for all other devel users?

                                      "Experience is something you don't get until just after you need it."

                                      Website: http://pfBlockerNG.com
                                      Twitter: @BBcan177ย  #pfBlockerNG
                                      Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                                      1 Reply Last reply Reply Quote 0
                                      • R
                                        Ramosel @TheNarc
                                        last edited by

                                        @thenarc said in Getting crash reports after updating to 2.4.4:

                                        He's done it again! Thanks BBCan. I can confirm that my two versions were different (php_pfb was back at v5.6.31) and after removing it and adding the link, they match. I was also able to start the pfb_filter service, and no more PHP errors.

                                        Agreed! unfortunately he helped me fix mine before we documented the versions. Thanks for confirming the differences.
                                        Still unsure how it occured.

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

                                          When you make a hard link (ln without the -s), the link doesn't get removed or changed when the original file is removed. It stays as a separate copy.

                                          So you make a hard link, pkg removes the old copy, leaving the old hard link in place
                                          New php pkg gets installed, it takes the original name, but since the link was hard and not symbolic this does nothing to the old link copy.

                                          That's just how hard links work -- it's a second reference to the exact same file, but the filesystem entry is independent.

                                          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 1
                                          • BBcan177B
                                            BBcan177 Moderator
                                            last edited by

                                            @jimp said in Getting crash reports after updating to 2.4.4:

                                            When you make a hard link (ln without the -s), the link doesn't get removed or changed when the original file is removed. It stays as a separate copy.

                                            Thanks Jim... Posted a PR to fix the symlinks here for pfBlockerNG-devel:
                                            https://github.com/pfsense/FreeBSD-ports/pull/574/files

                                            "Experience is something you don't get until just after you need it."

                                            Website: http://pfBlockerNG.com
                                            Twitter: @BBcan177ย  #pfBlockerNG
                                            Reddit: https://www.reddit.com/r/pfBlockerNG/new/

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