lighttpd uses most parts of the physical memory and causes out of memory crashes
Our lighttpd uses around 3gb of memory and causes out of memory crashes from time to time.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6318 www-data 16 0 3983m 2.9g 860 D 6 94.4 0:52.17 lighttpd
The server is running Debian etch x64. I don't think this memory usage is normal? We use mod_redirect and thought the problem is maybe solved with #874, but upgrading to 1.5.0 r1992 didn't help either. What else can we try?
Updated by Anonymous almost 12 years ago
For now the problem actually stopped as sudden as it started. We are pretty sure we were attacked. Check the two attached ganglia graphs about memory usage.
We could share the config in private to avoid revealing even more information about possible attack scenarios, if you understand.
Updated by stbuehler over 11 years ago
The valgrind trace is not really helping as long you didn't have a complete one (i.e., terminate lighttpd).
Do you use server.max-worker? See http://trac.lighttpd.net/trac/wiki/Docs%3AMultiProcessor - that may be the source of your access.log problems.
Your config and a little description what your server is doing (serving big files with fastcgi? ssl? ...) would be nice too.
And just as a process is using much memory that doesn't mean it leaks!
Updated by Anonymous over 11 years ago
Valgrind: OK sorry, didn't know that.
Our solution was to switch to Apache for a period of time, finished coding of our new site and cleaned up our rewrite rules a lot. Since then the problem is gone. We don't know if it was the new php coding or the config cleanup which solved it in the end.
Also available in: Atom