Dnsbl_error.log growth rate /size
-
Hi,
Came down this morning to find my 2.4 installation was wedged, after a reboot I saw that the root filesystem was full, the culprit seemed to be a 14G dnsbl_error.log.
I've got the logging option in the DNSBL tab set to disabled but I'm getting, roughly, 200 entries per second written to the dnsbl_error.log - all similar to:
2017-11-09 09:18:37: (configfile-glue.c.694) === start of condition block === 2017-11-09 09:18:37: (configfile-glue.c.350) go parent global/SERVERsocket==0.0.0.0:8443 2017-11-09 09:18:37: (configfile-glue.c.622) 2 (cached) result: true 2017-11-09 09:18:37: (configfile-glue.c.557) HTTP["host"] ( device-metrics-us.amazon.com ) compare to .* 2017-11-09 09:18:37: (configfile-glue.c.615) 3 (uncached) result: trueCan someone point me in the right direction to understand what the apparent error is that is being logged so frequently or, failing that, control the log files growth.
-
Also having this exact same issue, the file filled up all 6GB available on my filesystem. Did you ever figure out what was causing it or how to fix it? Interesting that all of my log was all filled with entries related to "device-metrics-us.amazon.com" as well. Sample of beginning of my log file:
2017-11-02 23:01:44: (log.c.217) server started 2017-11-02 23:07:46: (configfi202018-01-06 20:33:39: (configfile-glue.c.677) === start of condition block === 2018-01-06 20:33:39: (configfile-glue.c.385) 3 global/HTTPhost=~.* not available yet 2018-01-06 20:33:39: (configfile-glue.c.589) 1 (uncached) result: unset 2018-01-06 20:33:39: (configfile-glue.c.677) === start of condition block === 2018-01-06 20:33:39: (configfile-glue.c.531) SERVER["socket"] ( 0.0.0.0:8443 ) compare to 0.0.0.0:8443 2018-01-06 20:33:39: (configfile-glue.c.589) 2 (uncached) result: true 2018-01-06 20:33:39: (configfile-glue.c.677) === start of condition block === 2018-01-06 20:33:39: (configfile-glue.c.342) go parent global/SERVERsocket==0.0.0.0:8443 2018-01-06 20:33:39: (configfile-glue.c.596) 2 (cached) res2018-01-07 17:11:33: (2018-01-07 23:33:32: (configfile-glue.c.677) === start of condition block === 2018-01-07 23:32018-01-08 01:14:13: (configfile-glue.c.677) === start of condition block === 2018-01-08 01:14:13: (configfile-glue.c.531) HTTP["host"] ( device-metrics-us.amazon.com ) compare to .* 2018-01-08 01:14:13: (configfile-glue.c.589) 1 (uncached) result: true 2018-01-08 01:14:13: (configfile-glue.c.677) === start of condition block === 2018-01-08 01:14:13: (configfile-glue.c.596) 2 (cached) result: true 2018-01-08 01:14:13: (configfile-glue.c.677) === start of condition block === 2018-01-08 01:14:13: (configfile-glue.c.342) go parent global/SERVERsocket==0.0.0.0:8443 2018-01-08 01:14:13: (configfile-glue.c.596) 2 (cached) result: true 2018-01-08 01:14:13: (configfile-glue.c.531) HTTP["host"] ( device-metrics-us.amazon.com ) compare to .* 2018-01-08 01:14:13: (configfile-glue.c.589) 3 (uncached) result: true 2018-01-08 03:05:18: (configfile-glue.c.677) === start of condition block === 2018-01-08 03:05:18: (configfile-glue.c.385) 3 global/HTTPhost=~.* not available yet 2018-01-08 03:05:18: (configfile-glue.c.589) 1 (uncached) result: unset 2018-01-08 03:05:18: (configfile-glue.c.677) === start of condition block === 2018-01-08 03:05:18: (configfile-glue.c.531) SERVER["socket"] ( 0.0.0.0:8443 ) compare to 0.0.0.0:8443 2018-01-08 03:05:18: (configfile-glue.c.589) 2 (uncached) result: true 2018-01-08 03:05:18: (configfile-glue.c.677) === start of condition block === 2018-01-08 03:05:18: (configfile-glue.c.342) go parent global/SERVERsocket==0.0.0.0:8443 2018-01-08 03:05:18: (configfile-glue.c.596) 2 (cached) result: true 2018-01-08 03:05:18: (configfile-glue.c.385) 3 global/SERVERsocket==0.0.0.0:8443/HTTPhost=~.* not available yet 2018-01-08 03:05:18: (configfile-glue.c.589) 3 (uncached) result: unset 2018-01-08 03:05:19: (configfile-glue.c.677) === start of condition block === 2018-01-08 03:05:19: (configfile-glue.c.531) HTTP["host"] ( device-metrics-us.amazon.com ) compare to .*
-
In Firewall / pfBlockerNG / Log Browser tab you can delete the file to free disk space. You could also download it to a local drive if you want to keep it.
In Firewall / pfBlockerNG / General tab, there is a setting for log file size.
-
I am having identical problems. It seems like the dnsbl_error.log keeps trying to stay under the file size limit imposed for minutes to hours then something fails and the log file stops clearing just keeps growing and growing until you run out of disk space.
If you just delete the log file with rm -rf from shell access it still grows and eats disk space because the file is locked apparently. So i have been rebooting every day to clear it and regain diskspace so my firewall wont crash.
I figured out today that if you go to Firewall/pfBlockerNG/DNSBL and uncheck "Enable DNSBL", click save. Delete /var/log/pfblockerng/dnsbl_error.log, it actually deletes and regains lost disk space, avoiding a reboot. Then go back to settings and re-enable DNSBL it at least saves a reboot daily? Hope they fix this bug soon because its getting tedious to clean this by hand each day.
The culprit seems to be "HTTP["host"] ( device-metrics-us.amazon.com ) compare to .*"
I am not sure what is causing this, I do have several amazon devices, kindles, fire-tv's etc… They are apparently causing DNSBL to vomit at the rate of 200 lines per second like the gentleman said above? Eventually overloading the clearing function of log management filling the disk.
-
The next release will have a new function to process this log… Just got bogged down since getting back from the holidays... So still working on a couple loose ends... Thanks!
-
You could add these domains to Unbound as a Host override and set them to resolve to 0.0.0.0
Which will bypass DNSBL completely…
-
The next release will have a new function to process this log… Just got bogged down since getting back from the holidays... So still working on a couple loose ends... Thanks!
Awesome, thanks for the work and looking forward to the next release.
-
I can confirm that issue exist, 43GB log file after 8 hours ))
-
I'm seeing this problem now also. Twice now actually, the latest today. I'm now on pfsense 2.4.3-RELEASE and pfBlockerNG 2.1.2_2.
Anyone know if this log growth problem is fixed in 2.1.2_2 or if the next release will include it?
-
I've been having this issue every few days. Last time it filled up in like 3 days? Each time, the /var/log/pfblockerng/dnsbl_error.log file grows to 4.3 GB, which maxes out my Pfsense disk and then causes things to crash and my DNS server to go down.
Problem goes away if I restart pfblockerng service, which automatically clears the log file, and then follow that with a reboot. Unfortunately I cannot really keep constant tabs on the disk usage, so I've simply resorted to keeping the pfblockerng service disabled until this issue gets resolved.
Strangely I've been running pfblockerng for several months now and never had any issues until now.
-
Is there a ticket/bug to track this issue?
-
Is there a ticket/bug to track this issue?
This is fixed in the next major release… Its been submitted and is under review. Once approved it will be published as a "devel" release, followed by a full release shortly after...
