Zitat von Gareth Hopkins <[email protected]>:
Zitat von Gareth Hopkins <[email protected]>:
Hi There,
Any ideas ?
Cheers,
Gareth
"Out of memory" is a result of failing to allocate memory so the OS
is not able to service a request it maybe should. This could be a
problem when unbound tries to create sockets because of buffer
space involved. You should carefully check the user limits
regarding sockets/files/memory for the user unbound is running as
and the overall machine limits.
Hi Andreas,
Thanks for the reply.
My question was more related to what caused the out of memory errors
while connectivity to the internet was down and if there is a
workaround available.
Cheers,
Gareth
I'm not the expert but it might be that unbound tried to open a lot of
connections because many servers are unreachable suddenly if you
connectivity is lost, and that might be the reason for "out of memory"
error. So maybe lowering the "outgoing-range" could help or raise the
limits for unbound user and/or use libevent. Also note that some OS
have a 1024 file descriptor limit per process.
outgoing-range: <number>
Number of ports to open. This number of file descriptors can be
opened per thread. Must be at least 1. Default depends on com-
pile options. Larger numbers need extra resources from the oper-
ating system. For performance a a very large value is best, use
libevent to make this possible.
Regards
Andreas
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
