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

    PFBlockerNG 2.1.1_2 Memory Errors

    Scheduled Pinned Locked Moved pfBlockerNG
    61 Posts 17 Posters 69.1k 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.
    • RonpfSR
      RonpfS
      last edited by

      For those with failed installation. Verify that /var isn't full. The MaxMind database is huge so if you are using a RAM Disk, it might eat up memory that is needed for the pfblockerng.php.

      If disk space is running low, BBcan177 suggest to delete the /var/db/pfblockerng/deny and /var/db/pfblockerng/original folders before installation to free some disk space. This means it will need to redownload all IP feeds after installation.

      Check pfblockerng.log, the system log, Dashboard for crash report, Status Monitoring System Memory.

      Post relevant debug info here.

      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
      • W
        wiz561
        last edited by

        @RonpfS:

        @wiz561:

        I started a thread up over in the pfblocker posting and just letting everybody know that I'm also experiencing very similar memory issues.

        Thismorning when I logged in, I also had a pfsense crash report with the following:

        					Crash report begins.  Anonymous machine information:
        
        amd64
        10.3-RELEASE-p5
        FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016     root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense
        
        Crash report details:
        
        PHP Errors:
        [04-Aug-2016 00:18:40 America/Chicago] PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3868
        [04-Aug-2016 00:18:40 America/Chicago] PHP Stack trace:
        [04-Aug-2016 00:18:40 America/Chicago] PHP   1\. {main}() /etc/rc.start_packages:0
        [04-Aug-2016 00:18:40 America/Chicago] PHP   2\. sync_package() /etc/rc.start_packages:90
        [04-Aug-2016 00:18:40 America/Chicago] PHP   3\. eval() /etc/inc/pkg-utils.inc:631
        [04-Aug-2016 00:18:40 America/Chicago] PHP   4\. sync_package_pfblockerng() /etc/inc/pkg-utils.inc(631) : eval()'d code:3
        [04-Aug-2016 00:18:40 America/Chicago] PHP   5\. array_merge() /usr/local/pkg/pfblockerng/pfblockerng.inc:3868
        
        Filename: /var/crash/minfree
        2048
        

        The php memory should be 512M by default, so setting it in the inc file to 400M might not help.
        Did it fail without any fix to the inc file? Can you try setting the limit to 640M or 768M?
        What do you have for Firewall Maximum Table Entries?

        I'm going to have to do a bit of work this weekend on this and see more.  I can try it and see what happens, but I'm getting concerned about reaching my 2gb memory limit.  I can add more memory, but that requires me to go to the store and I'm kinda lazy…..and cheap.  :)

        Interesting that I too have a similar setup to the one user above.  I'm running it on vmware esxi with Snort (disabled) and OpenVPN.  Granted, I don't have nearly the hardware or setup, but it's interesting that we're both running vmware.

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

          OK…  Now maybe I'll try what others suggested...  :)

          I wiped and reinstalled pfsense tonight and pfblockng is still coming back with that crash and memory errors.  I know others said to adjust the memory but I thought I would give this a try.  Unfortunately, it failed.

          I also had issues with php-fpm having high utilization....so I'm hoping that the wipe/reinstall fixed the issue with that.  Time will tell.

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

            What about posting pfblockerNG, system log, crash report, screen shot of system activity, etc, so we can see what is happening on your setup?

            The crash report you posted earlier tells me you have under 400MB defined.

            PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted

            Did you raise the Firewall Maximum Table Entries ?

            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
            • PerforadoP
              Perforado Rebel Alliance
              last edited by

              Temporary Fix for

              php /usr/local/www/pfblockerng/pfblockerng.php update

              Failing with memory exhaustion:

              edit /usr/local/pkg/pfblockerng/pfblockerng.inc as discussed above:
              …
              pfb_global();
              ini_set('memory_limit', '640M');
              ...

              cp /etc/rc.php_ini_setup /etc/rc.php_ini_setup.BACKUP
              cp /usr/local/etc/php.ini /usr/local/etc/php.ini.BACKUP
              perl -pi -e 's/536870912/671088640/g' /etc/rc.php_ini_setup /usr/local/etc/php.ini

              512 * 1024 * 1024 -> 536870912
              640 * 1024 * 1024 -> 671088640 works for me. maybe your setup needs more :)

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

                @Perforado:

                Temporary Fix for

                php /usr/local/www/pfblockerng/pfblockerng.php update

                Failing with memory exhaustion:

                cp /etc/rc.php_ini_setup /etc/rc.php_ini_setup.BACKUP
                cp /usr/local/etc/php.ini /usr/local/etc/php.ini.BACKUP
                perl -pi -e 's/536870912/671088640/g' /etc/rc.php_ini_setup /usr/local/etc/php.ini

                512 * 1024 * 1024 -> 536870912
                640 * 1024 * 1024 -> 671088640 works for me. maybe your setup needs more :)

                There is probably a setting (memory_limit?) we can configure in the System/Advanced/System Tunables that will do that for you. But it may require a reboot.

                The fix for the inc file is specific to pfblocker and shouldn't be needed once BBcan177 change the code.

                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
                • PerforadoP
                  Perforado Rebel Alliance
                  last edited by

                  /var/db/aliastables:
                  -rw-r–r--  1 root  wheel    351450 Aug  5 10:56 pfB_Top_v4.txt
                  -rw-r--r--  1 root  wheel  30690970 Aug  5 11:00 pfB_Top_v6.txt

                  cat pfB_Top_v6.txt | wc -l
                  1421351

                  1.4mio entries? That can't be right?

                  cat pfB_Top_v4.txt | wc -l
                    22410

                  Could this be the the root cause of all this?

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

                    @Perforado:

                    /var/db/aliastables:
                    -rw-r–r--  1 root  wheel    351450 Aug  5 10:56 pfB_Top_v4.txt
                    -rw-r--r--  1 root  wheel  30690970 Aug  5 11:00 pfB_Top_v6.txt

                    cat pfB_Top_v6.txt | wc -l
                    1421351

                    1.4mio entries? That can't be right?

                    cat pfB_Top_v4.txt | wc -l
                      22410

                    Could this be the the root cause of all this?

                    What was the size of pfB_Top_v6.txt before the MaxMind db change ?  I do not use these table, so I can't compare.

                    On option BBcan177 mentioned was that he might need to aggregate the table  to shrink them.

                    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
                    • PerforadoP
                      Perforado Rebel Alliance
                      last edited by

                      pfB_Top_v6 was about 13000-ish before as far as i recall.

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

                        @RonpfS:

                        What about posting pfblockerNG, system log, crash report, screen shot of system activity, etc, so we can see what is happening on your setup?

                        The crash report you posted earlier tells me you have under 400MB defined.

                        PHP Fatal error:  Allowed memory size of 402653184 bytes exhausted

                        Did you raise the Firewall Maximum Table Entries ?

                        I've been busy the past couple of days and blowing it away and restoring the config was pretty simple.  I'm going to try to work on this a bit more this week and take the suggestions of what others have posted to see if it fixes it.  I am going to guess that changing the memory settings around will help, but I also need to buy more memory for my system.

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

                          Hi,

                          I've been reading this forum and trying to figure out if there is a fix for this or not. I really didn't see anyone say "This is the fix" with instructions.

                          Can someone point me in the right direction?
                          Has anyone contacted the package creator?
                          Why hasn't anyone pulled this package from being install if there is issues with it?

                          They should pull this package if its not working. It pretty much killed my pfsense box and I had to remove it.

                          Sorry for being so direct. But I just had to shut down my firewall ports to my websites and I'm trying to get this fixed as soon as possible so I can bring them back online.

                          Thanks,
                          Rick

                          1 Reply Last reply Reply Quote 0
                          • D
                            duanes
                            last edited by

                            Me Too…..
                            (NOTE - malloc failure still shows 512mb of ram.  My mem limit seems to be ignored)

                            I'm using
                            pfb_global();
                            ini_set('memory_limit', '4096M');

                            Still fails when updating with....

                            amd64
                            10.3-RELEASE-p5
                            FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016    root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense

                            Crash report details:

                            PHP Errors:
                            [08-Aug-2016 07:47:51 America/Chicago] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3876
                            [08-Aug-2016 07:47:51 America/Chicago] PHP Stack trace:
                            [08-Aug-2016 07:47:51 America/Chicago] PHP  1. {main}() /usr/local/www/pfblockerng/pfblockerng.php:0
                            [08-Aug-2016 07:47:51 America/Chicago] PHP  2. sync_package_pfblockerng() /usr/local/www/pfblockerng/pfblockerng.php:87
                            [08-Aug-2016 07:47:51 America/Chicago] PHP  3. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3876

                            1 Reply Last reply Reply Quote 0
                            • PerforadoP
                              Perforado Rebel Alliance
                              last edited by

                              All the php-scripts spawned by the gui are constrained by the memory-limit set by suhosin. Which is 512MB.

                              That's what my perl-one-liner was for. I even increased the limit to 4GB for testing today …

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

                                @lucasrca:

                                How I solved my problem:…

                                1. Updated Firewall Maximum Table Entries: 4000000 -> 8000000

                                This ended up being the missing link for me. My default was 2M. When Perforado mentioned the count in  /var/db/aliastables/ I checked mine: 4.4M in those lists alone. I bumped my max table entries in System / Advanced / Firewall & NAT from 2M to 10M and pfblockerng started working again.

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

                                  @Perforado:

                                  All the php-scripts spawned by the gui are constrained by the memory-limit set by suhosin. Which is 512MB.

                                  That's what my perl-one-liner was for. I even increased the limit to 4GB for testing today …

                                  For those wandering about suhosin, it is defined in /usr/local/etc/php.ini

                                  ; File generated from /etc/rc.php_ini_setup
                                  output_buffering = "0"
                                  expose_php = Off
                                  implicit_flush = true
                                  magic_quotes_gpc = Off
                                  max_execution_time = 900
                                  request_terminate_timeout = 900
                                  max_input_time = 1800
                                  max_input_vars = 5000
                                  register_argc_argv = On
                                  register_long_arrays = Off
                                  variables_order = "GPCS"
                                  file_uploads = On
                                  upload_tmp_dir = /tmp
                                  upload_max_filesize = 200M
                                  post_max_size = 200M
                                  html_errors = Off
                                  zlib.output_compression = Off
                                  zlib.output_compression_level = 1
                                  include_path = ".:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form"
                                  display_startup_errors=on
                                  display_errors=on
                                  log_errors=on
                                  error_log=/tmp/PHP_errors.log
                                  extension_dir=/usr/local/lib/php/20131226/
                                  date.timezone="America/New_York"
                                  session.hash_bits_per_character = 5
                                  session.hash_function = 1
                                  
                                  ; Extensions
                                  
                                  ; opcache Settings
                                  opcache.enabled="1"
                                  opcache.enable_cli="0"
                                  opcache.memory_consumption="50"
                                  
                                  [suhosin]
                                  suhosin.get.max_array_index_length = 256
                                  suhosin.get.max_vars = 5000
                                  suhosin.get.max_value_length = 500000
                                  suhosin.post.max_array_index_length = 256
                                  suhosin.post.max_vars = 5000
                                  suhosin.post.max_value_length = 500000
                                  suhosin.request.max_array_index_length = 256
                                  suhosin.request.max_vars = 5000
                                  suhosin.request.max_value_length = 500000
                                  suhosin.memory_limit = 536870912
                                  
                                  

                                  Setting 'memory_limit' in the inc file is maxed by the suhosin.memory_limit.

                                  The memory_limit is defined in /etc/inc/config.inc

                                  // Set memory limit to 512M on amd64.
                                  if ($ARCH == "amd64") {
                                  	ini_set("memory_limit", "512M");
                                  } else {
                                  	ini_set("memory_limit", "128M");
                                  }
                                  

                                  So for those using many IPV6 GeoIP table on amd64, they probably have to change /usr/local/etc/php.ini, /etc/rc.php_ini_setup, pfblockerng.inc as well as the Firewall Maximum Table Entries

                                  The php memory issues are not specific to pfBlockerNG, backup crashes when backup size is too big, the Diagnostics/Tables will crash when viewing huge table, etc.

                                  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
                                  • R
                                    richcj10gmail.com
                                    last edited by

                                    I am having similar issues + NAT / routing was not working at all.

                                    error:

                                    
                                    					Crash report begins.  Anonymous machine information:
                                    
                                    amd64
                                    10.3-RELEASE-p5
                                    FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016     root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense
                                    
                                    Crash report details:
                                    
                                    PHP Errors:
                                    [09-Aug-2016 11:27:29 America/New_York] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3875
                                    [09-Aug-2016 11:27:29 America/New_York] PHP Stack trace:
                                    [09-Aug-2016 11:27:29 America/New_York] PHP   1\. {main}() /etc/rc.start_packages:0
                                    [09-Aug-2016 11:27:29 America/New_York] PHP   2\. sync_package() /etc/rc.start_packages:90
                                    [09-Aug-2016 11:27:29 America/New_York] PHP   3\. eval() /etc/inc/pkg-utils.inc:631
                                    [09-Aug-2016 11:27:29 America/New_York] PHP   4\. sync_package_pfblockerng() /etc/inc/pkg-utils.inc(631) : eval()'d code:3
                                    [09-Aug-2016 11:27:29 America/New_York] PHP   5\. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3875
                                    
                                    

                                    I changed the fire wall rule # to 8000000 and added  ini_set("memory_limit", "768M");
                                    I still see the error above. But I at lest have routing back.

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

                                      @richcj10@gmail.com:

                                      I am having similar issues + NAT / routing was not working at all.

                                      error:

                                      
                                      					Crash report begins.  Anonymous machine information:
                                      
                                      amd64
                                      10.3-RELEASE-p5
                                      FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016     root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense
                                      
                                      Crash report details:
                                      
                                      PHP Errors:
                                      [09-Aug-2016 11:27:29 America/New_York] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3875
                                      [09-Aug-2016 11:27:29 America/New_York] PHP Stack trace:
                                      [09-Aug-2016 11:27:29 America/New_York] PHP   1\. {main}() /etc/rc.start_packages:0
                                      [09-Aug-2016 11:27:29 America/New_York] PHP   2\. sync_package() /etc/rc.start_packages:90
                                      [09-Aug-2016 11:27:29 America/New_York] PHP   3\. eval() /etc/inc/pkg-utils.inc:631
                                      [09-Aug-2016 11:27:29 America/New_York] PHP   4\. sync_package_pfblockerng() /etc/inc/pkg-utils.inc(631) : eval()'d code:3
                                      [09-Aug-2016 11:27:29 America/New_York] PHP   5\. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3875
                                      
                                      

                                      I changed the fire wall rule # to 8000000 and added  ini_set("memory_limit", "768M");
                                      I still see the error above. But I at lest have routing back.

                                      Did you fix  /usr/local/etc/php.ini, /etc/rc.php_ini_setup ?

                                      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
                                      • M
                                        marian78
                                        last edited by

                                        same problem:

                                        Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8388608 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3867 Call Stack: 0.0001 245984 1\. {main}() /usr/local/www/pkg_edit.php:0 0.4857 2721392 2\. eval('global $pfb; $pfb['save'] = TRUE; sync_package_pfblockerng();') /usr/local/www/pkg_edit.php:253 0.4857 2722328 3\. sync_package_pfblockerng() /usr/local/www/pkg_edit.php(253) : eval()'d code:3 3.9159 5449944 4\. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3867 PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 3867, Message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 8388608 bytes)
                                        

                                        Crash report begins.  Anonymous machine information:

                                        amd64
                                        10.3-RELEASE-p5
                                        FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016    root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense

                                        Crash report details:

                                        PHP Errors:
                                        [10-Aug-2016 12:50:00 Europe/Bratislava] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 8388608 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3867
                                        [10-Aug-2016 12:50:00 Europe/Bratislava] PHP Stack trace:
                                        [10-Aug-2016 12:50:00 Europe/Bratislava] PHP  1. {main}() /usr/local/www/pkg_edit.php:0
                                        [10-Aug-2016 12:50:00 Europe/Bratislava] PHP  2. eval() /usr/local/www/pkg_edit.php:253
                                        [10-Aug-2016 12:50:00 Europe/Bratislava] PHP  3. sync_package_pfblockerng() /usr/local/www/pkg_edit.php(253) : eval()'d code:3
                                        [10-Aug-2016 12:50:00 Europe/Bratislava] PHP  4. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3867
                                        [10-Aug-2016 12:54:33 Europe/Bratislava] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 8388608 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3867
                                        [10-Aug-2016 12:54:33 Europe/Bratislava] PHP Stack trace:
                                        [10-Aug-2016 12:54:33 Europe/Bratislava] PHP  1. {main}() /usr/local/www/pkg_edit.php:0
                                        [10-Aug-2016 12:54:33 Europe/Bratislava] PHP  2. eval() /usr/local/www/pkg_edit.php:253
                                        [10-Aug-2016 12:54:33 Europe/Bratislava] PHP  3. sync_package_pfblockerng() /usr/local/www/pkg_edit.php(253) : eval()'d code:3
                                        [10-Aug-2016 12:54:33 Europe/Bratislava] PHP  4. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3867

                                        pfsense runing in virtual, on HP N54L microserver, 2G RAM, 60G disk, WAN, LAN, DMZ, Wifi, OpenVPN server + client, suricata, pfblocker

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          richcj10gmail.com
                                          last edited by

                                          @RonpfS:

                                          @richcj10@gmail.com:

                                          I am having similar issues + NAT / routing was not working at all.

                                          error:

                                          
                                          					Crash report begins.  Anonymous machine information:
                                          
                                          amd64
                                          10.3-RELEASE-p5
                                          FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016     root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense
                                          
                                          Crash report details:
                                          
                                          PHP Errors:
                                          [09-Aug-2016 11:27:29 America/New_York] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3875
                                          [09-Aug-2016 11:27:29 America/New_York] PHP Stack trace:
                                          [09-Aug-2016 11:27:29 America/New_York] PHP   1\. {main}() /etc/rc.start_packages:0
                                          [09-Aug-2016 11:27:29 America/New_York] PHP   2\. sync_package() /etc/rc.start_packages:90
                                          [09-Aug-2016 11:27:29 America/New_York] PHP   3\. eval() /etc/inc/pkg-utils.inc:631
                                          [09-Aug-2016 11:27:29 America/New_York] PHP   4\. sync_package_pfblockerng() /etc/inc/pkg-utils.inc(631) : eval()'d code:3
                                          [09-Aug-2016 11:27:29 America/New_York] PHP   5\. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3875
                                          
                                          

                                          I changed the fire wall rule # to 8000000 and added  ini_set("memory_limit", "768M");
                                          I still see the error above. But I at lest have routing back.

                                          Did you fix  /usr/local/etc/php.ini, /etc/rc.php_ini_setup ?

                                          What fix?

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

                                            @richcj10@gmail.com:

                                            @RonpfS:

                                            @richcj10@gmail.com:

                                            I am having similar issues + NAT / routing was not working at all.

                                            error:

                                            
                                            					Crash report begins.  Anonymous machine information:
                                            
                                            amd64
                                            10.3-RELEASE-p5
                                            FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 13:29:35 CDT 2016     root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense
                                            
                                            Crash report details:
                                            
                                            PHP Errors:
                                            [09-Aug-2016 11:27:29 America/New_York] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3875
                                            [09-Aug-2016 11:27:29 America/New_York] PHP Stack trace:
                                            [09-Aug-2016 11:27:29 America/New_York] PHP   1\. {main}() /etc/rc.start_packages:0
                                            [09-Aug-2016 11:27:29 America/New_York] PHP   2\. sync_package() /etc/rc.start_packages:90
                                            [09-Aug-2016 11:27:29 America/New_York] PHP   3\. eval() /etc/inc/pkg-utils.inc:631
                                            [09-Aug-2016 11:27:29 America/New_York] PHP   4\. sync_package_pfblockerng() /etc/inc/pkg-utils.inc(631) : eval()'d code:3
                                            [09-Aug-2016 11:27:29 America/New_York] PHP   5\. file() /usr/local/pkg/pfblockerng/pfblockerng.inc:3875
                                            
                                            

                                            I changed the fire wall rule # to 8000000 and added  ini_set("memory_limit", "768M");
                                            I still see the error above. But I at lest have routing back.

                                            Did you fix  /usr/local/etc/php.ini, /etc/rc.php_ini_setup ?

                                            What fix?

                                            @Perforado:

                                            Temporary Fix for

                                            php /usr/local/www/pfblockerng/pfblockerng.php update

                                            Failing with memory exhaustion:

                                            edit /usr/local/pkg/pfblockerng/pfblockerng.inc as discussed above:
                                            …
                                            pfb_global();
                                            ini_set('memory_limit', '640M');
                                            ...

                                            cp /etc/rc.php_ini_setup /etc/rc.php_ini_setup.BACKUP
                                            cp /usr/local/etc/php.ini /usr/local/etc/php.ini.BACKUP
                                            perl -pi -e 's/536870912/671088640/g' /etc/rc.php_ini_setup /usr/local/etc/php.ini

                                            512 * 1024 * 1024 -> 536870912
                                            640 * 1024 * 1024 -> 671088640 works for me. maybe your setup needs more :)

                                            You can edit the files or do the perl command

                                            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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.