Fwd: varnish 2.0.4 backend errors
kristian at redpill-linpro.com
Wed Jul 15 11:48:20 CEST 2009
On Wed, Jul 15, 2009 at 10:01:08AM +0200, Lazy wrote:
> setting 500 as min threads didn't make any diference, funny thing is
> that failed requests are in logged in apache as succesful
Sorry if I didn't make myself clear: The output from varnishstat didn't
indicate that threads was the issue causing 503s. It was more of a
tuning-comment than a shot at solving the real problem. Sorry about the
> 09:23:50.563934 IP x.x.x.x.51235 > x.x.x.x.88: S
> 1066103134:1066103134(0) win 32792 <mss 16396,sackOK,timestamp
> 552835403 0,nop,wscale 7>
Is it possible for you to mail me the raw cap-file? (Feel free to obfuscate
the IPs, but I'm really more of an ethereal-man than tcpdump-output...).
Feel free to drop it directly to me, if that makes it easier.
> successful POST in apache logs,
> in varnishlog
> 14 Backend c 15 default default
The request must've started earlier, as this is just the backend request.
Do you have the entire transaction available?
> restart shouldn't make another backend connection if current one got closed ?
It should, but it should be noted that: 1. We don't know _why_ it fails. 2.
Restart in vcl_error is brand new, so there might still be some issues.
You could try to turn on vcl-trace. (-p vcl_trace=on).
Also, could you post your VCL in it's entirety? (If you already did, I
must've missed it.)
Redpill Linpro AS
Tlf: +47 21544179
Mob: +47 99014497
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
More information about the varnish-misc