varnish forward to wrong backend

[Lei Wang]

Hi Per,

>From the tcpdump, the request was passed to the varnish listening port (80)
and then passed to the wrong backend. The weird thing was all the bad
transaction passed to backend do not have any varnish related header as it
should be.

Good one
GET /6/3/3/6/4/221446336.ea HTTP/1.1
User-Agent: Java/1.4.2_19
Host: cache.internal.myserver.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
X-Forwarded-For: 10.150.4.118, 10.150.0.220
X-Varnish: 570940624

Bad one
GET /6/3/3/6/4/221446336.ea HTTP/1.1
User-Agent: Java/1.4.2_19
Host: cache.internal.myserver.com
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
X-Forwarded-For: 10.150.0.220

Thanks,

Lei


On Fri, Aug 16, 2013 at 6:20 AM, Per Buer <perbu at varnish-software.com>wrote:

> Hi Lei,
>
> It sounds like they are somehow bypassing your Varnish installation. If
> they where handled by Varnish they would be in varnishlog. Maybe the
> loadbalancer is doing something weird? Or the webservers have an exposed IP
> address outside the LB?
>
> Per.
>
>
> On Fri, Aug 16, 2013 at 2:21 PM, Lei Wang <leiwang at rhapsody.com> wrote:
>
>> Hi Per,
>>
>> There are not in varnishlog and even varnishncsa log. There only trace
>> may useful is the captured network tcpdump. It is quite big ans shows load
>> balance sent correct header and url to varnish listen port, then passed to
>> wrong backend.
>>
>> Thanks,
>>
>> Lei
>>
>>
>> On Fri, Aug 16, 2013 at 1:10 AM, Per Buer <perbu at varnish-software.com>wrote:
>>
>>> Hi Lei,
>>>
>>> On Thu, Aug 15, 2013 at 8:09 PM, Lei Wang <leiwang at rhapsody.com> wrote:
>>>
>>>> I have varnish 3 (varnish-3.0.4 revision 9f83e8f) installed to cache
>>>> multi-site in one configuration. Sometimes Varnish switched to use the
>>>> first backend in the configuration for all the requests to the other sites.
>>>> As in the sample configuration below, the request to backend2, backend3,
>>>> backend4 sometimes forwarded to backend1. Does anyone have the same problem
>>>> or know any solution, suggestion?
>>>>
>>>
>>> Could you see if you can post a varnishlog statement showing this
>>> behaviour? It should be fairly easy to find one if it happens regularly.
>>>
>>>
>>> Cheers,
>>>
>>> Per.
>>>
>>> --
>>>  <http://www.varnish-software.com/> *Per Buer*
>>> CTO | Varnish Software AS
>>> Phone: +47 958 39 117 | Skype: per.buer
>>> We Make Websites Fly!
>>>
>>> Winner of the Red Herring Top 100 Europe Award 2013
>>>
>>>
>>>
>>
>
>
> --
>  <http://www.varnish-software.com/> *Per Buer*
> CTO | Varnish Software AS
> Phone: +47 958 39 117 | Skype: per.buer
> We Make Websites Fly!
>
> Winner of the Red Herring Top 100 Europe Award 2013
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20130816/bfab1e23/attachment-0001.html>