Search results

your /tmp partition is full.

http://www.litespeedtech.com/docs/webserver/config/general/#log_debugLevel

enable debug logging, then check lsws/logs/error.log and stderr.log

Are you sure that you sent SIGBUS to the lshttpd process using high CPU? This process is the watch dog process, only start new process if one of the children process dies. It should not use a lot of CPU. Can you also do "strace -tt -T -p <pid_of_lshttpd_using_high_cpu>" before killing it with...

then install again from WHM.

You may need to update to the latest 4.0.20 build manually from command line. Make sure you use the correct 64bit, 32bit package Also, try cp /home/cpeasyapache/src/httpd-x.x.x/.libs/httpd /usr/local/apache/bin/httpd if Apache failed to start as well.

Maybe cached some page should not be cached. The error is related to a security token from my google result. what rewrite rule and code patch are you using? Does a reload fix it? check the response header "x-litespeed-cache: hit" see if you get a cached page, for login user, should not get any...

force reinstall latest 4.0.20 should address this.

this should have been addressed in latest 4.0.20 package. Please try a force reinstall from LSWS web console, under "Version Managment" page.

updated 4.0.20 package.

run easyapache first.

It is likely a firewall problem. port 7080 is closed.

what do you mean ? get any response? connection reset? 403?

It is mainly for ModSecurity 2.5 features, getting closer to be compatible with gotroot rule set.

Are you using cPanel? If yes, just run easyapache first, then build matching PHP. if not, you have to build PHP from web console. Follow http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi:troubleshoot if any problem.

remove it from environment. Again, it does not fix the problem in PHP engine, just prevent the core dump files from producing. Better switch to a PHP version does not have this problem.

check phpinfo() output.

You should report this problem to PHP group, bugs.php.net . call stack back trace should be helpful. And, you can try downgrade PHP to 5.3.4 or 5.2.17.

Yes, you should increase "Max connections" to 2000 under "server"->"tuning" page.

use GDB "bt" command to list the full call stack back trace.