Bug #4020
closed
Unbound not compiled with libevent
Added by Chris Buechler about 10 years ago.
Updated about 10 years ago.
Description
It appears Unbound is not being compiled with libevent. With the following in unbound.conf:
num-queries-per-thread: 4096
num-threads: 8
which happens by default on a system with 8 cores, it'll fail to start with:
: unbound -c /var/unbound/unbound.conf
[1416279801] unbound[87054:0] warning: too many file descriptors requested. The builtinmini-event cannot handle more than 1024. Config for less fds or compile with libevent
[1416279801] unbound[87054:0] fatal error: too much tcp. not enough fds.
- Status changed from New to Confirmed
- Status changed from Confirmed to Assigned
- Assignee set to Renato Botelho
Today we are using unbound from base, which has no support for building with libevent. I'll work on moving it to use unbound from ports.
Thats what i wanted to do but Ermal felt that it should be left with base and modify the compile options in base to support using libevent.
Warren Baker wrote:
Thats what i wanted to do but Ermal felt that it should be left with base and modify the compile options in base to support using libevent.
that change, to use ports, was committed awhile back in tools but reverted.
Unbound port built with libevent is marked BROKEN for FreeBSD 10+ due to an issue with capsicum, I reverted the commits to be able to check this problem before the move
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Assigned
- Status changed from Assigned to Feedback
- Status changed from Feedback to Assigned
- Status changed from Assigned to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF