Unbound.conf stats_noreset use 20-28%

mikekoke

Hi, after updating to 2.4.5 I often notice this process:
/usr/local/sbin/unbound-control -c /var/unbound/unbound.conf stats_noreset

I restarted because in some moments it came to use 20-28%, now still appears but at 8-10%.
I understood that it concerns the statistics of unbound, but I don't understand why after the update it started to have such a high use.
Thanks.

BBcan177

@mikekoke
If you use pfBlockerNG, upgrade to pfBlockerNG-devel.

mikekoke

@BBcan177 said in Unbound.conf stats_noreset use 20-28%:

@mikekoke
If you use pfBlockerNG, upgrade to pfBlockerNG-devel.

I am already using pfBlockerNG-devel.

BBcan177

@mikekoke
In the dashboard widget you can adjust the time between requests.
Are you on a physical box or virtualized environment?

mikekoke

I'm on a physical box.
Is the value to be changed in the pfblocker widget DNSBL Resolver Query?
Thanks.

BBcan177

@mikekoke
Yes

mikekoke

According to you it is better 10 or 15 having also set up DHCP Registration and Static DHCP.

BBcan177

@mikekoke
https://www.reddit.com/r/pfBlockerNG/comments/bs9zn6/psa_using_pfsense_with_pfblockerng_and_dhcp/

mikekoke

Thanks, I put 10 and i removed DHCP Registration.

mikekoke

Hi, I return to this topic after installing grafana and also after changing the value to 30 the use of nice cpu by dnsbl remains high, with peaks at 50% and beyond every 30 seconds as per the set value.
With 1,700,000 records in dnsbl is this normal?
@BBcan177