I just took another look at the new unbound reporting (which has been a really nice add) but this time I noticed no activity for several hours (since late last night):
Odd thing is that the OPNsense dashboard was reporting the Unbound service as green.
I restarted the service and reporting resumed as expected.
Here is the reporting view:
https://ibb.co/qMkZ0z8 (https://ibb.co/qMkZ0z8)
I looked at the Unbound log, and found this entry
Quote2023-03-02T19:17:19-
05:00
Error unbound Unable to open pipe. This is likely because Unbound isn't running.
Anyone else have this problem?
Is there a way to get an alert if the service stops working?
I saw the same thing so did a little looking into it and found I was not alone
https://github.com/opnsense/core/issues/6284
It looks like this "might" be fixed in the next release
@xconverger
Hmmm... seems to be a problem with opnsense and unbound, but the error reported in my log is different from the one in the Github issue.
What error message do you see in your log?
(Services: Unbound DNS: Log File)
I just realized the date in my log for when it threw the error was two days ago, so effectively there was no error in the log for when the reporting stopped.
For me unbound keeps working and providing DNS, just the reporting crashed/stopped so it doesnt seem like a big deal to me and I will wait to see what fixes were made as part of those commits. I am not looking into it much more for now as long as unbound keeps working for DNS
Well, it just happened to me for a second time.
Beyond the overview report, I looked a the details and they showed no records being created as well.
At the time, I was in the DCHPv4 Service, making some IP addresses static - I also did that last night so it is perhaps a trigger to the problem??
In any case, I'll keep watching it to see what happens.
Well I confirmed that adding a static ip address stops unbound reporting.
Unbound reporting has been running well for the last few days. However, I just went into the DCHPv4 Service, and made another IP addresses static. Once done, immediately Unbound reporting stopped.
To get it to start again, I went to the dashboard and restarted it.
I guess I will try and find out how to report this as a bug.
There's already a bug reported for it. See this thread.
https://forum.opnsense.org/index.php?topic=32161.0
Thank you and it has been raised on github
https://github.com/opnsense/core/issues/6402