Hi August, Thank for the info. I will definitely try that today.
Have a nice day. Lei On Fri, Nov 4, 2011 at 12:48 PM, Gresens, August <[email protected]>wrote: > We were able to resolve this. Our Varnish instance is pointing a load > balanced pool of backend servers (a vip on a hardware load balancer), so > to Varnish there is only one backend. We had a situation in which certain > images were returning 500 errors from the backend. Because saint mode was > enabled, it invalidated the backend (the only back end) after a certain > number of failures within a particular window. We disabled saint mode and > this fixed this issue. Best, August**** > > ** ** > ------------------------------ > > *From:* Lei Wang [mailto:[email protected]] > *Sent:* Friday, November 04, 2011 3:40 PM > *To:* Rob S > *Cc:* Gresens, August; [email protected] > *Subject:* Re: Intermittent 503's from Varnish**** > > ** ** > > I had the same problem. Please help! > > /usr/sbin/varnishd -P /var/run/varnish80.pid -a :80 -f > /etc/varnish/varnish80.vcl -T 127.0.0.1:6082 -t 120 -w 1,1000,120 -u > varnish -g varnish -i varnish81 -S /etc/varnish/secret -p > thread_pool_add_delay 2 -p thread_pools 1 -p thread_pool_min 800 -p > thread_pool_max 2000 -p session_linger 50 -p sess_workspace 4096 -n > varnish80 -s malloc,6.5G > > configuration related to this problem: > backend eadrm { > .host = "drm-ea.xxxxxxxx.com"; > .port = "80"; > .connect_timeout = 40s; > .first_byte_timeout = 80s; > .between_bytes_timeout = 40s; > } > > } elsif (req.http.host ~ "drm-ea") { > unset beresp.http.set-cookie; > set beresp.ttl = 86400s; > log "Adjusting EA-DRM TTL to 86400 seconds"; > > Thanks, > > Lei**** > > On Fri, Nov 4, 2011 at 11:52 AM, Rob S <[email protected]> wrote:**** > > Can you send the varnishlog for one of these failing requests? Is > this a POST or a GET request? Are you using default VCL, or can you > send the VCL you are using? > > Rob**** > > On Fri, Nov 4, 2011 at 6:44 PM, Gresens, August <[email protected]> > wrote: > > Hello > > > > > > > > We’re having a very nasty production issue. We’re getting intermittent > 503 > > from Varnish in front of a healthy backend. > > > > > > > > This seems to happen on cache-miss, but we’re not seeing requests make > it to > > the backend. Varnish immediately returns the 503. After the first 503, > the > > page can usually be loaded by requesting it a few more times. This seems > to > > indicate that there is some condition within Varnish that prevents it > from > > hitting the backend that clears up quickly. > > > > > > > > Has anyone seen this issue before? Is there anything we can try? > > > > > > > > This is our startup config: > > > > > > > > DAEMON_OPTS="-a :80 \ > > > > -T localhost:6082 \ > > > > -f /etc/varnish/default.vcl \ > > > > -S /etc/varnish/secret \ > > > > -s file,/var/lib/varnish/$INSTANCE/varnish_storage.bin,1G \ > > > > -p http_headers=128 \ > > > > -p sess_workspace=262144 \ > > > > -p connect_timeout=60 \ > > > > -p max_restarts=6 \ > > > > -p log_hashstring=on \ > > > > -p cli_timeout=60 \ > > > > -t 0" > > > > > > > > We are on version 2.0.5 > > > > > > > > Thanks, > > > > > > > > August > > > > > > > > > >**** > > > _______________________________________________ > > varnish-misc mailing list > > [email protected] > > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc > > > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc**** > > ** ** >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
