On 20.08.2010 12:05, michael bienstein wrote:
Here's the error.log snippet for sending my Chrome browser to http://localhost:8081/qlikview The first request gets sent to 127.0.0.1:80 and works. It is a redirect to /qlikview/index.htm. The second request gets sent to 127.0.0.1:81. This says that it acquired a connection which can't be true. The existing socket is then forcibly closed by remote host OS 10054. Now I have run netstat -ab and nothing is listening on port 81. So it is really strange. In any case, my Apache sends back the 502 because of this. Then there is a request for the favicon which fails because it isn't mapped to anything. So what is that OS 10054 and how to fix it?
It is the winsock error numbr, so 10054 is "Connection reset by peer".
Michael --- [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(46): proxy: BALANCER: canonicalising URL //mycluster/qlikview [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(1003): proxy: Entering byrequests for BALANCER (balancer://mycluster) [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(1046): proxy: byrequests selected worker "http://127.0.0.1"; : busy 0 : lbstatus 0 [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(581): proxy: BALANCER (balancer://mycluster) worker (http://127.0.0.1) rewritten to http://127.0.0.1/qlikview [Fri Aug 20 10:49:32 2010] [debug] mod_proxy.c(993): Running scheme balancer handler (attempt 0) [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_http.c(1966): proxy: HTTP: serving URL http://127.0.0.1/qlikview [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2011): proxy: HTTP: has acquired connection for (127.0.0.1) [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2067): proxy: connecting http://127.0.0.1/qlikview to 127.0.0.1:80 [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2193): proxy: connected /qlikview to 127.0.0.1:80 [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2444): proxy: HTTP: fam 2 socket created to connect to 127.0.0.1 [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2576): proxy: HTTP: connection complete to 127.0.0.1:80 (127.0.0.1) [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_http.c(1736): proxy: start body send [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_http.c(1840): proxy: end body send [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2029): proxy: HTTP: has released connection for (127.0.0.1)
[Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(46): proxy: BALANCER: canonicalising URL //mycluster/qlikview/index.htm [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(1003): proxy: Entering byrequests for BALANCER (balancer://mycluster) [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(1046): proxy: byrequests selected worker "http://127.0.0.1:81"; : busy 0 : lbstatus 10 [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_balancer.c(581): proxy: BALANCER (balancer://mycluster) worker (http://127.0.0.1:81) rewritten to http://127.0.0.1:81/qlikview/index.htm [Fri Aug 20 10:49:32 2010] [debug] mod_proxy.c(993): Running scheme balancer handler (attempt 0) [Fri Aug 20 10:49:32 2010] [debug] mod_proxy_http.c(1966): proxy: HTTP: serving URL http://127.0.0.1:81/qlikview/index.htm [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2011): proxy: HTTP: has acquired connection for (127.0.0.1)
It only means we got a connection object from the pool. It is not necessarily actually connected yet.
[Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2067): proxy: connecting http://127.0.0.1:81/qlikview/index.htm to 127.0.0.1:81 [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2193): proxy: connected /qlikview/index.htm to 127.0.0.1:81 [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2444): proxy: HTTP: fam 2 socket created to connect to 127.0.0.1 [Fri Aug 20 10:49:32 2010] [debug] proxy_util.c(2576): proxy: HTTP: connection complete to 127.0.0.1:81 (127.0.0.1)
But this tells us, that there *is* something at port 81 we could connect to.
[Fri Aug 20 10:49:33 2010] [error] [client 127.0.0.1] (OS 10054)An existing connection was forcibly closed by the remote host. : proxy: error reading status line from remote server 127.0.0.1:81
And our peer closes the new connection. That's the problem, why the worker isn't put into error state.
Can you try using "telnet 127.0.0.1 81" to connect to port 81? If this also works, then we no longer have any indication of an Apache problem. Instead you need to find out, what accepts connctions on this port on your machine. To check the opposite, if you find some port nothing responds to, you can verify the correct setting of the error state using that port.
Regards, Rainer --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|