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

    PfBlockerNG-devel 2.1.2

    Scheduled Pinned Locked Moved pfBlockerNG
    47 Posts 14 Posters 14.5k 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.
    • ForsakedF
      Forsaked
      last edited by Forsaked

      Thank you @RonpfS!

      pfSense: 2.4.3

      System: QOTOM-Q355G4
      CPU: Intel Core i5-5250U
      RAM: 8GB SK Hynix DDR3L-1600
      LAN: Intel I211-AT
      SSD: 256GB Lite-On

      1 Reply Last reply Reply Quote 1
      • RonpfSR
        RonpfS
        last edited by RonpfS

        pfBlockerNG-devel 2.2.1 is now available under 2.3.5-RELEASE-p2 😀

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        1 Reply Last reply Reply Quote 2
        • B
          bbrendon
          last edited by

          Any idea when this new version is going to be a "non-devel" version?

          B 1 Reply Last reply Reply Quote 0
          • ?
            A Former User
            last edited by

            @BBcan177 Hitting this on a pretty consistent basis:

            Crash report begins. Anonymous machine information:

            amd64
            11.2-RELEASE
            FreeBSD 11.2-RELEASE #24 5bbe95e97b4(factory-RELENG_2_4_4): Mon Jul 2 12:46:48 EDT 2018 root@buildbot3:/builder/crossbuild-master/pfSense/tmp/obj/builder/crossbuild-master/pfSense/tmp/FreeBSD-src/sys/pfSense

            Crash report details:

            PHP Errors:
            [05-Jul-2018 12:59:04 America/New_York] PHP Warning: SQLite3::exec(): database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3842
            [05-Jul-2018 13:00:48 America/New_York] PHP Warning: SQLite3::exec(): database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3845
            [05-Jul-2018 13:00:48 America/New_York] PHP Warning: SQLite3::query(): Unable to prepare statement: 5, database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3923
            [05-Jul-2018 13:02:33 America/New_York] PHP Warning: SQLite3::exec(): database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3842
            [05-Jul-2018 13:04:18 America/New_York] PHP Warning: SQLite3::exec(): database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3845
            [05-Jul-2018 13:04:18 America/New_York] PHP Warning: SQLite3::prepare(): Unable to prepare statement: 5, database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3957
            [05-Jul-2018 13:04:18 America/New_York] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3958
            [05-Jul-2018 13:06:04 America/New_York] PHP Warning: SQLite3::exec(): database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3842

            No FreeBSD crash data found.

            ? 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @A Former User
              last edited by

              @netgate-james Also this in Alerts

              PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 3958, Message: Call to a member function bindValue() on boolean @ 2018-07-05 13:11:20

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

                @netgate-james said in PfBlockerNG-devel 2.1.2:

                @netgate-james Also this in Alerts
                PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 3958, Message: Call to a member function bindValue() on boolean @ 2018-07-05 13:11:20

                I have only seen this on a few systems. So far the solution has been to change the SQLite3 PRAGMA journal_mode from "wal" to "delete". I haven't had much time to investigate the reason. Before I post a fix, I want to do some additional testing, however; you can test the following:

                If you can edit the file:

                /usr/local/pkg/pfblockerng/pfblockerng.inc
                

                and change the following line 3842
                https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L3842

                From:

                $db_handle->exec("PRAGMA journal_mode = wal;");
                

                To:

                $db_handle->exec("PRAGMA journal_mode = delete;");
                

                "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/

                ? O 2 Replies Last reply Reply Quote 0
                • ?
                  A Former User @BBcan177
                  last edited by

                  @bbcan177 patch applied, will follow-up with results. Thank you BBcan177!!

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User
                    last edited by A Former User

                    @BBcan177 been looking good since applying the change. Apparently this popped up

                    Crash report begins. Anonymous machine information:

                    amd64
                    11.2-RELEASE
                    FreeBSD 11.2-RELEASE #28 5bbe95e97b4(factory-RELENG_2_4_4): Thu Jul 5 00:38:07 EDT 2018 root@buildbot3:/builder/crossbuild-master/pfSense/tmp/obj/builder/crossbuild-master/pfSense/tmp/FreeBSD-src/sys/pfSense

                    Crash report details:

                    PHP Errors:
                    [06-Jul-2018 10:41:38 America/New_York] PHP Warning: SQLite3::exec(): database is locked in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3842

                    No FreeBSD crash data found.

                    No adverse behavior observed thus far.

                    Edit: Had another two of these same crash reports generate.

                    Edit: make that three .. still no adverse side-effects though.

                    1 Reply Last reply Reply Quote 0
                    • V
                      vladimirlind
                      last edited by

                      Pfsense (latest dev snap) keeps crashing with this warning on "Update" webgui tab :

                      Warning: Use of undefined constant pfb_status - assumed 'pfb_status' (this will throw an Error in a future version of PHP) in /usr/local/www/pfblockerng/pfblockerng_update.php on line 385 Warning: Use of undefined constant pfb_output - assumed 'pfb_output' (this will throw an Error in a future version of PHP) in /usr/local/www/pfblockerng/pfblockerng_update.php on line 392

                      1 Reply Last reply Reply Quote 0
                      • V
                        vladimirlind
                        last edited by

                        Here is the crashreport I caught:

                        Crash report begins. Anonymous machine information:

                        arm
                        11.2-RELEASE
                        FreeBSD 11.2-RELEASE #2 3f33035c36f(factory-RELENG_2_4_4): Tue Jul 10 15:36:43 EDT 2018 root@buildbot3:/builder/crossbuild-master/obj/armv6/C5dYt69Q/arm.armv6/builder/crossbuild-master/pfSense/tmp/FreeBSD-src/sys/pfSense-SG-3100

                        Crash report details:

                        PHP Errors:
                        [11-Jul-2018 15:33:20 Europe/Moscow] PHP Warning: Illegal string offset 'vip' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 1128
                        [11-Jul-2018 15:33:21 Europe/Moscow] PHP Warning: Illegal string offset 'vtype' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6320
                        [11-Jul-2018 15:33:21 Europe/Moscow] PHP Warning: Illegal string offset 'key' in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6321
                        [11-Jul-2018 15:33:23 Europe/Moscow] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6995
                        [11-Jul-2018 15:33:23 Europe/Moscow] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6995
                        [11-Jul-2018 15:33:23 Europe/Moscow] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6995
                        [11-Jul-2018 15:33:23 Europe/Moscow] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 7000
                        [11-Jul-2018 15:33:23 Europe/Moscow] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 7000
                        [11-Jul-2018 15:33:23 Europe/Moscow] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 7000

                        No FreeBSD crash data found.

                        1 Reply Last reply Reply Quote 0
                        • RonpfSR
                          RonpfS
                          last edited by

                          https://forum.netgate.com/topic/132659/php-warning-illegal-string-offset-vip-in-usr-local-pkg-pfblockerng-pfblockerng-inc-on-line-1128

                          2.4.5-RELEASE-p1 (amd64)
                          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                          1 Reply Last reply Reply Quote 0
                          • O
                            Okijames @BBcan177
                            last edited by

                            @bbcan177

                            amd64
                            11.1-RELEASE-p10
                            FreeBSD 11.1-RELEASE-p10 #13 r313908+293707af843(RELENG_2_4): Thu May 10 15:09:24 CDT 2018 root@buildbot2.netgate.com:/builder/ce-243/tmp/obj/builder/ce-243/tmp/FreeBSD-src/sys/pfSense

                            Crash report details:

                            PHP Errors:
                            [11-Jul-2018 17:37:26 America/Los_Angeles] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 4053
                            [11-Jul-2018 17:37:28 America/Los_Angeles] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3958
                            [11-Jul-2018 17:37:28 America/Los_Angeles] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3958

                            No FreeBSD crash data found.

                            Details: This is on an APU2 and corresponds with (Jul 11 17:37:23 kernel pid 41538 (php), uid 0 inumber 6266 on /var: filesystem full) . I used default pfsense partitioning during installation and /var is 58MB. This on a 256GB mSATA SSD with >200GB free in /. Good times! :)

                            @netgate-james Did changing wal to delete fix the issue for you?

                            ? 1 Reply Last reply Reply Quote 0
                            • ?
                              A Former User @Okijames
                              last edited by

                              @okijames said in PfBlockerNG-devel 2.1.2:

                              @bbcan177

                              amd64
                              11.1-RELEASE-p10
                              FreeBSD 11.1-RELEASE-p10 #13 r313908+293707af843(RELENG_2_4): Thu May 10 15:09:24 CDT 2018 root@buildbot2.netgate.com:/builder/ce-243/tmp/obj/builder/ce-243/tmp/FreeBSD-src/sys/pfSense

                              Crash report details:

                              PHP Errors:
                              [11-Jul-2018 17:37:26 America/Los_Angeles] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 4053
                              [11-Jul-2018 17:37:28 America/Los_Angeles] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3958
                              [11-Jul-2018 17:37:28 America/Los_Angeles] PHP Fatal error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3958

                              No FreeBSD crash data found.

                              Details: This is on an APU2 and corresponds with (Jul 11 17:37:23 kernel pid 41538 (php), uid 0 inumber 6266 on /var: filesystem full) . I used default pfsense partitioning during installation and /var is 58MB. This on a 256GB mSATA SSD with >200GB free in /. Good times! :)

                              @netgate-james Did changing wal to delete fix the issue for you?

                              See: https://forum.netgate.com/post/775962

                              The crashes are fewer and farther between, on a recent (not current) 2.4.4 snap (before php56 went to php72).

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

                                @okijames said in PfBlockerNG-devel 2.1.2:

                                @netgate-james Did changing wal to delete fix the issue for you?

                                If you have already changed "wal" to "delete" and are still experiencing those issues, can you try the following:

                                Delete the sqlite dbs and run a Force Reload - All to rebuild them.

                                rm /var/db/pfblockerng/dnsbl.sqlite*
                                rm /var/db/pfblockerng/dnsbl_cache.sqlite*
                                rm /var/db/pfblockerng/dnsbl_levent.sqlite*
                                

                                "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
                                • O
                                  Okijames @A Former User
                                  last edited by

                                  I have 4GB RAM so increasing /var RAMDISK to see what happens.

                                  O 1 Reply Last reply Reply Quote 0
                                  • O
                                    Okijames @Okijames
                                    last edited by

                                    Holding strong and working great at 26% of 250GB on /var.

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bbrendon @bbrendon
                                      last edited by bbrendon

                                      @bbrendon said in PfBlockerNG-devel 2.1.2:

                                      Any idea when this new version is going to be a "non-devel" version?

                                      I ask because 2.1 has some really annoying bugs. I'm trying to decide how long I should hold out or just install the devel version.

                                      J 1 Reply Last reply Reply Quote 0
                                      • J
                                        jacotec @bbrendon
                                        last edited by

                                        @bbrendon said in PfBlockerNG-devel 2.1.2:

                                        I ask because 2.1 has some really annoying bugs. I'm trying to decide how long I should hold out or just install the devel Version

                                        Same here, I went for the devel 2 weeks ago and I'm happy so far.
                                        Take care to switch the update branch to "unstable" first and grab the devel from there, then you can switch the update branch back to stable (no need to go to unstable with pfSense itself).

                                        Uninstall the 2.1 first, your settings will be preserved. I made a snapshot of my pfSense VM first so I felt really safe ;-)

                                        1 Reply Last reply Reply Quote 0
                                        • 4
                                          4ROMANY
                                          last edited by

                                          I've been having similar issues with this error:
                                          /usr/local/pkg/pfblockerng/pfblockerng.inc: New alert found: PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 3958, Message: Call to a member function bindValue() on boolean.

                                          Been happening for some time - not sure when it started - but I'm currently running 2.4.4-Dev. I made the change that was suggested - changing "wals" to "delete" - so I'll try to report back in a few days. When this PHP issue occurred CPU load for the PHP process would be very high - to the point you could not log in even via serial console. Most of the time you could log in but could not do anything - even reboot seems to hang.

                                          4 1 Reply Last reply Reply Quote 0
                                          • 4
                                            4ROMANY @4ROMANY
                                            last edited by

                                            @4romany

                                            So been about a week now and changing "journal_mode = delete" seems to have fixed my issue.

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