[Varnish] #1054: Child not responding to CLI, killing it

Varnish varnish-bugs at varnish-cache.org
Mon May 14 12:43:15 CEST 2012

#1054: Child not responding to CLI, killing it
  Reporter:  scorillo  |        Type:  defect  
    Status:  reopened  |    Priority:  normal  
 Milestone:            |   Component:  varnishd
   Version:  3.0.2     |    Severity:  normal  
Resolution:            |    Keywords:          

Comment(by etherael):

 The iostat output is quite huge but I couldn't see much difference between
 the read / write rates during or after the varnishd restart. I have it
 saved in case you want to analyse it directly.

 root at parrot:~$ varnishadm panic.show
 Child has not panicked or panic has been cleared
 Command failed with error code 300


 I was unable to find a varnishd.core anywhere, following the instructions
 at https://www.varnish-cache.org/trac/wiki/DebuggingVarnish I note that
 the varnishd bin is supposed to be not stripped but the one on this system
 is listed as stripped.

 root at parrot:~$ file /usr/sbin/varnishd
 /usr/sbin/varnishd: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
 dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped

Ticket URL: <https://www.varnish-cache.org/trac/ticket/1054#comment:7>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list