Mailing List Archive: FetchError :http first read error: EOF

FetchError :http first read error: EOF

Nov 21, 2016, 8:25 AM

Post #1 of 6 (983 views)

Hi,

I'm trying to solve this problem for a long time.
I reset the default.vcl settings, but it did not work. What is your
suggestion?

* << BeReq >> 1277958
- Begin bereq 1277957 fetch
- Timestamp Start: 1479744699.658494 0.000000 0.000000
- BereqMethod GET
- BereqURL /
- BereqProtocol HTTP/1.1
- BereqHeader Host: www.*****.com
- BereqHeader User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
- BereqHeader Accept: */*
- BereqHeader Accept-Language: tr-TR,tr;q=0.8,en-US;q=0.6,en;q=0.4
- BereqHeader X-Actual-IP: 50.60.135.57
- BereqHeader X-Forwarded-For: 50.60.135.57, 50.60.135.57
- BereqHeader Accept-Encoding: gzip
- BereqHeader X-Varnish: 1277958
- VCL_call BACKEND_FETCH
- VCL_return fetch
- BackendOpen 132 boot.default 176.53.126.10 8080 176.53.126.10 51776
- BackendStart 176.53.126.10 8080
- Timestamp Bereq: 1479744702.659311 3.000817 3.000817
- FetchError http first read error: EOF
- BackendClose 132 boot.default
- Timestamp Beresp: 1479744811.501441 111.842947 108.842130
- Timestamp Error: 1479744811.501446 111.842952 0.000005
- BerespProtocol HTTP/1.1
- BerespStatus 503
- BerespReason Service Unavailable
- BerespReason Backend fetch failed
- BerespHeader Date: Mon, 21 Nov 2016 16:13:31 GMT
- BerespHeader Server: Varnish
- VCL_call BACKEND_ERROR
- BerespHeader Content-Type: text/html; charset=utf-8
- BerespHeader Retry-After: 5
- VCL_return deliver
- Storage malloc s0
- ObjProtocol HTTP/1.1
- ObjStatus 503
- ObjReason Backend fetch failed
- ObjHeader Date: Mon, 21 Nov 2016 16:13:31 GMT
- ObjHeader Server: Varnish
- ObjHeader Content-Type: text/html; charset=utf-8
- ObjHeader Retry-After: 5
- Length 284
- BereqAcct 356 0 356 0 0 0
- End

Re: FetchError :http first read error: EOF [ In reply to ]

geoff at uplex

Nov 21, 2016, 8:53 AM

Post #2 of 6 (978 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/21/2016 05:25 PM, Ayberk Kimsesiz wrote:
>
> I'm trying to solve this problem for a long time. I reset the
> default.vcl settings, but it did not work. What is your
> suggestion?
>
> * << BeReq >> 1277958 - FetchError http first read
> error: EOF - BackendClose 132 boot.default - Timestamp
> Beresp: 1479744811.501441 111.842947 108.842130

You're misunderstanding the problem, it has nothing to do Varnish. And
there's nothing Varnish can do about it, no matter what you do with
the settings.

Your backend is not responding. In this case, it took over 108
seconds. Varnish has to time out and give up, eventually.

Your backend named "boot.default", presumably an Apache or nginx or
Tomcat or something like that, is the cause of the problem here.
*That* is what you have to fix, not Varnish. Find out why it's taking
so long, and fix that; or, as the case may be, yell at the application
developers until they get it fixed.

HTH,
Geoff
- --
** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYMyaaAAoJEOUwvh9pJNURGykQAKYVg0FEK0ZbPv2AlUBuD+Yc
W4+D637le8ubL5L7QXjH1B54WBzwWDH/IYSMZii46OnU+pSn06hhKLDFUJzPEzEH
FAY9mPa951D1Fh5GVW8QhxYyA1tL3f3NmJw/qkOOmKoy1pr452x/xwCP+nFHvQfw
DoQ+v29Qu+VOJD4Kcsi80AphODgLIkgvebs6LWF8XK6iu4kcxFVQFJnSGsLU+ZPp
6N9VtdmLx5pvULXBb7R4IALe4NH2m7ft6fLKYMgAHRqvT3hp2asnFCdypjZlxD68
q0TULy2wNf3cM2bbD4OFl2L/DHrRk+QYrJQm8crNwdbXNQSavRCMy17n84cVXDr3
KJnWyPTUQEegs7DCmbK8/nPNVY/qth1ErPDk9zuqxykdD9qzTqzaBcArIJfui1L9
erD969I8rJl1ixMyKVXMhxt6WMDjGBZmMy6T2Q4oLT3Ck5HPiHmicgzJMrRSXrv1
OXPm/OFpV51bfY8FhQljBe7kgd8TMXbT2r/mfAJRRRytXumeQNuHsYDDgmR09m+y
8ngfe3MCMYtYYn57y7IeD+oM+kxwZrz9+z4em1xHRuHNYkDRkC0esWjodOvGyQov
Ts6k3yzRhCaRtq2rBXThbT9JZDx3ZqztYcpzwNweKo9z1FIKUaHcsw9cHpuRMHeb
nRVsUMIWq5uiMjdVvbda
=bkTG
-----END PGP SIGNATURE-----

_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Re: FetchError :http first read error: EOF [ In reply to ]

ayberk.kimsesiz at gmail

Nov 21, 2016, 9:21 AM

Post #3 of 6 (978 views)

Permalink

I see very few *Error 503 Backend fetch failed*, errors during the day. But
when I follow the logs, there are hundreds of errors.
Where exactly do I need to look at Apache?

2016-11-21 19:53 GMT+03:00 Geoff Simmons <geoff@uplex.de>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 11/21/2016 05:25 PM, Ayberk Kimsesiz wrote:
> >
> > I'm trying to solve this problem for a long time. I reset the
> > default.vcl settings, but it did not work. What is your
> > suggestion?
> >
> > * << BeReq >> 1277958 - FetchError http first read
> > error: EOF - BackendClose 132 boot.default - Timestamp
> > Beresp: 1479744811.501441 111.842947 108.842130
>
> You're misunderstanding the problem, it has nothing to do Varnish. And
> there's nothing Varnish can do about it, no matter what you do with
> the settings.
>
> Your backend is not responding. In this case, it took over 108
> seconds. Varnish has to time out and give up, eventually.
>
> Your backend named "boot.default", presumably an Apache or nginx or
> Tomcat or something like that, is the cause of the problem here.
> *That* is what you have to fix, not Varnish. Find out why it's taking
> so long, and fix that; or, as the case may be, yell at the application
> developers until they get it fixed.
>
>
> HTH,
> Geoff
> - --
> ** * * UPLEX - Nils Goroll Systemoptimierung
>
> ScheffelstraÃŸe 32
> 22301 Hamburg
>
> Tel +49 40 2880 5731
> Mob +49 176 636 90917
> Fax +49 40 42949753
>
> http://uplex.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJYMyaaAAoJEOUwvh9pJNURGykQAKYVg0FEK0ZbPv2AlUBuD+Yc
> W4+D637le8ubL5L7QXjH1B54WBzwWDH/IYSMZii46OnU+pSn06hhKLDFUJzPEzEH
> FAY9mPa951D1Fh5GVW8QhxYyA1tL3f3NmJw/qkOOmKoy1pr452x/xwCP+nFHvQfw
> DoQ+v29Qu+VOJD4Kcsi80AphODgLIkgvebs6LWF8XK6iu4kcxFVQFJnSGsLU+ZPp
> 6N9VtdmLx5pvULXBb7R4IALe4NH2m7ft6fLKYMgAHRqvT3hp2asnFCdypjZlxD68
> q0TULy2wNf3cM2bbD4OFl2L/DHrRk+QYrJQm8crNwdbXNQSavRCMy17n84cVXDr3
> KJnWyPTUQEegs7DCmbK8/nPNVY/qth1ErPDk9zuqxykdD9qzTqzaBcArIJfui1L9
> erD969I8rJl1ixMyKVXMhxt6WMDjGBZmMy6T2Q4oLT3Ck5HPiHmicgzJMrRSXrv1
> OXPm/OFpV51bfY8FhQljBe7kgd8TMXbT2r/mfAJRRRytXumeQNuHsYDDgmR09m+y
> 8ngfe3MCMYtYYn57y7IeD+oM+kxwZrz9+z4em1xHRuHNYkDRkC0esWjodOvGyQov
> Ts6k3yzRhCaRtq2rBXThbT9JZDx3ZqztYcpzwNweKo9z1FIKUaHcsw9cHpuRMHeb
> nRVsUMIWq5uiMjdVvbda
> =bkTG
> -----END PGP SIGNATURE-----
>

Re: FetchError :http first read error: EOF [ In reply to ]

apj at mutt

Nov 21, 2016, 10:14 PM

Post #4 of 6 (970 views)

Permalink

On Mon, Nov 21, 2016 at 08:21:50PM +0300, Ayberk Kimsesiz wrote:

> Where exactly do I need to look at Apache?

We can't tell you where. We can only tell you that it is taking it a very long
time to respond.

--
Andreas

_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Re: FetchError :http first read error: EOF [ In reply to ]

ayberk.kimsesiz at gmail

Nov 21, 2016, 10:47 PM

Post #5 of 6 (970 views)

Permalink

This problem started in October. According to the reports in July,
everything was in the way. From July to October, we only set up tools like
Memcached, Redis, APC and then removed them. Could it be about them?

2016-11-22 9:14 GMT+03:00 Andreas Plesner <apj@mutt.dk>:

> On Mon, Nov 21, 2016 at 08:21:50PM +0300, Ayberk Kimsesiz wrote:
>
> > Where exactly do I need to look at Apache?
>
> We can't tell you where. We can only tell you that it is taking it a very
> long
> time to respond.
>
> --
> Andreas
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>

Re: FetchError :http first read error: EOF [ In reply to ]

lagged at gmail

Nov 21, 2016, 11:56 PM

Post #6 of 6 (970 views)

Permalink

These are concerns which you will want to take up with your
sysadmin/developer. We can only speculate on your Varnish issues, not your
entire stack.

On Tue, Nov 22, 2016 at 12:47 AM, Ayberk Kimsesiz <ayberk.kimsesiz@gmail.com
> wrote:

> This problem started in October. According to the reports in July,
> everything was in the way. From July to October, we only set up tools like
> Memcached, Redis, APC and then removed them. Could it be about them?
>
> 2016-11-22 9:14 GMT+03:00 Andreas Plesner <apj@mutt.dk>:
>
>> On Mon, Nov 21, 2016 at 08:21:50PM +0300, Ayberk Kimsesiz wrote:
>>
>> > Where exactly do I need to look at Apache?
>>
>> We can't tell you where. We can only tell you that it is taking it a very
>> long
>> time to respond.
>>
>> --
>> Andreas
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc@varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>