Enthusiastic logging when interface goes away

Eric Luehrsen ericluehrsen at gmail.com
Thu Oct 4 23:22:42 UTC 2018

> On Thu, Oct 4, 2018, 11:09 AM Mike via Unbound-users 
> <unbound-users at nlnetlabs.nl <mailto:unbound-users at nlnetlabs.nl>> wrote:
>     On 10/4/2018 10:59 AM, Mark Deneen wrote:
>      > I'm guessing that your supervisor process, whether it be systemd,
>     runit,
>      > etc, is repeatedly starting unbound.  Unbound prints this error
>     message,
>      > exits, and then is launched again.
>      >
>     Unbound is running continuously.  I do not see the usual unbound
>     start-up messages in the logs, just that one log message repeated.
>     Maybe something within unbound is restarting an unbound process?  I
>     don't know, which is why I'm asking.  :)
>     I should have added this initially:
>     Unbound Version 1.6.8, running on OpenBSD 6.3 (amd64)

The problem is Unbound logs for each outbound connection it cannot make. 
This is not a restart issue. The solutuon should be in Unbound where 
this message has a burn down timer. When a message is sent, the time is 
recorded and messages are not sent until (config) time later. Pretty 
simple if() gating the syslog call. Default should be 5 minutes as many 
outages are hour or more.

- Eric

More information about the Unbound-users mailing list