Reporting -> Unbound DNS

[emfabox]

Hello,

for some reason Reporting stops until I restart unbound service - anyone out there with the same issue?

Running on V23-7.5-amd64

Thank you.

[CJ]

That used to happen but it was fixed several versions ago.

What does your unbound config look like?  What are you restarting Unbound for?

[emfabox]

Hm - what files or something else do you need to look at?

Basically I restart unbound to get the reporting back and after a couple hours it"s stops again...

Thank you.

[emfabox]

Sorry - now I got something -> configd.py   [0522a5b3-486c-4aa4-98bf-8de52602e250] Script action failed with Command '/usr/local/opnsense/scripts/unbound/stats.py totals --max '10'' 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 totals --max '10'' died with <Signals.SIGABRT: 6>.

[cookiemonster]

seems some setting(s) are causing the db query to bomb out. Suggest to log as issue in github. Your db file might be needed but is a guess only.