Actions
Bug #163
closedlogging problem in mod_proxy after proxy disconnect
Status:
Fixed
Priority:
High
Category:
mod_proxy
Target version:
-
ASK QUESTIONS IN Forums:
Description
I'm running tracd & lihttpd 1.3.13 using this config:
$HTTP["host"] == "projects.example.com" { proxy.server = ("" => ( "trac" => ( "host" => "127.0.0.1", "port" => 9090 ))) }
Nothing happens on tracd shutdown (in my first case it just crashed, i killed it for following tests), but as soon as someone points his browser to url that should be proxified, logging goes nuts. It starts writing over 30 lines a second in error.log, staritng like this:
2005-06-27 03:06:43: (mod_proxy.c.918) error: unexpected close of proxy connection for / (no proxy process on host: 127.0.0.1, port: 9090 ?) 2005-06-27 03:06:43: (mod_proxy.c.700) establishing connection failed: Connection refused 2005-06-27 03:06:43: (mod_proxy.c.918) error: unexpected close of proxy connection for / (no proxy process on host: 127.0.0.1, port: 9090 ?) 2005-06-27 03:06:43: (mod_proxy.c.723) write failed: Broken pipe -1 2005-06-27 03:06:43: (mod_proxy.c.817) proxy-server disabled: 127.0.0.1 9090 10
then repeating following lines until disk gets full
2005-06-27 03:06:43: (mod_proxy.c.918) error: unexpected close of proxy connection for (no proxy process on host: 127.0.0.1, port: 9090 ?) 2005-06-27 03:06:43: (mod_proxy.c.1088) unhandled proxy.state 3 2005-06-27 03:06:43: (mod_proxy.c.918) error: unexpected close of proxy connection for (no proxy process on host: 127.0.0.1, port: 9090 ?) 2005-06-27 03:06:43: (mod_proxy.c.1088) unhandled proxy.state 3 2005-06-27 03:06:43: (mod_proxy.c.918) error: unexpected close of proxy connection for (no proxy process on host: 127.0.0.1, port: 9090 ?) 2005-06-27 03:06:43: (mod_proxy.c.1088) unhandled proxy.state 3
lighttpd itself won't crash and continue to work, but it always tries to log even after drive is full.
Some relevant info:
# lighttpd -v lighttpd-1.3.13 (ssl) - a light and fast webserver Build-Date: Apr 3 2005 23:49:27
(debian build)
I was able to reproduce the error more times but I haven't tried another systems/builds.
Updated by jan over 18 years ago
- Status changed from New to Fixed
- Resolution set to fixed
r488 fixed this finally. Will be in 1.3.16
Actions
Also available in: Atom