Swap exceed & Child not responding to CLI, killing it

Lasse Karstensen lkarsten at varnish-software.com
Fri Jun 21 11:07:47 CEST 2013

On Thu, Jun 20, 2013 at 09:21:00AM +0200, Hans Schou wrote:
> I have just recently upgraded to Varnish 3.0.2 64bit Debian Squeeze
> on a new server an encounter some problems Ive not seen before.
> There is 32G physical RAM and I use a 50G backend storage file.
> # ps -eo rss,vsz,comm,cmd | grep varnishd
> 32439516 96968568 varnishd   /usr/sbin/varnishd -P
> /var/run/varnishd.pid -a :80,:8080 -T localhost:6082 -f
> /etc/varnish/default.vcl -s
> file,/var/lib/varnish/v02/varnish_storage.bin,50G -t 0 -p
> sess_workspace 262144 -p thread_pool_min 200 -p thread_pool_max 4000
> -p thread_pool_add_delay 2 -p session_linger 100

Why is your Varnish using 96GB virtual memory?

Please post more information. varnishstat -1 output and some VCL.

> After running 8-10 hours the server is starting to using swap. When
> swapping increases to about 40% the server becomes slow and it ends
> up with a kill in syslog:
> varnishd[7632]: Child (31696) not responding to CLI, killing it.
> varnishd[7632]: Child (31696) died signal=3

You can increase cli_timeout to stop the management process from killing the
child. Of course this is to keep your cached content slightly longer, your website
will be slow/dead while linux arranges its fingers/toes.

With regards,
Lasse Karstensen
Varnish Software AS

More information about the varnish-misc mailing list