Varnish 500's now not 302's
Nicholas_Maesepp at scee.net
Nicholas_Maesepp at scee.net
Wed May 9 04:11:16 CEST 2012
Hi
Continuing on with my last problem of the varnish cache returning a 302
for certain objects without contacting the backend I am now getting 500
errors from the cache. Object is available from the backend so definitely
not a 500 from the backend and logs + tcpdump show it trying to deliver
from cache only. Oddly enough its on mainly gif and png images that I
notice anyhow, and it happened to multiple caches within 1 hour of each
other on the same objects. A restart of varnish stopped the 500 errors.
Previously to attempt to resolve my 302 issue I lowered the amount of RAM
malloc'ed to 5 gig. Varnish now uses up 73% of the system's RAM. I have no
swap and there was at least a gig free on all caches before they started
serving 500's.
Here is a copy of the varnishlog.
16 ReqStart c 10.130.XX.XX 3259 1429474950
16 RxRequest c GET
16 RxURL c /static/furn/portal/common/pixel.gif
16 RxProtocol c HTTP/1.1
16 RxHeader c host: www.example.com
16 RxHeader c Accept: text/html, application/xhtml+xml, */*
16 RxHeader c Accept-Encoding: gzip, deflate
16 RxHeader c Accept-Language: en-US
16 RxHeader c Cache-Control: max-age=259200
16 RxHeader c Cookie: portalLocaleCookie=en_AU;
WT_FPC=id=XX.XX.XX.XX-249718560.30138265:lv=1336488750511:ss=1336488730455;
PDC4_COOKIE=Vk6CPp9WGbfxrZMnGxQlhFfWW0cJD0NGB4mNFcvQJ6nFwmRD1kxS!-925861289
16 RxHeader c User-Agent: Mozilla/5.0 (compatible; MSIE 9.0;
Windows NT 6.1; WOW64; Trident/5.0)
16 RxHeader c Via: 1.1 xx.xx.xx.xx:3128 (squid/2.6.STABLE21)
16 RxHeader c Xroxy-Connection: keep-alive
16 RxHeader c Z-Forwarded-For: AAAAAAAAAAAA
16 RxHeader c X-Forwarded-For: XX.XX.XX.XX
16 RxHeader c X-Forwarded-Port: 80
16 RxHeader c X-Forwarded-Proto: http
16 RxHeader c Connection: keep-alive
16 VCL_call c recv lookup
16 VCL_call c hash hash
16 Hit c 1429284571
16 VCL_call c hit deliver
16 VCL_call c deliver deliver
16 TxProtocol c HTTP/1.1
16 TxStatus c 500
16 TxResponse c Internal Server Error
16 TxHeader c cache-control: max-age=900
16 TxHeader c Content-Length: 0
16 TxHeader c Accept-Ranges: bytes
16 TxHeader c Date: Wed, 09 May 2012 00:54:41 GMT
16 TxHeader c X-Varnish: 1429474950 1429284571
16 TxHeader c Age: 33236
16 TxHeader c Via: 1.1 varnish
16 TxHeader c Connection: keep-alive
16 Length c 0
16 ReqEnd c 1429474950 1336524881.724712133
How I understand this is my server does the recv call, determines its a
lookup and then hashes as per my vcl, which is req,url and then server.ip
and then it does hit which is just to return deliver. Which should deliver
the object from cache, instead it gives me a 500.
I've decided to turn off range_support as I understand this is considered
experimental ? I'd like to avoid trial and error of my configuration if
possible. I'm just guessing at current really. Any more knowledgeable
ideas are welcomed. However I'd like to not have to go to disk for the
cache, I don't see why malloc should not be working as intended if this is
my issue.
Sony Computer Entertainment Australia Pty Ltd
Level 1, 63-73 Ann Street Surry Hills NSW 2010
P.O. Box 5023 Darlinghurst NSW 2010
ph: +61 (0)2 9324 9500 fax: +61 (0)2 9324 9558
http://au.playstation.com
http://www.facebook.com/PlayStationAU
THE WORLD IS IN PLAY.
PlayStation®Vita has arrived.
http://www.psvita.com
**********************************************************************
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify postmaster at scee.net
This footnote also confirms that this email message has been checked for
all known viruses.
Sony Computer Entertainment Australia Pty. Limited
Registered Office: Level 1, 63-73 Ann Street, Surry Hills, NSW 2010
Australia
Registered in Australia: 077 583 183
**********************************************************************
Please consider the environment before printing this e-mail
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20120509/38a6f56a/attachment.html>
More information about the varnish-misc
mailing list