FetchError :http first read error: EOF
ayberk.kimsesiz at gmail.com
Mon Nov 21 18:21:50 CET 2016
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 at 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.
> - --
> ** * * UPLEX - Nils Goroll Systemoptimierung
> Scheffelstraße 32
> 22301 Hamburg
> Tel +49 40 2880 5731
> Mob +49 176 636 90917
> Fax +49 40 42949753
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> -----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc