Opened 8 years ago
Closed 6 years ago
#52918 closed defect (invalid)
unbound - warning: too many file descriptors requested
Reported by: | macuserguru | Owned by: | nerdling (Jeremy Lavergne) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.5 |
Keywords: | Cc: | ||
Port: | unbound |
Description (last modified by mf2k (Frank Schima))
Hi, what should I do to resolve this, which entry in unbound.conf should be changed?
are this the right:
# Default is 4096. 65536 disables it. # max-udp-size: 4096
or what else?
Warning message:
$ sudo /opt/local/etc/LaunchDaemons/org.macports.unbound/unbound.wrapper restart Nov 18 16:36:31 unbound[1955:0] warning: too many file descriptors requested. The builtinmini-event cannot handle more than 1024. Config for less fds or compile with libevent Nov 18 16:36:31 unbound[1955:0] warning: continuing with less udp ports: 465
greetings Fritz
Change History (11)
comment:1 Changed 8 years ago by macuserguru
comment:2 Changed 8 years ago by mf2k (Frank Schima)
Keywords: | unbound start warning removed |
---|---|
Owner: | changed from macports-tickets@… to nerdling |
Status: | new → assigned |
Type: | request → defect |
In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers unbound
), if any.
Note that a "request" ticket type is only for requesting a new port.
comment:3 Changed 8 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:4 Changed 8 years ago by ken-cunningham-webuse
looks like you might want to try the +libevent variant
$ port variants unbound unbound has the variants: libevent: Build with libevent (slower, but allows use of large outgoing port ranges)
see also <http://unbound.net/documentation/howto_optimise.html> section on Using Libevent
--hope this helps you. - K
comment:5 Changed 8 years ago by macuserguru
I am not the macports guru, but I think I must adapt the unbound Portfile
But I running unbound on my macbook only for me - which parameter should I change in the unbound.conf?
comment:6 Changed 8 years ago by macuserguru
Now - if I understand right I must reduce
# more outgoing connections # depends on number of cores: 1024/cores - 50 outgoing-range: 950
But I use 2 cores
# more outgoing connections # depends on number of cores: 1024/2 - 50 outgoing-range: 462
comment:7 Changed 8 years ago by macuserguru
And this too?
outgoing-range: 462 num-queries-per-thread: 231
are this right now?
comment:8 Changed 8 years ago by ken-cunningham-webuse
Hi - no idea, sorry. I'm happy to help you with the macports end of things, but you'll need someone who knows how to configure unbound to help you if you need help beyond what is referenced in that URL I listed above.
Although someone here might be able to help you with that (like the port maintainer maybe), you'll probably have more luck on the website where unbound is kept.
For example, I see there is an unbound users mailing list here <http://unbound.net/pipermail/unbound-users/>. Read through there - no doubt this question has been asked and answered 100 times before -- but if not, I'd suggest it would be more efficient to post a question to that list for unbound configuration help.
comment:9 Changed 8 years ago by macuserguru
With
num-treads: 2 outgoing-range: 465 num-queries-per-thread: 256
it works well now.
I - better my MBP - are the only user for unbound. I use my own DNSSEC without forwarders to resolve addresses.
comment:11 Changed 6 years ago by nerdling (Jeremy Lavergne)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Closing as "invalid" since this appears to be specific to a scenario, and the fixes likely should not be forced on all users.
I run the latest macports on El Capitan 10.11.6