Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

apache22 forward/reverse proxy on current

Hi all,

Updated an i386pae domu to amd64 and in the process updated apache22 to the 

Since having done the above, apache serves as it should but when proxying a 
connection it fails with no errors produced and only severed connections as an 
indication there is a problem:

[Mon Jun 16 12:34:18 2008] [debug] proxy_util.c(2015): proxy: 
connected /search?hl=en&q=test&btnG=Google+Search&meta= to
[Mon Jun 16 12:34:18 2008] [debug] proxy_util.c(2172): proxy: HTTP: fam 2 
socket created to connect to *
[Mon Jun 16 12:34:18 2008] [debug] proxy_util.c(2269): proxy: HTTP: connection 
complete to (
[Mon Jun 16 12:34:18 2008] [debug] mod_proxy_http.c(1622): proxy: start body 
[Mon Jun 16 12:34:28 2008] [info] [client] (32)Broken pipe: 
core_output_filter: writing data to the network
[Mon Jun 16 12:34:28 2008] [debug] mod_proxy_http.c(1711): proxy: end body 
[Mon Jun 16 12:34:28 2008] [debug] proxy_util.c(1873): proxy: HTTP: has 
released connection for (*)

I typically use it to proxy internal client connections and to serve inbound 
requests to a zope server.

The symptoms at present are the ability to access google via a client machine 
but the inability to query google (as shown above) with the connection being 
severed pretty quickly.

Accessing the zope server results in the title being displayed but that's 
about it.

The log message:

Broken pipe: core_output_filter: writing data to the network

I've seen before when an apache module does not complete it's intended action, 
usually when a client clicks 'stop' or starts browsing to a different page. 
As the proxy seems to function fine up until more data is being transported 
(attempted anyway) could this be a network issue?

No config changes have been made.

NetBSD sammy.internal 4.99.64 NetBSD 4.99.64 (XEN3_DOMU) #1: Mon Jun 16 
14:36:08 EST 2008  
root%spike.internal@localhost:/usr/obj/sys/arch/amd64/compile/XEN3_DOMU amd64

Unfortunately using squid results in a uvm fault at the moment so no http 
proxying for me under current :(

Please let me know if there is some information I can provide to try and nail 
this down.



Home | Main Index | Thread Index | Old Index