Child not responding to ping, killing it

[Poul-Henning Kamp]

In message <1216998105.4889ead90d5f9 at www.qalpit.com>, Olivier Beau writes:

>i doubled cli_timeout's and ping_interval's defaults :
>
># varnishadm -T localhost:6082 param.show | grep -e cli_timeout -e ping_interval
>cli_timeout                10 [seconds]
>ping_interval              6 [seconds]
>#
>
>Still had the problem twice today;
>should i try raising those params somemore ?

If you update to trunk, it should coredump the cacher process instead,
then try using gdb to get a backtrace so we can see what it is
doing instead of answering pings...

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.