New pfblockerNG install Database Sanity check Failed
-
here: running pfSense 2.8.0-RELEASE and pfBlockerNG 3.2.8-dev
Made the suggested change to line 1232.
Still same issue showing DNSBL (unbound mode) out of sync.
Should I revert the channge to ensure that the patch when available works correctly?
Thanks for nay help.
-
I had the same issue
make the suggested change on line 1232
then go to general
uncheck- pfBlockerNG Enable
- Keep Settings Enable
save
wait for it to save
then
check
- pfBlockerNG Enable
- Keep Settings Enable
save
wait for it to save
then
force reload all
-
-
@Laxarus This worked for me as well. Though I had to search the web how to edit the file (the easiest way).
Therefore:
Addition for anyone struggling to find where to edit files on your pfsense system.
Go to Diagnostics --> Edit File --> insert the location of the file:
/usr/local/pkg/pfblockerng/pfblockerng.sh
Go to line number 1232 by filling it in the Go to line field.
That line should read:
s1="$(grep -cv ^${ip_placeholder2}$ ${masterfile})"
replace only (leave the rest intact):
masterfile
to
mastercat
Then follow the above instructions from @Laxarus https://forum.netgate.com/post/1219635
-
-
Ran into this issue today as well running on 25.07.1 with pfblockerNG-devel 3.2.7. Followed the steps outlined in this thread to edit the
pfblockerng.sh
file, then deleted/force reloaded all the lists, and all was well again. Thank you everyone in this thread for your your help and great instructions. -
@BBcan177 said in New pfblockerNG install Database Sanity check Failed:
From:
s1="$(grep -cv ^${ip_placeholder2}$ ${masterfile})"To:
s1="$(grep -cv ^${ip_placeholder2}$ ${mastercat})"Is it possible to update the pfSense package with a bug fix version?
-
FYI, this bug is still present on pfSense v2.8.1-RC and pfBlockerNG-devel v3.2.8
-
-
-
-
Same issue on 25.07.1
pfBlockerNG-devel 3.2.7Database Sanity check [ FAILED ] ** These two counts should match! ** ------------ Masterfile Count [ 26379 ] Deny folder Count [ 26378 ]
-
Thank you BIG Time! I had the same problem with pfBlocker Database mismatch message, and its now fixed...Again, Thanks!
-
pfBlocker been updated tonight, now the Sanity Check Passes without need of patching!
Thanks to the Developer GREAT! Also other bug fixes been applied with the Update!