<font size=2 face="sans-serif">If I go direct to the backend I do not
have the error.</font>
<br>
<br><font size=2 face="sans-serif">I imagine I could use varnishadm console
to load a different VCL, thought I've never tried, as restarting varnish
fixes the issues straight away. I find it unlikely as my other caches didn't
have the problem at the time and they were hitting the same backend. </font>
<br>
<br><font size=2 face="sans-serif">Also should mention I do use grace and
saintmode where I can. </font>
<br>
<br><font size=2 face="sans-serif">Nick</font>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Hugues Alary <hugues.alary@gmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Nicholas_Maesepp@scee.net</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">varnish-misc@varnish-cache.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/02/2012 10:28 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: Strange
302</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Hi,</font>
<br>
<br><font size=3>Have you tried bypassing varnish by either removing it
or doing a return(pipe); as the 1st instruction in your vcl_recv() and
see if you still get the 302? If not, it *could* be varnish, if yes, it
is your backend application that send a 302.</font>
<br>
<br><font size=3>-Hugues<br>
</font>
<br><font size=3>On Tue, May 1, 2012 at 5:22 PM, <</font><a href=mailto:Nicholas_Maesepp@scee.net target=_blank><font size=3 color=blue><u>Nicholas_Maesepp@scee.net</u></font></a><font size=3>>
wrote:</font>
<br><font size=3 face="sans-serif">Hi All</font><font size=3> <br>
</font><font size=3 face="sans-serif"><br>
Been running varnish-3.0.2 revision 55e70a4 for a couple weeks using
-smalloc and 6G. Got several of them and they run fine for a couple weeks
and for the 2nd time now the first cache has stopped serving a key css
file and returning a 302. I don't cache the css and I also don't implement
any 302 redirects via varnish.</font><font size=3> <br>
</font><font size=3 face="sans-serif"><br>
GET </font><a href=http://www.example.com/r09_d71/static/includes/style/portal_combined_min.css target=_blank><font size=3 color=blue face="sans-serif"><u>http://www.example.com/r09_d71/static/includes/style/portal_combined_min.css</u></font></a><font size=3 face="sans-serif">
HTTP/1.1" 302 210 "http:/</font><a href=http://www.example.com/ target=_blank><font size=3 color=blue face="sans-serif"><u>www.example.com/</u></font></a><font size=3 face="sans-serif">"
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0"</font><font size=3>
<br>
</font><font size=3 face="sans-serif"><br>
After a restart of varnish only I get <br>
<br>
GET </font><a href=http://www.example.com/r09_d71/static/includes/style/portal_combined_min.css target=_blank><font size=3 color=blue face="sans-serif"><u>http://www.example.com/r09_d71/static/includes/style/portal_combined_min.css</u></font></a><font size=3 face="sans-serif">
HTTP/1.1" 200 44805 "</font><a href=http://www.example.com/ target=_blank><font size=3 color=blue face="sans-serif"><u>http://www.example.com/</u></font></a><font size=3 face="sans-serif">"
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0"</font><font size=3>
<br>
</font><font size=3 face="sans-serif"><br>
I believe a few other image objects may also not load properly but it is
hard to tell with a broken css and the interesting part is I don't cache
the css whilst I do the images. </font><font size=3><br>
</font><font size=3 face="sans-serif"><br>
I have made some tweaks(thanks internet), which I may not fully understand
and worked fine in limited testing whilst giving performance improvements.</font><font size=3>
<br>
</font><font size=3 face="sans-serif"><br>
-p log_hashstring=off \</font><font size=3> </font><font size=3 face="sans-serif"><br>
-p shm_workspace=32768
\</font><font size=3> </font><font size=3 face="sans-serif"><br>
-p thread_pool_workspace=262144
\</font><font size=3> </font><font size=3 face="sans-serif"><br>
-p http_gzip_support=off
\</font><font size=3> </font><font size=3 face="sans-serif"><br>
-p http_range_support=on
\</font><font size=3> </font><font size=3 face="sans-serif"><br>
-p http_req_hdr_len=9072
\</font><font size=3> <br>
</font><font size=3 face="sans-serif"><br>
Any ideas why I would get a 302? I track varnish memory using cloudwatch
(in AWS) and at the time of restart it was at 65% and had been on the decline
for a couple hours from 88%. The total Ram on the box is 7.5G so 90% is
about the limit varnish will hit. Have I not allowed enough RAM for worker
threads?</font><font size=3> <br>
</font><font size=3 face="sans-serif"><br>
# # The minimum number of worker threads to start</font><font size=3> </font><font size=3 face="sans-serif"><br>
VARNISH_MIN_THREADS=30</font><font size=3> </font><font size=3 face="sans-serif"><br>
#</font><font size=3> </font><font size=3 face="sans-serif"><br>
# # The Maximum number of worker threads to start</font><font size=3> </font><font size=3 face="sans-serif"><br>
VARNISH_MAX_THREADS=1000</font><font size=3> </font><font size=3 face="sans-serif"><br>
#</font><font size=3> </font><font size=3 face="sans-serif"><br>
# # Idle timeout for worker threads</font><font size=3> </font><font size=3 face="sans-serif"><br>
VARNISH_THREAD_TIMEOUT=120</font><font size=3> <br>
<br>
<br>
</font><font size=3 face="sans-serif"><br>
Cheers</font><font size=3> <br>
</font><font size=3 face="sans-serif"><br>
Nick Maesepp</font><font size=3> <br>
</font>
<br><font size=3>-- <br>
Hugues ALARY</font>
<br><font size=2 color=blue face="sans-serif"><u><br>
</u></font><a href></a>
<p><font size=2 face="sans-serif"><b><br>
Sony Computer Entertainment Australia Pty Ltd</b><br>
Level 1, 63-73 Ann Street Surry Hills NSW 2010<br>
P.O. Box 5023 Darlinghurst NSW 2010<br>
ph: +61 (0)2 9324 9500 fax: +61 (0)2 9324 9558</font>
<p><a href=http://au.playstation.com/><font size=2 color=blue face="sans-serif"><u>http://au.playstation.com</u></font></a><font size=2 color=blue face="sans-serif"><u><br>
</u></font><a href=www.facebook.com/PlaystationAU><font size=2 color=blue face="sans-serif"><u>http://www.facebook.com/PlayStationAU</u></font></a>
<p><font size=2 face="sans-serif"><br>
<b><br>
THE WORLD IS IN PLAY.</b><br>
PlayStationŽVita has arrived.<br>
</font><a href=http://www.psvita.com/><font size=2 face="sans-serif">http://www.psvita.com</font></a><font size=2 face="sans-serif">
<br>
<br>
</font><font size=2 color=blue face="sans-serif"><u><br>
</u></font><a href=http://au.playstation.com/psvita><img src=http://au.playstation.com/media/2deMCPFh/psvita_corp_sig_au.jpg width=414 height=152 alt=PSMOVE></a><font size=2 face="Arial"><br>
<br>
**********************************************************************<br>
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@scee.net<br>
This footnote also confirms that this email message has been checked for
all known viruses.<br>
Sony Computer Entertainment Australia Pty. Limited<br>
Registered Office: Level 1, 63-73 Ann Street, Surry Hills, NSW 2010 Australia<br>
Registered in Australia: 077 583 183<br>
**********************************************************************<br>
</font><font size=2 color=#008000 face="Arial"><b><i><br>
Please consider the environment before printing this e-mail</i></b></font>