Hello,
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 ? Olivier Selon Poul-Henning Kamp <[EMAIL PROTECTED]>: > In message <[EMAIL PROTECTED]>, Olivier Beau writes: > >Hi all, > > > >I installed varnish (trunk) on 3 redhat5 64bit, (serving the same website) > > > >i see those logs on only one server : > > > >Jul 22 18:12:25 img-front1 varnishd[19818]: Child (27470) not responding to > >ping, killing it. > >Jul 22 18:12:25 img-front1 varnishd[19818]: Child (27470) not responding to > >ping, killing it. > >Jul 22 18:12:25 img-front1 varnishd[19818]: Child (27470) died signal=9 > > Try increasing the cli_timeout and ping_interval parameters and see if > that mitigaes the issue. > > If it does, then the child simply gets stuck for long periods of time. > > If it doesn't change things, then the child is stuck in an endless loop > and getting a stack backtrace from a core file would be wonderful. > > Right now you'll not get a coredump on the signal 9, but give me a > few minutes, and the coredump will be controled by the diag_bitmap > paramter. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Olivier Beau _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
