Search results

update: 1. from Strats:"changed the Max CONN to 20, and even to 30 and noticed that there is nearly always some requests at WaitQ." 2. changed Max CONN to 50, the WaitQ disappear! otherwise, have to plan following: opcode cache wordpress super cache suExec ProcessGroup mode optimize mysql...

from the screenshot, the problem is at the vhost which WaitQ=9, if WaitQ=0, visitor won't feel slowdown. now Max CONN=10, can you change it to 20 to see if WaitQ will become 0. where to change it: https://www.litespeedtech.com/docs/webserver/config/general#phpSuExecMaxConn if still problem...

the logic regarding "the culprit is .htaccess" doesn't look correct or enough. during the high traffic, you remove the rewrite rules, then the website stops working, the load goes back --- that's because no one will access a not-working website, so the traffic go down rapidly and load drops...

the rewrite rules looks fine. questions: 1. during high traffic time ? 2. the website still working after remove these rules ? anyway, you can also try following rules while there seems no difference in theory. RewriteEngine On RewriteBase / RewriteCond $1 !\.(css|js|gif|jpe?g|png|woff)$ [NC]...

do you mean the issue has resolved by removing # Redirect root requests RewriteCond %{REQUEST_URI} ^/novo/$ RewriteRule !^/ /novo/public/$1 [L] ?

this looks wrong and won't match any URL. how about change to RewriteRule ^cms/(.*)$ /novo/cms/public/$1 [L]

You can PM me root access to your server, and access to Plesk CP,

likely. I'm not sure since not familiar with Plesk. anyway, why not have a try ? it's safe. after copy, you may need restart litespeed, then check php info page again, see if xcache is enabled or not.

I think you have to for that specific domain and now the headache thing may be "Listeners" setting. lsws web admin -> Configuration -> Listeners can't conflict with the setting in httpd.conf

watch and compare php info page under litepeed and apache, find out what is the difference regarding xcache

Thanks for the upate. so 4.3.1 will fix it --- https://core.trac.wordpress.org/ticket/33423

have you installed xcache or zend opcache as discussed in ticket ? I can take a further look into your server within 12 hours. while you can collect more info.

if you're on a shared host, then is not practical, since it'll affect all other accounts on same server. how about turn it off ?

one possible reason is "double compression" for a quick test, put a phpinfo.php under document root, search "zlib.output_compression", if it's on, set it to 0. or disable lsws gzip compression: lsws web admin -> Server -> Tuning -> Enable Compression: No see if it helps.

Hi, please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:lsapi-troubleshooting if you run Ubuntu, should use apt-get instead of yum. search pcre in above wiki page, you may get useful info for you, it looks apt-get install pcre-devel can resolve the particular...

how about #yum install pcre-devel then rebuild php

please refer https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:503-errors#lsphp_process_hit_memory_limit see if raise memory soft/hard limit, opcache > 1024 mb is ok.

great !

in web admin almost page, you can see message like "Litespeed Web Server Enterprise 5.0.4", it's same output of /usr/local/lsws/bin/lshttpd -v also in Actions -> Version Manager, you can all version history installed on your server. but no build info in webadmin at present, only...

/usr/local/lsws/bin/lshttpd -v also there are 3 text files under /usr/local/lsws/autoupdate/ platform release build