Search results

is litespeed process still running ? #ps -ef|grep litespeed if still running, you can kill them directly #killall litespeed until no longer see it by ps then #/usr/local/lsws/bin/lswsctrl start

no need do it -- since it says lsphp5 already match with apache's.

it looks the problem is lsphp5 taking too much time to complete a request. thus it queues up. you can strace a lsphp5 process to find where it's blocked at.

please check if mysql is the bottle neck. run #mysqladmin processlist help to tell some information. looks like too many incoming requests -- like a DDOS. you can try set lsws web admin->Server->Security->Per Client Throttling to limit request rate from single IP. see if it'll improve a bit...

please refer http://www.litespeedtech.com/support/forum/threads/solved-permissions-issues-with-new-accounts.10076/#post-82944 and http://www.litespeedtech.com/support/forum/threads/solved-permissions-issues-with-new-accounts.10076/#post-83092

PHP suEXEC Max Conn: 500 this is too large and caused the error you reported. the default is 10. please back to 10, then increase it gradually, by step of 5 ot 10. monitor lsws web admin -> Actions -> Real-Time Stats especially WaitQ column. if it's always 0, or being non-0 very short time...

not sure if you've done these: http://php.net/manual/en/mssql.requirements.php "To use the MSSQL extension on Unix/Linux, you first need to build and install the FreeTDS library. Source code and installation instructions are available at the FreeTDS home page: » http://www.freetds.org/"...

not sure if it's because of cache. try disable cache for https, see if both works fine. to do this, in rewrite rule, add RewriteCond %{HTTPS} !on i.e., RewriteCond %{HTTPS} !on RewriteCond %{REQUEST_URI} !^/(wp-admin|wp-login.php|wp-cron.php) RewriteRule (.*) - [E=Cache-Control:max-age=43200]

Hi, same steps to build apc.so: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:apc

should be RewriteCond %{REQUEST_URI} !^/(wp-admin|wp-login.php|wp-cron.php) RewriteRule (.*) - [E=Cache-Control:max-age=43200] >I've tried to turn off "Cache Request with Query String" "Cache Request with Cookie" "Cache Response with Cookie" at litespeed server control panel please do not...

in native virtual host case, please refer lsws web admin->Configuration->Virtual Host Templates->PHP_SuEXEC how this template archive that goal. I think 2 necessary settings: 1. Security->ExtApp Set UID Mode: DocRoot UID 2. External App -> define $VH_NAME_lsphp then "Script Handler", map...

if virtual host is from apache's httpd.conf, lsws web admin->Server->General-> PHP suEXEC:Yes PHP suEXEC Max Conn:10 (or 15, 20, 30 ...)

please keep monitoring your server .. if this happen frequently or just one time can't make any conclusion base on above info which is limited and not enough.

this lsphp55 error can be ignored. to have it disappear, just run #ln -s /usr/local/lsws/fcgi-bin/lsphp5 /usr/local/lsws/fcgi-bin/lsphp55 >2014-12-14 02:30:40.137 [STDERR] Unable to create lock file: Disk quota exceeded this message looks great. check if the disk is full, without any free space...

these INFO / NOTICE message haven't any useful info in it. any message in stderr.log at that time ?

replace with RewriteCond %{ENV:good_pass} !^$ RewriteRule . - [R=403,L] see if it works

please compare what user the lsphp process run as. and the file's ownership/permission(and it's parent directory) it's a unix ownership/permission issue, should not relate to litespeed version.

2 ways: 1. build memcached.so yourself. refer: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:apc same steps as building apc.so 2. through rpm: refer: http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:php:rpm

in lsws web admin, when add Domains to a listener, the pop up tip say in your case, www.shop.domain.com map to a virtual host, since www is removed, so it's shop.domain.com it's duplicated with 2nd mapping. suggestion: in 1st mapping, change www.shop.domain.com to www.domain.com, 2nd mapping...

please edit /usr/local/lsws/conf/httpd_config.xml change <enableChroot>1</enableChroot> to <enableChroot>0</enableChroot> then restart lsws /usr/local/lsws/bin/lswsctrl restart your issue should be resolved.