3.2.0_7 issue

JonH

Running 23.09.1 on a sg-5100, recently updated to pfB 3.2.0_7 and now find errors in the desktop widget for dnsbl.
I've cleared the errors but they keep returning, apparently during processing the nightly update that I perform.
2023-12-20 02:35:45,634|ERROR| [pfBlockerNG]: Failed to parse: pfb_py_data.txt: []

That file is 60+ MB so I have not tried to wade through it.

I saw another post from a few weeks ago and that poster (@py) had some entries that match what I have:

12/19/23 03:15:29,EasyPrivacy,solutions.|pages.indigovision.com,||solutions.|pages.indigovision.com^
12/19/23 03:15:34,SFS_Toxic_BD,admin@slotgacor777.click,admin@slotgacor777.click
12/19/23 03:15:35,SFS_Toxic_BD,reachthroughregion.ru\,reachthroughregion.ru\
12/19/23 03:15:35,SFS_Toxic_BD,tacticaldiameter.ru\,tacticaldiameter.ru\
12/20/23 03:15:29,EasyPrivacy,solutions.|pages.indigovision.com,||solutions.|pages.indigovision.com^
12/20/23 03:15:34,SFS_Toxic_BD,admin@slotgacor777.click,admin@slotgacor777.click
12/20/23 03:15:35,SFS_Toxic_BD,reachthroughregion.ru\,reachthroughregion.ru\
12/20/23 03:15:35,SFS_Toxic_BD,tacticaldiameter.ru\,tacticaldiameter.ru\

A lot of the previously mentioned thread seemed to involve vpn. I run openvpn but I am the only client and I haven't been using it for months. It's just sitting there running and waiting to be of service when I need it.

I'd like to know if there is a solution for this.

jrey

@JonH

These are generally caused by errors in the list.. and the lines referenced are being discarded.

Check your reference count in the pfblockerng.log, you will likely find that the list is still loading, just with these entries being excluded.

once the source list is correct the error will go away.

Example

[ SFS_Toxic_BD ]		 Downloading update .. 200 OK.
  ----------------------------------------------------------------------
  Orig.    Unique     # Dups     # White    # TOP1M    Final                
  ----------------------------------------------------------------------
  47449    47448      19         0          0          47429                
  ----------------------------------------------------------------------

12/21/23 07:01:23,SFS_Toxic_BD,admin@slotgacor777.click,admin@slotgacor777.click
12/21/23 07:01:25,SFS_Toxic_BD,reachthroughregion.ru\,reachthroughregion.ru\
12/21/23 07:01:25,SFS_Toxic_BD,tacticaldiameter.ru\,tacticaldiameter.ru\

in the downloaded file you will find the lines referenced in the error

/var/db/pfblockerng/dnsblorig/SFS_Toxic_BD.orig

admarz.com
admin.i5wed.com
admin@slotgacor777.click
adminlette.org
admiraq.site

however in the processed file you won't:

/var/db/pfblockerng/dnsbl/SFS_Toxic_BD.txt

,admarz.com,,0,SFS_Toxic_BD,DNSBL_Malicious
,admin.i5wed.com,,0,SFS_Toxic_BD,DNSBL_Malicious
,adminlette.org,,0,SFS_Toxic_BD,DNSBL_Malicious
,admiraq.site,,0,SFS_Toxic_BD,DNSBL_Malicious

Edit: if I recall correctly the post from @py that I think you are looking at was more about the resolver and dhcp. He has/had other issues not related specifically to the errors here. Cause and effect.

3.2.0_7 is not processing anything different than 3.2.0_6 would have. The one line change between the two releases has nothing to do with processing of files.

JonH

@jrey Thanks. I do confirm that I deleted the log entries for the error and when the cron job for the feeds ran again (0315, once daily) no further errors appeared.

With your explanation I now understand what I am seeing and how to resolve it.