Re: Unbound swapping

Wouter, Something I just noticed: root@dns:/opt# tail -f unbound.log [1505432173] unbound[53221:4] error: internal error: looping module stopped [1505432173] unbound[53221:4] error: internal error: looping module stopped [1505432173] unbound[53221:4] error: internal error: looping module stopped

Re: Unbound swapping

2017-09-14 5:08 GMT-03:00 W.C.A. Wijngaards via Unbound-users : > Hi Eduardo, Hi Wouter! Thank you for the answer. > I have no real good idea. But looking at your numbers, I see that you > are running a network heavy application, unbound, and it uses about 10G > on

Re: Unbound swapping

Hi Eduardo, I have no real good idea. But looking at your numbers, I see that you are running a network heavy application, unbound, and it uses about 10G on 12G memory. The buff/cache is 2G. Adds up to 12G. And it is swapping. Sounds reasonable, it is maxed out on memory, this is where swap

Unbound swapping

I'm trying to understand why unbound is swapping ~900MB: root@dns:~# top -b -n 1 | grep "SWAP\|unbound" PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ SWAP COMMAND 11991 unbound 20 0 9751036 8.189g 3824 S 81.2 69.9 3192:03 840364 unbound root@dns:~# cat