Varnish gets in a restart loop and causes the system to lock up; how can I fix?

Posted by chrism2671 on Server Fault See other posts from Server Fault or by chrism2671
Published on 2011-03-02T14:29:10Z Indexed on 2011/03/02 15:27 UTC
Read the original article Hit count: 282

Filed under:

Here is an extract from the syslog.

Mar  2 14:01:10 ip-10-226-34-17 varnishd[20204]: Child (20205) not responding to ping, killing it.
Mar  2 14:01:16 ip-10-226-34-17 varnishd[20204]: Child (20205) not responding to ping, killing it.
Mar  2 14:01:16 ip-10-226-34-17 varnishd[20204]: Child (20205) died signal=3
Mar  2 14:01:21 ip-10-226-34-17 varnishd[20204]: Child cleanup complete
Mar  2 14:01:21 ip-10-226-34-17 varnishd[20204]: child (13224) Started
Mar  2 14:01:21 ip-10-226-34-17 varnishd[20204]: Child (13224) said Closed fds: 4 5 6 10 11 13 14
Mar  2 14:01:21 ip-10-226-34-17 varnishd[20204]: Child (13224) said Child starts
Mar  2 14:01:21 ip-10-226-34-17 varnishd[20204]: Child (13224) said managed to mmap 536870912 bytes of 536870912
Mar  2 14:01:21 ip-10-226-34-17 varnishd[20204]: Child (13224) said Ready
Mar  2 14:01:35 ip-10-226-34-17 varnishd[20204]: Child (13224) not responding to ping, killing it.
Mar  2 14:02:10 ip-10-226-34-17 last message repeated 7 times
Mar  2 14:03:15 ip-10-226-34-17 last message repeated 13 times
Mar  2 14:03:20 ip-10-226-34-17 varnishd[20204]: Child (13224) not responding to ping, killing it.
Mar  2 14:05:53 ip-10-226-34-17 varnishd[20204]: Child (13224) not responding to ping, killing it.
Mar  2 14:05:53 ip-10-226-34-17 varnishd[20204]: Child (13224) not responding to ping, killing it.
Mar  2 14:05:53 ip-10-226-34-17 varnishd[20204]: Child (13224) died signal=3
Mar  2 14:05:53 ip-10-226-34-17 varnishd[20204]: Child cleanup complete
Mar  2 14:05:53 ip-10-226-34-17 varnishd[20204]: child (13288) Started

I'm not expecting a solution here but any help just to decode what each line is doing would be very instructive.

Many thanks!

© Server Fault or respective owner

Related posts about varnish