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

    Pfsense 2.4 and pfBlockerNG issue.

    Scheduled Pinned Locked Moved
    2.4 Development Snapshots
    5
    15
    4.7k
    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.
    • D
      dcol Banned
      last edited by

      There are issues with using PFsence. Here is a crash dump. Looks like a logging issue. I will turn off all PFblockerNG logging and see if it helps.

      Crash report begins.  Anonymous machine information:

      amd64
      11.0-RELEASE-p3
      FreeBSD 11.0-RELEASE-p3 #178 8fb831d(RELENG_2_4): Fri Nov 11 19:23:26 CST 2016    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense

      Crash report details:

      PHP Errors:
      [12-Nov-2016 13:57:24 America/Phoenix] PHP Warning:  array_map(): Argument #2 should be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
      [12-Nov-2016 13:57:24 America/Phoenix] PHP Stack trace:
      [12-Nov-2016 13:57:24 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
      [12-Nov-2016 13:57:24 America/Phoenix] PHP  2. array_map() /usr/local/www/pfblockerng/pfblockerng_log.php:184
      [12-Nov-2016 13:57:24 America/Phoenix] PHP Warning:  implode(): Argument must be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
      [12-Nov-2016 13:57:24 America/Phoenix] PHP Stack trace:
      [12-Nov-2016 13:57:24 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
      [12-Nov-2016 13:57:24 America/Phoenix] PHP  2. implode() /usr/local/www/pfblockerng/pfblockerng_log.php:184

      1 Reply Last reply Reply Quote 0
      • D
        dcol Banned
        last edited by

        Update - Got another Crash Report. Disabling logs does not fix this issue. PFblockerNG does need some work to run on PFsense 2.4
        I sent the logs to the dev team.

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

          Which log file were you trying to view?

          "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
          • D
            dcol Banned
            last edited by

            I wasn't trying to view logs, most of them don't work, or at least the firewall logs don't work. This was a crash report that hasn't shown up since.

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

              @dcol:

              I wasn't trying to view logs, most of them don't work, or at least the firewall logs don't work. This was a crash report that hasn't shown up since.

              The crash report that you posted above is for the pfBlockerNG Log tab… so it looks like it didn't find a particular log file to view?? If this only happened once than ignore...

              I haven't had any time to load 2.4 and test it out... on the list of things too do...

              Also not the following redmine:
              https://redmine.pfsense.org/issues/6919

              "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
              • D
                dcol Banned
                last edited by

                Just updated to today's version of 2.4.0 and got another PFblockerNG crash report when I forced an update. Forced update again and did not see a crash report. PFblocker does work.

                Crash report begins.  Anonymous machine information:

                amd64
                11.0-RELEASE-p3
                FreeBSD 11.0-RELEASE-p3 #179 8fb831d(RELENG_2_4): Sat Nov 12 21:27:00 CST 2016    root@buildbot2.netgate.com:/builder/ce/tmp/obj/builder/ce/tmp/FreeBSD-src/sys/pfSense

                Crash report details:

                PHP Errors:
                [13-Nov-2016 15:17:17 America/Phoenix] PHP Warning:  array_map(): Argument #2 should be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
                [13-Nov-2016 15:17:17 America/Phoenix] PHP Stack trace:
                [13-Nov-2016 15:17:17 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
                [13-Nov-2016 15:17:17 America/Phoenix] PHP  2. array_map() /usr/local/www/pfblockerng/pfblockerng_log.php:184
                [13-Nov-2016 15:17:17 America/Phoenix] PHP Warning:  implode(): Argument must be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
                [13-Nov-2016 15:17:17 America/Phoenix] PHP Stack trace:
                [13-Nov-2016 15:17:17 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
                [13-Nov-2016 15:17:17 America/Phoenix] PHP  2. implode() /usr/local/www/pfblockerng/pfblockerng_log.php:184
                [13-Nov-2016 15:17:37 America/Phoenix] PHP Warning:  array_map(): Argument #2 should be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
                [13-Nov-2016 15:17:37 America/Phoenix] PHP Stack trace:
                [13-Nov-2016 15:17:37 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
                [13-Nov-2016 15:17:37 America/Phoenix] PHP  2. array_map() /usr/local/www/pfblockerng/pfblockerng_log.php:184
                [13-Nov-2016 15:17:37 America/Phoenix] PHP Warning:  implode(): Argument must be an array in /usr/local/www/pfblockerng/pfblockerng_log.php on line 184
                [13-Nov-2016 15:17:37 America/Phoenix] PHP Stack trace:
                [13-Nov-2016 15:17:37 America/Phoenix] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng_log.php:0
                [13-Nov-2016 15:17:37 America/Phoenix] PHP  2. implode() /usr/local/www/pfblockerng/pfblockerng_log.php:184

                1 Reply Last reply Reply Quote 0
                • D
                  dcol Banned
                  last edited by

                  A note for anyone that applied the forced patch above.
                  You must apply it after every update until it is fixed in 2.4

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

                    Adding the earlyshell-command "touch /etc/inc/xmlrpc.inc" in the shellcmd package seems to keep things happy relatively easy.. Sync wont work though, but i don't expect it will with the fetch either though.

                    1 Reply Last reply Reply Quote 0
                    • D
                      dcol Banned
                      last edited by

                      Thanks for that. Installed the Shellcmd package and added the command. Let you know if any problems after the next update.

                      1 Reply Last reply Reply Quote 0
                      • D
                        dcol Banned
                        last edited by

                        That Shellcmd worked great. Updated to the latest dev version 11/19 and had no issues with PFblocker this time.
                        Thanks!

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