Since we switched from bind to unbound we experienced a problem: after a
few days or weeks or normal working (monitoring stats with a
"unbound-control stats_noreset" command every 5 minutes) unbound-control
stops working: every unbound-control command we issue (apart -v) get no
response and we have to issue a CTRL-C.
Just before it happens, the following error is logged:
Jun 1 22:05:03 aragorn unbound: [15980:3] error: tube msg write failed:
Resource temporarily unavailable
Jun 1 22:05:03 aragorn unbound: [15980:3] fatal error: could not write
stat values over cmd channel
Please note that I have increased the openfiles with:
unbound:\
:openfiles=2048:\
:tc=daemon:
_unbound:*:53:53:unbound:0:0:Unbound Daemon:/var/unbound:/sbin/nologin
I have done a search in Internet and found only a single user reporting
this problem:
https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=752
Please note that this user is using OpenBSD too!
Isn't this really strange?
Maybe this is an OpenBSD specific problem, perhaps related to intensive
use of stats, with some kind of memory/socket leak...?
Thanks.
