Ticket #635 (new defect)

Opened 2 years ago

Last modified 1 year ago

lighttpd 1.4.11 mod_proxy on OS X Darwin and OpenBSD

Reported by: lj@socialserve.com Assigned to: jan
Priority: normal Milestone:
Component: mod_proxy Version: 1.4.11
Severity: normal Keywords:
Cc: Blocking:
Need Feedback:

Description

I believe there is a bug in mod_proxy lighttpd-1.4.11 on platform OS X Darwin (PPC) and OpenBSD 3.9 (PPC). In testing on Linux the problem didn't happen.

When the mod_proxy is configured:

server.network-backend = "write" # or writev

proxy.balance = "hash" # or fair we did not test round-robin

proxy.server = ( "" => ( ( "host" => "10.0.0.1", "port" => 80 ),

( "host" => "10.0.0.2" , "port" => 80 ) ) )

The error.log showed:

(network_write.c.55) write failed: Broken pipe 13

(connections.c.538) connection closed: write failed on fd 13

or with writev:

(network_writev.c.116) writev failed: Socket is not connected 9

(mod_proxy.c.824) write failed: Socket is not connected 57

Testing with apache benchmark tool 'ab' most of the time there was no problem. However testing with Firefox was when these error messages showed up. We tested lighttpd proxying for apache 2 on OS X and Linux.

Attachments

Change History

05/04/2007 03:01:40 AM changed by badalex@gmail.com

I can verify this using OpenBSD 4.1 as the maching running lighttpd (it also happend and 4.0 and its version of lighttpd 1.4.11) lighttpd -v lighttpd-1.4.13 (ssl)

I am also using lighttpd as a reverse proxy for some apache web servers here is what shows up in the log

2007-05-03 20:51:18: (network_writev.c.111) writev failed: Socket is not connected 9 2007-05-03 20:51:18: (mod_proxy.c.824) write failed: Socket is not connected 57 2007-05-03 20:51:18: (mod_proxy.c.911) proxy-server disabled: 192.168.0.2 80 9 2007-05-03 20:51:18: (mod_proxy.c.1249) no proxy-handler found for: /css/vars.css 2007-05-03 20:51:18: (mod_proxy.c.1249) no proxy-handler found for: /css/uploads.css 2007-05-03 20:51:18: (mod_proxy.c.1249) no proxy-handler found for: /js/common.js 2007-05-03 20:51:19: (mod_proxy.c.1249) no proxy-handler found for: /css/common.css 2007-05-03 20:51:19: (mod_proxy.c.1249) no proxy-handler found for: /js/uploads.js 2007-05-03 20:51:19: (mod_proxy.c.1249) no proxy-handler found for: /js/ajax.js 2007-05-03 20:51:19: (mod_proxy.c.1249) no proxy-handler found for: /images/home.gif 2007-05-03 20:51:20: (mod_proxy.c.1249) no proxy-handler found for: /favicon.ico 2007-05-03 20:51:23: (mod_proxy.c.1294) proxy - re-enabled: 192.168.0.2 80

lighttpd.conf: server.modules = (

"mod_proxy",

"mod_accesslog" )

server.document-root = "/www/pages/"

server.errorlog = "/www/logs/lighttpd.error.log"

index-file.names = ( "index.php", "index.html",

"index.htm", "default.htm" )

$HTTPhost? =~ "demeter\.example\.com" {

proxy.server = ( "" => (( "host" => "192.168.0.2" )) )

}

We get this regradless of the os and browser on the client (Firefox/Opera/IE7, Mac/Linux 2.6/Windows XP). Also 192.168.0.2 is a linux box running apache 2.2.2. Apache2 running as a reverse proxy never gave us any problems.

Add/Change #635 (lighttpd 1.4.11 mod_proxy on OS X Darwin and OpenBSD)




Change Properties