Bug #16600
open
pfBlockerNG breaks HA XMLRPC sync
100%
Description
tested on:
25.11-RELEASE (amd64)
built on Mon Dec 15 17:04:00 UTC 2025
FreeBSD 16.0-CURRENT
installation of the pfBlockerNG or pfBlockerNG-devel package (current version 3.2.13_1, same for devel) stops the secondary HA node from implementing the changes from the main node during XMLRPC sync
pfBlockerNG doesn't need to be started or have any config - installation breaks the XMLRPC sync config update, deinstallation fixes it immediately
Status_outputs attached for both nodes, after XMLRPC sync initiated from master, one case with no pfb on both nodes, another case with pfb installed on backup node only
Steps to reproduce:
1) enable XMLRPC sync on the master to backup;
2) install pfblockerNG on backup;
3) make the change in firewall rules on master, run the XMLRPC sync - sync event registers on backup but no changes in config
Files
Updated by aleksei prokofiev 1 day ago
Tested on 25.11-RELEASE (amd64)
built on Mon Dec 1 20:59:00 MSK 2025
FreeBSD 16.0-CURRENT
I can confirm this issue.
Updated by Marcos M 1 day ago
- Status changed from Confirmed to Feedback
- Assignee set to Marcos M
- % Done changed from 0 to 100
I've pushed a fix for this and picked it to 25.11.
https://github.com/pfsense/FreeBSD-ports/commit/8a7063600a9397a512423fb65e8d7cf9fd2f5201
Updated by Glenn Hall 1 day ago
After upgrading my system to pfBlockerNG-devel 3.2.13_2, I am now getting the following PHP error at every Cron or Reload update. Also, the pfb_filter service is crashing and must be manually restarted.
Crash report begins. Anonymous machine information:
amd64
16.0-CURRENT
FreeBSD 16.0-CURRENT #41 plus-RELENG_25_11-n256500-a43915e7ef55: Mon Dec 1 19:02:15 UTC 2025 root@pfsense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-Plus-snapshots-25_11-main/obj/amd64/mjYGPXLl/var/jenkins/workspace/pfSe
Crash report details:
PHP Errors:
[22-Dec-2025 18:07:55 America/Detroit] PHP Fatal error: Uncaught TypeError: SQLite3::busyTimeout(): Argument #1 ($milliseconds) must be of type int, string given in /usr/local/pkg/pfblockerng/pfblockerng.inc:6245
Stack trace:
#0 /usr/local/pkg/pfblockerng/pfblockerng.inc(6245): SQLite3->busyTimeout()
#1 /usr/local/pkg/pfblockerng/pfblockerng.inc(5566): pfb_open_sqlite()
#2 /usr/local/pkg/pfblockerng/pfblockerng.inc(1114): pfb_daemon_filterlog()
#3 {main}
thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6245
Updated by Glenn Hall about 23 hours ago
The earlier error was fixed, however I am now getting that same error, but for line 6251 instead of 6245.
@Crash report begins. Anonymous machine information:
amd64
16.0-CURRENT
FreeBSD 16.0-CURRENT #41 plus-RELENG_25_11-n256500-a43915e7ef55: Mon Dec 1 19:02:15 UTC 2025 root@pfsense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-Plus-snapshots-25_11-main/obj/amd64/mjYGPXLl/var/jenkins/workspace/pfSe
Crash report details:
PHP Errors:
[23-Dec-2025 00:00:00 America/Detroit] PHP Fatal error: Uncaught TypeError: SQLite3::busyTimeout(): Argument #1 ($milliseconds) must be of type int, string given in /usr/local/pkg/pfblockerng/pfblockerng.inc:6251
Stack trace:
#0 /usr/local/pkg/pfblockerng/pfblockerng.inc(6251): SQLite3->busyTimeout()
#1 /usr/local/pkg/pfblockerng/pfblockerng.inc(6765): pfb_open_sqlite()
#2 /usr/local/www/pfblockerng/pfblockerng.php(72): pfBlockerNG_clearsqlite()
#3 {main}
thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6251
[23-Dec-2025 00:00:00 America/Detroit] PHP Fatal error: Uncaught TypeError: SQLite3::busyTimeout(): Argument #1 ($milliseconds) must be of type int, string given in /usr/local/pkg/pfblockerng/pfblockerng.inc:6251
Stack trace:
#0 /usr/local/pkg/pfblockerng/pfblockerng.inc(6251): SQLite3->busyTimeout()
#1 /usr/local/pkg/pfblockerng/pfblockerng.inc(6765): pfb_open_sqlite()
#2 /usr/local/www/pfblockerng/pfblockerng.php(68): pfBlockerNG_clearsqlite()
#3 {main}
thrown in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 6251
No FreeBSD crash data found.@