Thu Apr 12 11:29:12 2001] [notice] Apache/2.0.17-dev (Unix) configured -- resuming normal operations
[Thu Apr 12 12:19:18 2001] [error] [client 10.0.1.4] proxy: error reading status line from remote server www.channelcincinnati.com, referer: http://www.drudgereport.com/
[Thu Apr 12 12:19:33 2001] [error] [client 10.0.1.4] proxy: error reading status line from remote server www.channelcincinnati.com
[Thu Apr 12 12:19:54 2001] [error] (32)Broken pipe: core_output_filter: writing data to the network
[Thu Apr 12 12:20:04 2001] [error] [client 10.0.1.4] proxy: error reading status line from remote server www.channelcincinnati.com
[Thu Apr 12 12:20:05 2001] [error] (111)Connection refused: proxy: attempt to connect to 208.45.172.82:80 (scrooge.ibsys.com) failed
The last line is normal; it's the first few that I'm looking into.
Do we go somewhere bad if we don't read a good status line from the origin server? All servers in the pool are running against www.channelcincinnati.com in this timeframe (site's got a lot of graphics).
Chuck
On Thursday, April 12, 2001, at 10:46 AM, Chuck Murcko wrote:
On Wednesday, April 11, 2001, at 10:27 PM, Graham Leggett wrote:
"Victor J. Orlikowski" wrote:
Does ProxyPassReverse work as intended for you in your testing? Or do I need to update my code?
I checked it yesterday quite carefully and it worked - I think the threading issues were causing all types of hassles.
The last patch fixes FTP, and the patch before that fixes threading - the proxy was pretty hozed before that. Make sure your code is up to date as of the last CVS commit...
including -current httpd, apr, and apr-util?
Chuck
Chuck Murcko Topsail Group http://www.topsail.org/
