pfBlockerNG - Failed to parse: pfb_py_data.txt

[RobbieTT]

On restart I get a yellow ! on the DNSBL widget, directing me to the py_error.log.

The error log only contains this:

2024-02-29 16:00:25,892|ERROR| [pfBlockerNG]: Failed to parse: pfb_py_data.txt: []
2024-02-29 16:00:44,506|ERROR| [pfBlockerNG]: Failed to parse: pfb_py_data.txt: []

I can delete the log entries and the green tick on the widget will return but a subsequent restart will trigger it again.

24.03.a.20240229.0929

Any ideas to fix this properly?

️

[garyn]

@RobbieTT I do not know the root cause for this issue, but I just posted about a similar issue about the gambling-porn list.

To debug this, ssh into pfsense. The log files are in /var/log/pfblocker. Once you have narrowed down which list is causing the problem, the original lists are downloaded to /var/db/pfblockerng/dnsblorig. The parsed version is then placed in /var/db/pfblockerng/dnsbl, ... so don't bother editing that one because it will be over written. You need to work directory on the pfsense box because the pfsense gui only loads the last 10k lines and, for example, the gambling-porn original list is >200k lines.

Using whatever clues the the error log gives you, search for the error text. From your post, it looks like there are two problem lines. Either comment (#) or delete the problem lines.

Then, follow these steps here to place your list on 'hold' until the root problem is fixed:

https://forum.netgate.com/topic/186505/pfblocker-parse-errors-with-stevenblacklists-gambling-porn

I'm guessing that it would also be useful to report the issue back to the list creator. In my case it was:

https://github.com/StevenBlack/hosts/issues/

Good luck!

[provels]

@RobbieTT
I chased that error once and was caused (for me) by a bad Smart TV block List.

[RobbieTT]

@garyn

I just cannot find what may be causing this. There is little to no information in the error message so I have yet to find what I am targeting. I have manually looked at the (big) lists and didn't notice anything obvious but manual reviews lead to proximity blindness.

Any other ideas how to simplify this hunt?

️

[garyn]

@RobbieTT you've got company, ... google pfb_py_data and you'll see several reddit posts. Reddit seems to imply deleting the log files.?.? My issue was an incorrectly formatted item on one of StevenBlack's lists. So, my assumption that your pfb_py_data.txt error was also and item in a list may have been incorrect.

If this is a list, do you know which source (which distribution) it's coming from? Which lists to you upload?

[Gertjan]

@RobbieTT said in pfBlockerNG - Failed to parse: pfb_py_data.txt:

Any other ideas how to simplify this hunt?

By looking at the file ?!

The format is rather simple, and 'constructed' after the DNSBL you've selected to use. One of them contains a format error not detected by pfBlocker upon construction, but when read back in, it fails.

Start removing one by one your DNSBL feeds, a,d as soon as the errors goes away, you'll know which one to exclude.

Btw : this is what I would do to tackle the issue.

[Gertjan]

@RobbieTT said in pfBlockerNG - Failed to parse: pfb_py_data.txt:

Any other ideas how to simplify this hunt?

By looking at the file ?!

The format is rather simple, and 'constructed' after the DNSBL you've selected. MOst priobably, one of them contains a format error not detected by pfBlocker upon construction, but when read back in, it fails.

Start removing one by one your DNSBL feeds, and as soon as the errors goes away, you'll know which one to exclude.

Btw : this is what I would do to tackle the issue.