Welcome! Log In Create A New Profile

Advanced

Re: 10054: An existing connection was forcibly closed by the remote host

Francis Daly
June 14, 2016 06:16PM
On Tue, Jun 14, 2016 at 09:24:59AM -0400, madvas wrote:

Hi there,

> 8712#14268: *2060 WSARecv() failed (10054: An existing connection was
> forcibly closed by the remote host) while reading response header from
> upstream, client:0.xx.xx.0

If that error message is in nginx's error log, it suggests that nginx
thinks that something else closed the connection.

What is "upstream", in your case? Does it have any logs to indicate
a problem?

An old reply to the other thread you mailed this to indicated that it
may have been using a php server with not enough php children available.

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

10054: An existing connection was forcibly closed by the remote host

madvas June 14, 2016 09:24AM

Re: 10054: An existing connection was forcibly closed by the remote host

Francis Daly June 14, 2016 06:16PM

Re: 10054: An existing connection was forcibly closed by the remote host

walwong July 27, 2018 02:13AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 308
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready