Unbound DNS Reporting Stops

[axsdenied]

The report for Unbound (not the logfile) appears to stop functioning until I restart unbound.  DNS resolution still works but the report shows zero queries.

Anyone come across this?

[N00bOner]

Yes - same behavior here.

[axsdenied]

I did find the following in logs and I believe I saw an thread in OCT, with similar issues.  Not sure if this log is actually related as it could be the page for looking at the unbound logs directly?

Code: [Select]

[acb0e85e-47dd-48ac-af18-8a195f12ffd5] Script action failed with Command '/usr/local/opnsense/scripts/unbound/stats.py details --limit '1000'' died with <Signals.SIGABRT: 6>. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 44, in execute subprocess.check_call(script_command, env=self.config_environment, shell=True, File "/usr/local/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/unbound/stats.py details --limit '1000'' died with <Signals.SIGABRT: 6>.

[dinguz]

Same here, and lots of the following messages in the log, every 10-15s or so:

Code: [Select]

2023-12-16T20:53:04 Informational unbound [27616:0] info: dnsbl_module: no logging backend found.
2023-12-16T20:53:04 Informational unbound [27616:0] info: dnsbl_module: attempting to open pipe