Search results

It is about time to test water now. The latest 4.0.10 build is very stable.

We have uploaded a new 4.0.10 build, it should be the final build. Have been tested on a few busy site that experience 503 errors, the latest build is very stable. So, all user who have manually upgrade to 4.0.10 release should download again and do a manual upgrade again.

for using per user php.ini, please check http://www.litespeedtech.com/support/forum/showthread.php?t=2915&highlight=PHPRC

suPHP does not support php_value, php_flag in .htaccess, it uses php.ini for that account. php_value and php_flag is safer as certain PHP configurations are not allowed. Litespeed can be configured to use the per user php.ini via PHPRC environment variable in lsphp5 external app configuration...

Do not understand what exactly is the problem.

LiteSpeed assign listeners to different process. If you distribute sites to multiple shared IP or you have many sites with dedicate IP, LSWS will distribute them to different lshttpd process (assuming you have 2-cpu license or above). For a single large site, you may create the listener...

It usually caused by PHP crashes. have you been able to nail it down?

4.x should work better on this.

make sure to get the 4.0.10 release package. 4.0.9 still have random 503 issue.

To stop a DDoS attack, you have to some how identify the source of the attack, and block them at firewall.

For this kind attack, each IP will not hit the limit in order to ban it. you may have to do some access log analysis. Say, find and block top 'n' IPs that access the same URL in the last 'n' minutes.

Please search the forum to find the answer.

It wont work that way. once the max connections reached, no more TCP connections will be accepted by LSWS, so it wont be able to send back a redirect response. You have to use something like DNS load balancing, or use our Load balancer in front of the web server farm.

Since you use VPS, memory buffer is limited. You can try set "Max I/O Buffer Size" to "0". http://www.litespeedtech.com/docs/webserver/config/general/#inMemBufSize

Please try a manual upgrade to 4.0.10, just change the version number in the download link to get it.

nothing important, no need to upgrade.

Maybe you are using request rate throttling? http://www.litespeedtech.com/docs/webserver/config/security/#dynReqPerSec

Have you noticed change in memory usage? I remember the last time I tried, seems it does not help as expected, maybe still missing something to turn it on. have added code Yes, you are right, a graceful restart bug was introduced in 4.0.9, it has been fixed in our 4.0.10 build.

There is what happened during GRACEFUL restart, while start a new instance of LSWS, the old LSWS tries to finish the current pending requests, so it need to keep the old Ruby processes alive, so, the old LSWS instance and ruby processes may not terminate immediately even the new LSWS instance is...

It could be ture for suEXEC, each user only get a limited number of PHP processes, if all are busy or hung, no more PHP request can be processed for that user until a PHP process becomes available. PHP run out of web server process, web server does not have tight control on it. you need to...