[prev in list] [next in list] [prev in thread] [next in thread]
List: varnish-misc
Subject: Re: I have no idea why backend is sick
From: Abraham Cruz Sustaita <abraham.sustaita () buscacorp ! com>
Date: 2012-07-19 1:07:52
Message-ID: CANoN4qmR-64o=ERYe6Eu9rxi86Xe35YZ0XVFJ+SALmbZuzURYw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I can see that's exact the problem... so now I have to figured it out why
two servers with the exact same configuration have different results...
Thanks to all for your help.
2012/7/18 Hugo Cisneiros (Eitch) <hugo.cisneiros@gmail.com>
> On Wed, Jul 18, 2012 at 8:55 PM, Abraham Cruz Sustaita
> <abraham.sustaita@buscacorp.com> wrote:
> > I have 8 servers, 7 of them are working as they supposed to be working.
> > However, I have app02, and it is not working. The first problem I noticed
> > was it was reporting errors even when I change the error reporting to
> off.
> > The second problem, and the one that is give me troubles, is that after I
> > reboot the server, it is not working. I have this in the log:
> >
> > varnishlog | grep app02
> > 0 Backend_health - app02 Still healthy 4--X-R- 3 3 5 0.000488
> 0.000000
> > HTTP/1.1 301 Moved Permanently
> [...]
> > 0 Backend_health - app02 Went sick 4--X-R- 2 3 5 0.000722 0.000000
> > HTTP/1.1 301 Moved Permanently
> [...]
> > 0 Backend_health - app02 Still sick 4--X-R- 0 3 5 0.000503 0.000000
> > HTTP/1.1 301 Moved Permanently
> >
> > But the problem is that the server is working ok. If I do wget app02 from
> > varnish, it returns what it is supposed to return! But varnish says that
> it
> > went sick... Is there anyway I can trace this?
>
> As Shibashish said in the thread, the two requests (varnish and wget)
> aren't the same, since Varnish does not specify the Host header and
> your wget does.
>
> Probably, your Apache configuration isn't catching Varnish's request
> because it's not in the correspondent VirtualHost, and it's using the
> default configuration. To simulate your varnish's probe, you have to
> do:
>
> wget -O /dev/null -S http://app02.domain.com/health-check.html
>
> *without* hosts or anything. It must return HTTP 200. Take a look at
> Apache's global configuration and see if it's redirecting. Use wget to
> help identify the redirects.
>
> --
> []'s
> Hugo
> www.devin.com.br
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>
[Attachment #5 (text/html)]
I can see that's exact the problem... so now I have to figured it out why two \
servers with the exact same configuration have different results...<br><br>Thanks to \
all for your help.<br><br><div class="gmail_quote">2012/7/18 Hugo Cisneiros (Eitch) \
<span dir="ltr"><<a href="mailto:hugo.cisneiros@gmail.com" \
target="_blank">hugo.cisneiros@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="im">On Wed, Jul 18, 2012 at 8:55 PM, Abraham Cruz \
Sustaita<br> <<a href="mailto:abraham.sustaita@buscacorp.com">abraham.sustaita@buscacorp.com</a>> \
wrote:<br> > I have 8 servers, 7 of them are working as they supposed to be \
working.<br> > However, I have app02, and it is not working. The first problem I \
noticed<br> > was it was reporting errors even when I change the error reporting \
to off.<br> > The second problem, and the one that is give me troubles, is that \
after I<br> > reboot the server, it is not working. I have this in the log:<br>
><br>
> varnishlog | grep app02<br>
> 0 Backend_health - app02 Still healthy 4--X-R- 3 3 5 0.000488 0.000000<br>
> HTTP/1.1 301 Moved Permanently<br>
</div>[...]<br>
<div class="im">> 0 Backend_health - app02 Went sick 4--X-R- 2 3 5 0.000722 \
0.000000<br> > HTTP/1.1 301 Moved Permanently<br>
</div>[...]<br>
<div class="im">> 0 Backend_health - app02 Still sick 4--X-R- 0 3 5 0.000503 \
0.000000<br> > HTTP/1.1 301 Moved Permanently<br>
><br>
> But the problem is that the server is working ok. If I do wget app02 from<br>
> varnish, it returns what it is supposed to return! But varnish says that it<br>
> went sick... Is there anyway I can trace this?<br>
<br>
</div>As Shibashish said in the thread, the two requests (varnish and wget)<br>
aren't the same, since Varnish does not specify the Host header and<br>
your wget does.<br>
<br>
Probably, your Apache configuration isn't catching Varnish's request<br>
because it's not in the correspondent VirtualHost, and it's using the<br>
default configuration. To simulate your varnish's probe, you have to<br>
do:<br>
<br>
wget -O /dev/null -S <a href="http://app02.domain.com/health-check.html" \
target="_blank">http://app02.domain.com/health-check.html</a><br> <br>
*without* hosts or anything. It must return HTTP 200. Take a look at<br>
Apache's global configuration and see if it's redirecting. Use wget to<br>
help identify the redirects.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
[]'s<br>
Hugo<br>
<a href="http://www.devin.com.br" target="_blank">www.devin.com.br</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
varnish-misc mailing list<br>
<a href="mailto:varnish-misc@varnish-cache.org">varnish-misc@varnish-cache.org</a><br>
<a href="https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc" \
target="_blank">https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc</a><br>
</div></div></blockquote></div><br>
_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic