Welcome! Log In Create A New Profile

Advanced

Re: nginx big bug

March 07, 2012 02:03PM
error.log

==========================================================================

2012/03/07 22:53:35 [error] 9924#9964: *109 WSARecv() failed (10054: An existing connection was forcibly closed by the remote host) while reading response header from upstream, client: 192.168.1.25, server: localhost, request: "GET /2.php HTTP/1.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.25"


2012/03/07 22:53:35 [error] 9924#9964: *111 WSARecv() failed (10054: An existing connection was forcibly closed by the remote host) while reading response header from upstream, client: 192.168.1.215, server: localhost, request: "GET /phpMyAdmin/index.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.25"


2012/03/07 22:54:54 [error] 9924#9964: *114 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 192.168.1.215, server: localhost, request: "GET /1.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.25"


2012/03/07 22:54:54 [error] 9924#9964: *124 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 192.168.1.25, server: localhost, request: "GET /2.php HTTP/1.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.25"


2012/03/07 22:59:34 [error] 9924#9964: *193 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 192.168.1.215, server: localhost, request: "GET /1.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.25"


2012/03/07 22:59:34 [error] 9924#9964: *203 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 192.168.1.25, server: localhost, request: "GET /2.php HTTP/1.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.25"
Subject Author Posted

nginx big bug

catball123 March 07, 2012 01:07PM

Re: nginx big bug

catball123 March 07, 2012 01:09PM

Re: nginx big bug

Cliff Wells March 07, 2012 01:52PM

Re: nginx big bug

catball123 March 07, 2012 01:59PM

Re: nginx big bug

catball123 March 07, 2012 02:03PM

Re: nginx big bug

catball123 March 07, 2012 02:06PM

Re: nginx big bug

catball123 March 07, 2012 02:11PM

Re: nginx big bug

Cyril Lavier March 07, 2012 02:06PM

Re: nginx big bug

Maxim Dounin March 07, 2012 02:10PM

Re: nginx big bug

antodas March 16, 2015 06:01PM

Re: nginx big bug

madvas June 14, 2016 09:23AM

Re: nginx big bug

Maxim Dounin March 17, 2015 09:44AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 57
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready