[Unbound-users] Resolving Timeouts/Issues

Wouter Wijngaards wouter at NLnetLabs.nl
Thu Oct 9 11:53:39 UTC 2008

Hash: SHA1

Hi Dave,

Dave Ellis wrote:
> Hey Wouter,
> The timeouts happen as before, except less often and usually after a
> single timeout it'll resolve the host correctly when retrying the 2nd
> time. Either way, everything is quite a bit better. 
> After about 3 minutes from startup the timeouts start. I did notice any
> domain in the cache resolves right away, but if unbound has to query
> another NS server it times out.

> 	num-threads: 8

> And the output of the log when the service is stopped.
> [1223529704] unbound[24517:0] info: service stopped (unbound 1.0.2).
> [1223529704] unbound[24517:0] info: server stats for thread 0: 42804
> queries, 21012 answers from cache, 21792 recursions
> [1223529704] unbound[24517:0] info: server stats for thread 0:
> requestlist max 1031 avg 811.488 exceeded 10926
> [1223529704] unbound[24517:0] info: average recursion processing time
> 2.075908 sec

The max requestlist van 1031 - which is pretty big - it was exceeded
10926 times.  Thus, you are still under-capacity.  I think that explains
the timeouts.

You paste only the statistics for thread 0.  The others are the same?
Or are there no others (?).

Did you recompile without threading? In that case, do you have 1.5g * 8
= 12 Gb memory for all the threads? If not scale back the cache sizes,
otherwise you start swapping and slowing down. Divide the cache size by
8 perhaps.

If you recompiled with libevent, then the memory is not the issue. An in
that case I would suggest trying --with-libevent, and outgoing-range:
2048 and num-queries-per-thread: 2048 to get additional capacity.

Best regards,

Version: GnuPG v1.4.9 (GNU/Linux)


More information about the Unbound-users mailing list