>From the varnish documentation I see that the threadpool max has a default of 1000 as I am doing some test on a (smal) VPS I reduced this number to 40 just to see if this might cause the problem.
Frank. On Mon, Jan 11, 2010 at 12:22 PM, Frank van Lingen <[email protected]> wrote: > Below the last messages. These are two restarts within the hour, but > most of the times it seems to run for several hours 4-8 without > problems. I could not find any panic messages. I found some messages > in the varnish mailing list regarding this but the only ones I found > where 'died signal=6' > > JJan 10 18:17:22 server1 varnishd[14016]: Child (23771) not responding > to ping, killing it. > Jan 10 18:17:23 server1 varnishd[14016]: Child (23771) not responding > to ping, killing it. > Jan 10 18:17:23 server1 varnishd[14016]: Child (23771) died signal=3 > Jan 10 18:17:23 server1 varnishd[14016]: child (25855) Started > Jan 10 18:17:23 server1 varnishd[14016]: Child (25855) said Closed > fds: 4 5 9 10 12 13 > Jan 10 18:17:23 server1 varnishd[14016]: Child (25855) said Child starts > Jan 10 18:17:23 server1 varnishd[14016]: Child (25855) said managed to > mmap 41943040 bytes of 41943040 > Jan 10 18:17:23 server1 varnishd[14016]: Child (25855) said Ready > Jan 10 18:49:43 server1 varnishd[14016]: Child (25855) not responding > to ping, killing it. > Jan 10 18:49:44 server1 varnishd[14016]: Child (25855) not responding > to ping, killing it. > Jan 10 18:49:44 server1 varnishd[14016]: Child (25855) died signal=3 > Jan 10 18:49:44 server1 varnishd[14016]: child (5186) Started > Jan 10 18:49:44 server1 varnishd[14016]: Child (5186) said Closed fds: > 4 5 9 10 12 13 > Jan 10 18:49:44 server1 varnishd[14016]: Child (5186) said Child starts > Jan 10 18:49:44 server1 varnishd[14016]: Child (5186) said managed to > mmap 41943040 bytes of 41943040 > Jan 10 18:49:44 server1 varnishd[14016]: Child (5186) said Ready > Jan 10 20:13:43 server1 varnishd[14016]: Child (5186) not responding > to ping, killing it. > Jan 10 20:13:44 server1 varnishd[14016]: Child (5186) not responding > to ping, killing it. > Jan 10 20:13:44 server1 varnishd[14016]: Child (5186) died signal=3 > Jan 10 20:13:44 server1 varnishd[14016]: child (13400) Started > Jan 10 20:13:44 server1 varnishd[14016]: Child (13400) said Closed > fds: 4 5 9 10 12 13 > Jan 10 20:13:44 server1 varnishd[14016]: Child (13400) said Child starts > Jan 10 20:13:44 server1 varnishd[14016]: Child (13400) said managed to > mmap 41943040 bytes of 41943040 > Jan 10 20:13:44 server1 varnishd[14016]: Child (13400) said Ready > > Jan 10 18:49:44 server1 varnishd[14016]: child (5186) Started > > -------------------------------------------- > Frank van Lingen > email : [email protected] > VOIP (skype) : fvlingen > IM (yahoo,hotmail) : fvlingen > IM (AIM) : [email protected] > URL : http://vanlingen.name > LinkedIn : fvlingen > ------------------------------------------- > > > > On Mon, Jan 11, 2010 at 9:49 AM, Poul-Henning Kamp <[email protected]> > wrote: >> In message <[email protected]>, >> Frank v >> an Lingen writes: >> >>>But I notice that once every so often the cache seems to either flush >>>itself or restart. During this 2-3 seconds that this happens I can not >>>load any pages. >> >> Check your syslog for panic messages from varnish, this should not >> happen in regular use. >> >> -- >> 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
