Maintained by: NLnet Labs

[Unbound-users] TCP random timeouts

W.C.A. Wijngaards
Tue Nov 30 15:48:55 CET 2010

Hash: SHA1

Hi Thomas,

On 11/29/2010 01:20 AM, Thomas Guthmann wrote:
>> Since you did not compile with libevent, you do have a limit there,
>> certainly as compared to your 950 outgoing-range.  If you used libevent,
>> you could simply state the number you want (it takes about 65k for every
>> buffer); so 100 or 200 would be a lot.
> How did you know/notice that libevent wasn't working ? Because I thought
> I was using it...

Then this should not be a problem, just increase your incoming-num-tcp.

> Indeed when I increased num-tcp unbound complained about the 1024 files
> limit so obviously libevent is not used... But based on unbound -h and
> ldd output it looks like it is linked with libevent.

What was the complaint?  Perhaps it complained about having to increase
the ulimit?  Otherwise, it should not complain if you have libevent (and
it looks like it works).  ulimit -n shows the number of file descriptors
that you allow; unbound tries to increase it (if it has root powers) if
you configure it to use lots.

> Did I miss the documentation part "how to enable libevent in
> unbound.conf ?" Should I use more than one thread or is it a bug with
> old EL5 libraries ?

No, it should just work,

> linked libs: libevent 1.4.13-stable (it uses epoll),

> => /usr/lib/ (0x009fd000)

Looks fine,

Best regards,
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora -