LSWS freaks out on Full Cache event

[meto]

LSWS started to restart itself when I got 100% on my tmpfs for cache. I think it's behaviour should be addressed otherwise than throwing 503 which leads to restart...

 

[webizen]

it is recommended old caches get purged periodically (cronjob) and there is enough space available for cache.

 

[meto]

It does every ten minutes. Anyhow this behavior should be somehow addressed (maybe disable cache for 60 sec?).

 

[webizen]

if tmpfs for cache is full, no cache file will be created in tmpfs. however, lsws should continue to serve as if cache being disabled (not enabled). 503 error is likely due to something else. can you paste here anything in error.log around the time when 503 error occurs?

also is the "restart" in "throwing 503 which leads to restart" referring to LSWS restart or PHP restart?

 

[meto]

I got errors like:

At [11/Jun/2011:00:10:48 +0200], web server with pid=9762 received unexpected signal=7, a core file is created. A new instance of web server will be started automatically!

Please forward the following debug information to bug@litespeedtech.com.
Environment:

Server: LiteSpeed/4.1.1 Enterprise
OS: Linux
Release: 2.6.18-238.5.1.el5.028stab088.1
Version: #1 SMP Tue Mar 29 21:02:16 MSD 2011
Machine: x86_64

If the call stack information does not show up here, please compress and forward the core file located in /tmp/lshttpd/.

[New Thread 9765]
[New Thread 9764]
Core was generated by `litespeed'.
Program terminated with signal 7, Bus error.
#0 0x00002b2ee4628863 in ?? ()
#0 0x00002b2ee4628863 in ?? ()
#1 0x00002aaaaaac0eb9 in ?? ()
#2 0x00002aaaaaada000 in ?? ()
- Pokaż cytowany tekst -

 

[webizen]

you need gdb (gnu debugger) and lsws dbg (http://www.litespeedtech.com/packages/lsws-4.1.1-ent-x86_64-linux-dbg.tar.gz) both installed.

 

[meto]

I've mailed corefiles and bug info.