Unbound stats stop working

Started by Ben S, May 22, 2024, 02:03:57 PM

Previous topic - Next topic
Hi,

I'm quite new to OPNsense so hopefully I haven't missed anything obvious here.   I'm running Unbound with statistics enabled, and since updating to 24.1.7 I'm seeing the stats sometimes just stop.  It keeps answering queries just fine.  I didn't notice this on 24.1 but I'd only run it for a few days, however since the upgrade it seems to stop within an hour usually.  Restarting the service will generally get them working again, until they stop again.  I have reset the DNS data since the upgrade, and that didn't help any more than a restart does.

I can see that the timestamp on /var/unbound/data/unbound.duckdb matches the time that the UI graphs stop, so it appears to be a data collection problem and not just a UI display problem.

If I ktrace the /usr/local/opnsense/scripts/unbound/logger.py process then it appears to be doing nothing while the stats are not updating.  If I then restart the service the first line from kdump is

55384 python3.11 RET   flock -1 errno 4 Interrupted system call

which suggests to me it was stuck trying to get a lock on a file, unfortunately it's not clear which file, or why it couldn't get the lock (presumably another process held it, but what/why?)

I've checked /var/log/resolver and there is nothing useful around the time that stats stop.

This is just a home installation so there is not a huge volume of DNS queries being handled, the size of /var/unbound/data/unbound.duckdb is currently only around 2MB after resetting earlier today.

Does anyone have any suggestions of anything else I can check please?  It seems to stop fairly often so I should be able to find out if any suggestions help fairly soon.

Thanks
Ben