Search results

May I have your test script? Or login to your server to take a look? Enable debug logging?

I don't think 4.0.9 will make difference on this, but it is recommended to upgrade to 4.0.9 .

Understood. You may want to go back to 4.0.6 as the 4.0.7 release may have random 503 problem.

Are you using control panel? or everything configured from lsws web console natively? If possible, please PM me a temp root access, I will check what is going on.

You can switch to another version from the web console if you have not uninstall the older version.

If you install LSWS to a user's home directory, and the user's home directory has permission mask 0700 or 0750, you could have this problem unless you run lshttpd as this user. you should install it to /usr/local/lsws or /opt/lsws if you have root.

From which version you upgrade from? What is the state of running lsphp5? parent PID? strace output? Are you using PHP suEXEC?

Looks like out of disk space on the partition that LSWS was installed to.

4.1RC1 release package has been updated with all the fixes in 4.0.x releases. Hopefully, it will be the last build of 4.1RC1, we can move on to 4.1RC2

Usually, the dummy bots only request one URL, so the page is cached in memory by kernel, multiple CPU license wont cause higher disk I/O. AIO will help when the I/O wait of your server is high. I don't think CiscoGuard really help on this, so it is better off not using it.

Ok, this problem is fixed. You can download 4.0.9 and manually upgrade again or wait for 4.0.10

We recommend eAcc + /dev/shm , theoretically, it is in a HDD, but actually is in memory. Right now, PHP suEXEC starts standalone PHP process individually, so the in memory cache cannot be shared at all.

Are you using cPanel? If yes, use the "Build Matching PHP" feature in WHM plugin. If you have to use the "compile PHP" feature from web console, you can set "Install Path Prefix" to "/usr/local", the default open_basedir should work. If you need to install PHP to /usr/local/lsws/lsphp5, you...

Xcache is not recommended for shared hosting using suEXEC as it does not have a shared on disk storage. If you want to use the latest PHP release, eAccelerator may not be up-to-date, just be cautious.

We will investigate this issue. Thanks for bringing this issue to our attention.

Maybe change PHP suEXEC to "User's home directory Only" will fix that. http://www.litespeedtech.com/docs/webserver/config/general/#phpSuExec

You can check /usr/local/apache/log/error_log, there will be many entries like a IP hit the connection hard limit or the soft limit. You can write a script to parse the list of IP that hits the hard limit, then block them with iptables.

Thanks for the update. Glad you found a working opcode cache for 5.3.

Is https listener configured natively in LSWS console? You may need to add both "domain.com" and "www.domain.com" to the listener to vhost mapping now. 4.0.9 is available now.

4.0.7 and 4.0.8 may have random 503 errors, 4.0.9 should have addressed that. please upgrade.