[Unbound-users] Issues with Unbound 1.4.18

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Phil,

On 08/31/2012 01:45 PM, Phil Davies wrote:
> Hi Wouter,
> 
> Thanks for the advice , I've recompiled unbound with debug enabled,
> So I'll wait until the next crash and see if I get any extra
> information. In terms of load these servers are doing about 1400
> queries per second and when they are running handle this with about
> 10-15% CPU.  As for ulimit I haven't changed any defaults.

The default could be small for the data seg size (one Freebsd server
tells me 512M, another 1G).  That could be easily too small for
unbound if you unbound.conf a large cache.  Configuring unbound to use
500 M according to config would use about 1000M in practice (due to
malloc).  Monitor your process size, or check the config file (default
unbound easily fits in the 512Mb default, but then would be a bit
small for the amount of queries per second you get).  I would guess
that you want to use a big chunk of memory of your machine to service
that queryload, multiple GBs, and this does not fit in the default ulimit.

Also, I am interested if unbound prints errors to syslog?  Or the
logfile if you enabled one?

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQQKcpAAoJEJ9vHC1+BF+Npq0P/j2zmuHRVJDwX9b5LBfrmBau
pycRFKlV3ULH98E8DuMRStcW54fha+zZWI1h45tN1/I3XEKHImPOXK5stX4cmzc0
eTHQrMQ16wT5EUrJHiGXLjJ/KtpsfKCrRrreQSKn0vBBOWxI7JU+B1g80xDUTcf0
ob8aSVqoIjRHchj097NAZN4DZl85K0312HX4lwjxjESZf3+YQrZ7S3MZTn5HaNoy
cQ2RGy7in20JXJhIjuXKXym7H4yf7oCFl1ciDxq5jKTLWtVzaNpPL7oKPyk8QfFD
nSb5bpEB28SpJe4TbsUdzoaHxS50HkyQVk2B0I7TiCYGIp2uN/9I+GSaAYluvZy5
Qjn86sOQbDQRXPH+Dn4ycXwoTolcl5s1P8uXrp6PL1kPHq3I0Mg1VRGWIlx2a3/2
8L0jwtC568DKNx7y/YnofEfSM2beUZJ511oUpJC6M44hfns8HQ9KTeQ7GGnfkjWu
D4W+1E6/HnAnQ4qX5a5s6JQtV3N7Qc0XGCglrP2GjYebvPgTCNRdXAk4bcE+OL0J
zwZFxaLu/RlsBQ8GqIkog/QybXDC4pvLdC/M2fXM6wRD16iKDHvlIlfcFMEGnvEP
p/pyCpVE1QktxhfLE1+d0frBd+UrNAH9yfR3Dv53MZPE/4tC8MKt5zTpDHxOjhdD
0UZYACS28VOsX4GILbFk
=K1k7
-----END PGP SIGNATURE-----