mod_proxy hang, log spew (upstream 2144)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lighttpd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: lighttpd
Release:
Description: Ubuntu 10.04.1 LTS
Release: 10.04
lighttpd:
Installed: 1.4.26-1.1ubuntu3
Candidate: 1.4.26-1.1ubuntu3
Version table:
*** 1.4.26-1.1ubuntu3 0
500 http://
100 /var/lib/
Expected:
In case the lighttpd proxy module detects a connection has been closed on it from the other end, it logs an error, closes its own end of the connection and continues working.
What actually happens:
The problem is logged, but the connection is not closed. The problem therefore continues to get logged until there is no more disk space.
Description:
I am using lighttpd as a proxy to apply ssl to another web service. After some time, my disk had become full. The error.log file was filling the disk (many gigabytes) with consecutive lines like this:
2011-01-25 13:13:33: (mod_proxy.c.853) write failed, remote connection close: Broken pipe 32
2011-01-25 13:13:33: (mod_proxy.c.853) write failed, remote connection close: Broken pipe 32
2011-01-25 13:13:33: (mod_proxy.c.853) write failed, remote connection close: Broken pipe 32
This is a bug in the proxy module in that it senses the connection was broken, logs that and proceeds not to close its own end of the connection. This way the error keeps happening over and over.
This problem was reported to the lighttpd project as bug #2144:
http://
and, according to them, fixed with this small patch:
Please apply this bugfix to the package in Lucid Lynx (10.04).
Changed in lighttpd (Ubuntu): | |
status: | New → Confirmed |
Effects me too.
I switched from Ubuntu 8.10 to Ubuntu 10.04 and this problem started appearing.