[solved] Litespeed webserver stops working while cleancache script is runnning

[gnu.smtp]

Hello guys,

We have a number of server with litespeed running and most of them is having issues with the cleancache script running. While running these we are not even able to do any thing on litespeed admin, not able to switch to Apache nor even able to get the sites working while running these scripts.

Any body facing the same issue any suggestion or fix for this.

4346 ? DN 0:00 find /tmp/lshttpd/swap/e -type f -mtime +1 -delete
14347 ? DN 0:00 find /tmp/lshttpd/swap/e -type f -mtime +1 -delete

We are not even able to kill these process and only thing we can do is to reboot the server to get the apache/litespeed working.

Any idea why those are not able to get killed ? and what can be done to get this fixed for ever

[webizen]

Originally Posted by gnu.smtp

...
4346 ? DN 0:00 find /tmp/lshttpd/swap/e -type f -mtime +1 -delete
14347 ? DN 0:00 find /tmp/lshttpd/swap/e -type f -mtime +1 -delete

We are not even able to kill these process and only thing we can do is to reboot the server to get the apache/litespeed working.

Any idea why those are not able to get killed ? and what can be done to get this fixed for ever

/tmp/lshttpd/swap is used by LSWS swap. you need point your cache storage to a different place (out side of /tmp/lshttpd/swap)

[gnu.smtp]

Hello,

Thanks you,

if we move this to home folder, will that be albe to get deletted if needed ? Also Where to get this done ? from litespeed admin panel ?

[Wirta]

It's interesting to note that litespeed is having issues with cleancache script. I haven't tried myself but going to give it a try and see how I can help you. I'm not an expert however I will try my best. Good luck and let me know if you're able to solve the problem.

[webizen]

Originally Posted by gnu.smtp

Hello,

Thanks you,

if we move this to home folder, will that be albe to get deletted if needed ? Also Where to get this done ? from litespeed admin panel ?

Yes, you can point your cache storage path to somewhere under home folder such as /path/to/home/dir/diskcache. you need to manually create the folder first and point that in LSWS admin console (Configuration => Server => Cache)

[gnu.smtp]

Hello,

We have changed the cache directory and swap directory to /home partition.

But this has not helped with the issue. Also it is not possible to terminate them, once they start running.

We cannot afford this type of frequent downtimes with a paid solution like litespeed.

[webizen]

You need to leave swap directory in /tmp/lshttpd unchanged and ONLY change diskcache directory to a different place (e.g. /home/diskcache). The cleancache script should only purge files under cache directory NOT others (i.e. swap, etc). Your problem is cleancache script removes files under swap as you mixed cache and swap together causing lsws inaccessible.

[gnu.smtp]

Hello,

We had swap set to default, ad made the change when the issue persistsed even after changing cache to /home.

The current setup is as follows.

swap directory : /tmp/lshttpd/

cache directory : /home/litespeed/cache

Caching is disabled on the server. We are monitoring with this setup and will keep you posted.

[NiteWave]

swap directory : /tmp/lshttpd/

the default swap is /tmp/lshttpd/swap

is your /tmp NFS ? it may be very slow per some of our past experience.

if so, better to use local disk as /tmp

also, please run iostat to check if some of hard disks have high i/o wait issue.

[gnu.smtp]

Originally Posted by NiteWave

the default swap is /tmp/lshttpd/swap

I have changed this to /tmp/lshttpd/swap. But we have problems with cron/script clearing swap directory also.

Originally Posted by NiteWave

is your /tmp NFS ? it may be very slow per some of our past experience.
if so, better to use local disk as /tmp

all drives on the server are local.

Originally Posted by NiteWave

also, please run iostat to check if some of hard disks have high i/o wait issue.

IO wait goes a bit high when the script/cron runs. But this affects only httpd service. Also we are unable to switch to apache when the issue occurs.

Thank you.