Re: Random “http first read error: EOF” errors

Guillaume Quintard guillaume at varnish-software.com
Wed Mar 29 10:51:36 CEST 2017


And what's the Apache value?

-- 
Guillaume Quintard

On Wed, Mar 29, 2017 at 10:48 AM, Hazar Güney <hazarguney at gmail.com> wrote:

> It is default value which is 60:
>
> param.show backend_idle_timeout
> 200
> backend_idle_timeout
>         Value is: 60.000 [seconds] (default)
>         Minimum is: 1.000
>
>         Timeout before we close unused backend connections.
>
> On Wed, Mar 29, 2017 at 11:18 AM, Guillaume Quintard <
> guillaume at varnish-software.com> wrote:
>
>> I'm suspecting Apache's closing a keep-alive connection because it and
>> Varnish didn't agree on the timeout. Can you check? (in varnish, the param
>> is called backend_idle_timeout)
>>
>> --
>> Guillaume Quintard
>>
>> On Wed, Mar 29, 2017 at 10:12 AM, Hazar Güney <hazarguney at gmail.com>
>> wrote:
>>
>>> Backend is Apache.
>>>
>>> On Wed, Mar 29, 2017 at 10:34 AM, Guillaume Quintard <
>>> guillaume at varnish-software.com> wrote:
>>>
>>>> Indeed, looking at the Timestamp lines, it's not a timeout. What's your
>>>> backend?
>>>>
>>>> --
>>>> Guillaume Quintard
>>>>
>>>> On Wed, Mar 29, 2017 at 7:45 AM, Hazar Güney <hazarguney at gmail.com>
>>>> wrote:
>>>>
>>>>> I see sporadic fetch errors (http first read error: EOF) from backend
>>>>> but backend is normally healthy. It seems that timeout is not the root
>>>>> issue in this case. What could be the reason?
>>>>>
>>>>> *   << BeReq    >> 98808229
>>>>> -   Begin          bereq 98808228 fetch
>>>>> -   Timestamp      Start: 1490683823.763272 0.000000 0.000000
>>>>> -   BereqMethod    GET
>>>>> -   BereqURL       XXXX
>>>>> -   BereqProtocol  HTTP/1.1
>>>>> -   BereqHeader    Pragma: no-cache
>>>>> -   BereqHeader    Accept: */*
>>>>> -   BereqHeader    From: bingbot(at)microsoft.com
>>>>> -   BereqHeader    Host: XXXX
>>>>> -   BereqHeader    User-Agent: Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)
>>>>> -   BereqHeader    Accept-Encoding: gzip
>>>>> -   BereqHeader    X-Varnish: 98808229
>>>>> -   VCL_call       BACKEND_FETCH
>>>>> -   VCL_return     fetch
>>>>> -   BackendOpen    38 reload_2017-03-20T11:32:44.st2 10.35.78.11 80 172.17.0.2 48388
>>>>> -   BackendStart   10.35.78.11 80
>>>>> -   Timestamp      Bereq: 1490683823.763758 0.000487 0.000487
>>>>> -   *FetchError*     *http first read error: EOF*
>>>>> -   BackendClose   38 reload_2017-03-20T11:32:44.st2
>>>>> -   Timestamp      Beresp: 1490683823.764271 0.000999 0.000513
>>>>> -   Timestamp      Error: 1490683823.764277 0.001005 0.000005
>>>>> -   BerespProtocol HTTP/1.1
>>>>> -   BerespStatus   503
>>>>> -   BerespReason   Service Unavailable
>>>>> -   BerespReason   Backend fetch failed
>>>>> -   BerespHeader   Date: Tue, 28 Mar 2017 06:50:23 GMT
>>>>> -   BerespHeader   Server: Varnish
>>>>> -   VCL_call       BACKEND_ERROR
>>>>> -   BereqHeader    X-Varnish-Backend-5xx: 1
>>>>> -   VCL_return     retry
>>>>> -   Timestamp      Retry: 1490683823.764294 0.001022 0.000017
>>>>> -   Link           bereq 97940444 retry
>>>>> -   End
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> varnish-misc mailing list
>>>>> varnish-misc at varnish-cache.org
>>>>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20170329/430b1578/attachment.html>


More information about the varnish-misc mailing list