unbound generating too many log messages
wouter at nlnetlabs.nl
Tue Jan 19 15:50:07 UTC 2016
-----BEGIN PGP SIGNED MESSAGE-----
On 19/01/16 16:37, Mike via Unbound-users wrote:
> On 1/19/2016 10:20 AM, Taylor R Campbell via Unbound-users wrote:
>> That's irrelevant to the issue Philippe raised. The network is
>> not always available, no matter how well you configure your
>> system or engineer your software. The problem here is that when
>> the network is down, Unbound spews junk to its log as fast as it
> At one point, on this mailing list I documented 20,000 syslog
> messages per second from unbound when the network interface was
> unavailable for a couple of seconds.
> While unbound logging has improved a bit since then, I still see
> far too many essentially duplicate syslog messages for a single
> network unavailable event.
> If I need high volume logging for troubleshooting, I'll increase
> the logging verbosity. Logging should be something that is
> helpful, not something I cringe about.
Is it always the "sendto failed:" error that makes you cringe? That
aren't already squelched by logging verbosity? Is there an errno that
I should also squelch, or should I squelch all errors from the
sendto() system call?
Best regards, Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the Unbound-users