PfBlockerNG-devel 2.1.2
-
@jacotec
https://www.reddit.com/r/PFSENSE/comments/8lnugz/pfblockerng_devel_version_released/"Before Installing this version, you must first uninstall the pfBlockerNG Release version (2.1.2_3).
Ensure that you have "Keep Settings" ENABLED so that you do not loose your existing Settings!"
-
@mtarbox said in PfBlockerNG-devel 2.1.2:
@jacotec
https://www.reddit.com/r/PFSENSE/comments/8lnugz/pfblockerng_devel_version_released/"Before Installing this version, you must first uninstall the pfBlockerNG Release version (2.1.2_3).
Ensure that you have "Keep Settings" ENABLED so that you do not loose your existing Settings!"
Thanks for the link
... clear now!Need to think if I try or wait ... I guess the update of the release will work as usual, and that's my main production router here and usually I'm staying at stable ... just the new things are soooooo cool
-
DNSBL keeps beeing async after the upgrade to 2.1.2.
A force reload and disabling the live sync feature won't help.Does anyone have an idea?
-
Did you inspect the logs ?
Maybe go to General Tab and click save, do the same with IP tab and DNSBL tab. This might detect errors in your configuration.Last thing you could try, in General tab, is to untick PfblockerNG Enable and Keep settings then Save, this will clear your database.
Tick the boxes back, Save, then do a Force Reload All. -
This won't work, im still out of sync.
The log can be found here. -
This is because you have twice the Samedi_SecureMecca URL defined in your DNSBL table.
[ Samedi_SecureMecca ] Downloading update [ 05/27/18 10:12:55 ] .. 200 OK. . . . [ Samedi_SecureMecca ] Reload [ 05/27/18 10:13:00 ] . completed .. . . . ---------------------------------------------------------------------- Orig. Unique # Dups # White # TOP1M Final ---------------------------------------------------------------------- 25263 25263 23422 157 0 1684 ---------------------------------------------------------------------- . . . *** DNSBL update [ 1530059 ] [ 1528375 ] ... OUT OF SYNC ! *** [ 05/27/18 10:14:30 ]1530059 - 1528375 = 1684
Header/Label have to be different.
-
Thank you!
I will check this, when i'm at home.Edit:
You where right, somehow i managed to use the same Header/Label on 2 different lists, which caused the error.
Now everything is fine, thank you! -
Iām getting the following error on a semi-regular basis which seems to completely lock up PHP
PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 3990, Message: Call to a member function fetchArray() on boolean
Any ideas? Thanks for the great package
-
This post is deleted! -
Did you uninstall the 2.1.2_3 Version before install the 2.1.2 Dev version?
Did you run a Force Reload All ?What is the status of the pfBlockerNG firewall filter & pfBlockerNG DNSBL service ? Restart the services.
Did you look at the logs files ?
-
Yes. BBCan sent me a git fix to test.
-
Did the package name changed from "2.1.2_2" to 2.2.1"?
I have an update available. -
https://github.com/pfsense/FreeBSD-ports/pull/526
-
Thank you @RonpfS!
-
pfBlockerNG-devel 2.2.1 is now available under 2.3.5-RELEASE-p2
-
Any idea when this new version is going to be a "non-devel" version?
-
@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/pfSenseCrash 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 3842No FreeBSD crash data found.
-
@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
-
@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:20I 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.incand 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#L3842From:
$db_handle->exec("PRAGMA journal_mode = wal;");To:
$db_handle->exec("PRAGMA journal_mode = delete;"); -
@bbcan177 patch applied, will follow-up with results. Thank you BBcan177!!
