Varnish keeps on crashing on Centos 6

[MAGNIEN, Thierry]

Hi,

Try issuing a "varnishadm panic.show" command and see if it gives you a hint ?

Regards,
Thierry

De : varnish-misc-bounces at varnish-cache.org [mailto:varnish-misc-bounces at varnish-cache.org] De la part de Snels Nick
Envoyé : mardi 4 décembre 2012 10:20
À : varnish-misc at varnish-cache.org
Objet : Varnish keeps on crashing on Centos 6

Hi,

sorry for the double posting. I already posted my problem to the forum, but didn't get any replies. So I'm trying on the mailing list now. As it is a very annoying little problem that wont go away.

My Varnish (3.0.3 revision 9e6a70f) installation crashes regularly on a Centos 6 64bit machine with 8GB RAM (Linux 2.6.32-279.2.1.e16.x86_64) taking down all my websites. I get the following error in /var/log/messages:

Nov 30 04:26:07 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:17 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:27 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:37 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:47 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:53 mail abrt[26160]: File '/usr/sbin/varnishd' seems to be deleted
Nov 30 04:26:53 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:53 mail varnishd[31995]: Child (16991) not responding to CLI, killing it.
Nov 30 04:26:53 mail varnishd[31995]: Child (16991) died signal=3 (core dumped)
Nov 30 04:27:07 mail varnishd[31995]: child (26167) Started
Nov 30 04:27:09 mail varnishd[31995]: Child (26167) said Child starts
Nov 30 04:27:09 mail varnishd[31995]: Child (26167) said SMF.s0 mmap'ed 12884901888 bytes of 12884901888
Nov 30 04:28:33 mail clamd[1289]: SelfCheck: Database status OK.
Nov 30 04:29:30 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:29:40 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:29:50 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:30:00 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:30:10 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:30:20 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:30:30 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:30:33 mail abrt[26219]: File '/usr/sbin/varnishd' seems to be deleted
Nov 30 04:30:33 mail varnishd[31995]: Child (26167) not responding to CLI, killing it.
Nov 30 04:30:33 mail varnishd[31995]: Child (26167) died signal=3 (core dumped)
Nov 30 04:30:34 mail varnishd[31995]: child (26220) Started
Nov 30 04:30:44 mail varnishd[31995]: Pushing vcls failed:#012CLI communication error (hdr)
Nov 30 04:30:44 mail varnishd[31995]: Child (26220) said Child starts
Nov 30 04:30:49 mail varnishd[31995]: Child (26220) said SMF.s0 mmap'ed 12884901888 bytes of 12884901888
Nov 30 04:30:49 mail varnishd[31995]: Child (26220) said Child dies
Nov 30 04:30:49 mail varnishd[31995]: Child (26220) died status=1

I need to manually restart Varnish to get everything up and running again.

I have already issued the command: echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled

But the same crashes keep on happening.

-------- /etc/sysconfig/varnish ------------
NFILES=131072
MEMLOCK=82000
VARNISH_VCL_CONF=/etc/varnish/default.vcl
VARNISH_LISTEN_PORT=80
VARNISH_ADMIN_LISTEN_ADDRESS=127.0.0.1
VARNISH_ADMIN_LISTEN_PORT=8888
VARNISH_SECRET_FILE=/etc/varnish/secret
VARNISH_MIN_THREADS=2
VARNISH_MAX_THREADS=1000
VARNISH_THREAD_TIMEOUT=120
VARNISH_STORAGE_FILE=/var/lib/varnish/varnish_storage.bin
VARNISH_STORAGE_SIZE=12G
VARNISH_STORAGE="file,${VARNISH_STORAGE_FILE},${VARNISH_STORAGE_SIZE}"
VARNISH_TTL=120
DAEMON_OPTS="-a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} \
             -f ${VARNISH_VCL_CONF} \
             -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} \
             -t ${VARNISH_TTL} \
             -w ${VARNISH_MIN_THREADS},${VARNISH_MAX_THREADS},${VARNISH_THREAD_TIMEOUT} \
             -u varnish -g varnish \
             -S ${VARNISH_SECRET_FILE} \
             -s ${VARNISH_STORAGE}"

-------- /etc/varnish/default.vcl ------------
backend default {
  .host = "127.0.0.1";
  .port = "4040";
}
#Enable compression
sub vcl_recv {
  if (req.http.Accept-Encoding) {
    if (req.url ~ "\.(jpg|jpeg|png|gif|gz|tgz|bz2|tbz|mp3|ogg)$") {
      # No point in compressing these
      remove req.http.Accept-Encoding;
    } elsif (req.http.Accept-Encoding ~ "gzip") {
      set req.http.Accept-Encoding = "gzip";
    } elsif (req.http.Accept-Encoding ~ "deflate" && req.http.user-agent !~ "MSIE") {
      set req.http.Accept-Encoding = "deflate";
    } else {
      # unknown algorithm
      remove req.http.Accept-Encoding;
    }
  }
}

Any ideas how I can solve these crashes? Thanks.

Kind regards,

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20121204/de1484ec/attachment.html>