On 17.01.2011 08:23, Ruediger Pluem wrote:
On 01/15/2011 05:01 PM, Joe Orton wrote:
On Wed, Jan 12, 2011 at 03:30:01PM -0500, Jim Jagielski wrote:
My current migration of mod_proxy away from the scoreboard
and to slotmem is done. All that remains is some final
testing.
This will serve as the basis for adding in members during
runtime. Currently, the idea is that we only change the
number of workers, but nothing really prevents us from
also doing it with balancers themselves at some point.
I'll be committing most likely tomorrow...
With prefork I am seeing erratic results for the mod_rewrite proxy tests
in t/modules/rewrite.t, though I've no reason to believe it is directly
caused by this set of changes. Is anybody else seeing this?
I get either:
t/modules/rewrite.t (Wstat: 0 Tests: 29 Failed: 2)
Failed tests: 28-29
or
t/modules/rewrite.t (Wstat: 0 Tests: 29 Failed: 1)
Failed test: 27
and have not dug further. Sometimes all the tests pass.
Same for me. Just thought it was something weird on my side.
Same here.
Proxy returns 502
# testing : proxy/QSA test appended args correctly
# expected: (?s-xim:QUERY_STRING = foo=bar&bloo=blar\n)
# received: HTTP/1.1 502 Proxy Error
# Connection: close
# Date: Mon, 17 Jan 2011 17:03:30 GMT
# Server: Apache/2.3.11-dev (Unix) mod_ssl/2.3.11-dev OpenSSL/0.9.8q DAV/2
# Content-Length: 439
# Content-Type: text/html; charset=iso-8859-1
# Client-Date: Mon, 17 Jan 2011 17:03:30 GMT
# Client-Peer: 127.0.0.1:8529
# Title: 502 Proxy Error
#·
# <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
# <html><head>
# <title>502 Proxy Error</title>
# </head><body>
# <h1>Proxy Error</h1>
# <p>The proxy server received an invalid^M
# response from an upstream server.<br />^M
# The proxy server could not handle the request <em><a
href="/modules/rewrite/proxy-qsa.html">GET /modules/rewrite/proxy-qsa.html</a></em>.<p>
# Reason: <strong>Error reading from remote server</strong></p></p>
# </body></html>
[Mon Jan 17 18:03:30.954082 2011] [proxy:debug] [pid 21205]
mod_proxy.c(1079): Running scheme http handler (attempt 0)
[Mon Jan 17 18:03:30.954121 2011] [proxy:debug] [pid 21205]
proxy_util.c(2087): proxy: HTTP: has acquired connection for (*)
[Mon Jan 17 18:03:30.954153 2011] [proxy:debug] [pid 21205]
proxy_util.c(2140): proxy: connecting
http://localhost:8529/modules/cgi/env.pl?foo=bar&bloo=blar to localhost:8529
[Mon Jan 17 18:03:30.954195 2011] [proxy:debug] [pid 21205]
proxy_util.c(2266): proxy: connected
/modules/cgi/env.pl?foo=bar&bloo=blar to localhost:8529
[Mon Jan 17 18:03:30.957360 2011] [proxy_http:error] [pid 21205]
(20014)Internal error: [client 127.0.0.1:53088] proxy: error reading
status line from remote server localhost:8529
[Mon Jan 17 18:03:30.957433 2011] [proxy_http:debug] [pid 21205]
mod_proxy_http.c(1531): [client 127.0.0.1:53088] proxy: NOT Closing
connection to client although reading from backend server localhost:8529
failed.
[Mon Jan 17 18:03:30.957467 2011] [proxy:error] [pid 21205] [client
127.0.0.1:53088] proxy: Error reading from remote server returned by
/modules/rewrite/proxy-qsa.html
[Mon Jan 17 18:03:30.957490 2011] [proxy:debug] [pid 21205]
proxy_util.c(2102): proxy: HTTP: has released connection for (*)
The backend request is not contained in the access log.
I couldn't reproduce above LogLevel trace4, but maybe I simply wasn't
patient enough.
Regards,
Rainer
