strange restart, taking 15 minutes

Sat Mar 7 18:52:04 CET 2009

Hi,

I've just seen a strange restart that heppened this morning, after only 
about 25 h runtime; apparantly, there was a problem, but the parent 
process needed serveral kill attempts and more than 15 minutes to 
finally restart it's child:

# grep varnish /var/log/syslog
Mar  7 08:52:42 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:52:48 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:52:53 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:52:58 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:03 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:08 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:13 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:18 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:23 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:28 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:34 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:38 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:43 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:48 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:53 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:53:58 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:03 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:08 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:13 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:18 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:23 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:28 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:37 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:38 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:43 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:48 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:53 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:54:58 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:56:18 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:00 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:06 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:11 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:16 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:21 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:26 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:31 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:36 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:41 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:46 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:54 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:58:56 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:01 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:06 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:11 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:16 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:21 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:26 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:31 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:36 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:41 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:47 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:51 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 08:59:56 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:01 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:06 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:17 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:17 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:22 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:27 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:00:32 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:03:26 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:06:16 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:06:19 localhost varnishd[652]: Child (653) not responding to 
ping, killing it.
Mar  7 09:06:19 localhost varnishd[652]: Child (653) died signal=3
Mar  7 09:06:19 localhost varnishd[652]: Child cleanup complete
Mar  7 09:06:20 localhost varnishd[652]: child (13213) Started
Mar  7 09:06:20 localhost varnishd[652]: Child (13213) said Closed fds: 
4 5 6 7 11 12 14 15
Mar  7 09:06:20 localhost varnishd[652]: Child (13213) said Child starts
Mar  7 09:06:20 localhost varnishd[652]: Child (13213) said managed to 
mmap 483183820800 bytes of 483183820800
Mar  7 09:06:20 localhost varnishd[652]: Child (13213) said Ready

never seen something like this before. and also strange, I restarted 4 
identically configured and loadbalanced varnishes at the same time, but 
only this one performed the shown restart a day later; the others are 
still running without issues.

this happened with trunk, r3576.

Cheers, Sascha