Thanks, I'll do as you suggest and see what happens. If it's wedged, then I should do what, attach with gdb and get a backtrace?
Thanks, Skye On 20-Apr-08, at 11:41 PM, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Skye Poier > Nott writes > : >> Update: I ran varnishd in foreground with -d and I'm seeing these >> periodically, which would explain the cache invalidation... >> >> Child not responding to ping >> Cache child died pid=23899 status=0x9 > > This is the manager process not getting a reply from the child > process and restarting it, assuming that it is not serving > requests either. > > You need to find out why the child process does not reply to pings. > > The first thing to do is to increase the managers timeout by > increasing > the "cli_timeout" parameter to see if the child process is wedged > or just slow. > > -- > 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. > _______________________________________________ > varnish-misc mailing list > [email protected] > http://projects.linpro.no/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] http://projects.linpro.no/mailman/listinfo/varnish-misc
