populating cache backends out-of-band

2009-04-08 Thread Doug Beaver
hi, i've searched the mailing lists and looked over the developer section of the wiki, and haven't found an answer for this yet. is it possible to preemptively store the response for a given uri without making a http request to the backend host(s)? i have a varnish tier with 100 hosts that is

Re: varnish killing off the child process after a few minutes

2009-04-08 Thread Kristian Lyngstol
On Tue, Apr 07, 2009 at 01:01:51PM -0700, Tung Nguyen wrote: Hi guys, We're on varnish 2.0.3 It looks like varnish restarts the child process for us every so often, causing 503s :(. Was wondering if this is a known issue. Can you check the syslog for any more information? -- Kristian

Re: varnish 2.0.4 and new config changes

2009-04-08 Thread Kristian Lyngstol
On Tue, Apr 07, 2009 at 05:29:23PM -0700, Jauder Ho wrote: On Tue, Apr 7, 2009 at 4:46 AM, Kristian Lyngstol krist...@redpill-linpro.com wrote: On Tue, Apr 07, 2009 at 04:11:04AM -0700, Jauder Ho wrote: FYI, beresp.ttl does not work on varnish 2.0.4. It does work on -trunk though.

Re: varnish killing off the child process after a few minutes

2009-04-08 Thread Tung Nguyen
Sure, Here's the syslog around one of the times when the child looks like its crashing. Apr 8 01:19:00 ey03-s00344 varnishd[2628]: assets. Apr 8 01:19:00 ey03-s00344 varnishd[2628]: vcl_recv. Apr 8 01:19:00 ey03-s00344 varnishd[2628]: /javascripts/responders_1239147022.js?1239147050

Re: Varnish 2.0.3 consuming excessive memory

2009-04-08 Thread Darryl Dixon - Winterhouse Consulting
Hi DES, Darryl Dixon - Winterhouse Consulting darryl.di...@winterhouseconsulting.com writes: +if (req.http.Pragma ~ .*no-cache.* || req.http.Cache-Control ~ .*no-cache.*) { +purge_url(regsub(req.url, [?].*$, .*$)); +} + It would be interesting to see how often this

Re: Varnish 2.0.3 consuming excessive memory

2009-04-08 Thread Darryl Dixon - Winterhouse Consulting
hi darryl i had a simlar problem (varnish child process consuming lots of memory) a week ago (see the thread make varnish don't start a subprocess) the solution for my problem seems to be to use a high-enough cache-size: starting varnish with -s file,/tmp/storage,300M will make the