Search results

Looks fine, is there any other PHP related external app configuration? maybe we need to login to take a look.

Please show us the full lsphp5 extapp configuration.

Are you sure that you changed the correct external app configuration? server level? vhost level?

http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:lsapi make sure to copy your existing configuration from phpinfo().

Maybe you need to rebuild your lsphp5 binary, the current binary is using an older version of LSAPI which is not capable of running suEXEC daemon mode. please check phpinfo() output for the SAPI version, the latest version is "LiteSpeed V6.7". Are you using a control panel?

That's normal. all of those processes has a common parent process, 11203, you need to check that process, it should be a lsphp5 process running as root. if it is lscgid or lshttpd, you are not using suEXEC daemon mode.

Generally, higher I/O wait is caused by higher disk I/O activities, why there are more disk I/O activities, I cannot answer it without checking the server. there are many factors. But you need to need to identify where the disk I/O activities coming from. you can use iotop, then do some strace...

If this server is constantly dealing with dynamic content with request/response body larger than 1MB, LSWS may use temporary file to store the body data, which could increase disk I/O activities, cause higher I/O wait. There could be other factors, you should check output of "iotop" was well.

Only something tell LiteSpeed to restart, sometimes, control panel will ask web server to restart to rotate log or apply configuration changes. it is logged by our server. It is likely means that your PHP is not using suEXEC daemon mode. it should not happen with suEXEC daemon mode. You should...

When LSWS restarts, it needs to restart all children processes started by the web server, what you see is likely due to server restarts. Maybe you can try to minimize server restarts? If you run a single large web site, do not need changing user id for different account. you can manually start...

You can try changing www.shop.domain.com to ww?.shop.domain.com .

tell them to do a force reinstall to get the latest build of 4.2.19.

Not possible at this moment.

your load is coming from mysqld, so you need to optimize your table index and SQL query. Turn on slow query cache, check "msyqladmin processlist", extended status etc to find out where is the bottle neck. Usually, a missing table index on a large table could cause big trouble.

need to see "top" output.

This issue should have been addressed in our latest 4.2.19 build. Any user reporting this issue should upgrade to 4.2.19 with /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.19

Sure, we will work with our client to figure it out. I probably know what is problem. Need to find a solution. Will facebook side takes a "200" response instead of "206 Partial Content" response contains the whole file?

For LSWS built-in page cache, it is a complete waste to cache static file in file system, then serve it from cache as static file instead of serving the original one. The expire time of an cache entry is stored in the file for that entry. In your case, only when the previous cache entry has...

Not sure what is your issue. Please start a new thread if you have any issue with litespeed.

If everything should go through our anti-DDoS service, you can only allow traffic from our IP. Otherwise, proxy based anti-DDoS service wont work if your IP was targeted.