Search results

We'll investigate this issue for sure. This is the first time I'm aware of it. Thanks for reporting. and just now I tested on apache. yes, as you stated, apache can handle DirectoryIndex pages.php?pageid=7 as expected.

reproduced the issue on lsws, not tried on apache yet. the workaround is to use the powerful rewriterule: DirectoryIndex pages.php?pageid=7 ===> RewriteEngine On RewriteRule ^$ pages.php?pageid=7

recommend starting from 2-CPU/core license, then upgrade/downgrade/keep the license according to your server's load/traffic etc.

because you set "Max Connections = 1" try: Max Connections = 5 Env PHP_LSAPI_CHILDREN=5 keep Instances = 1

but I did tests on www.casafree.com/test/info.php looks like not cached. try following slightly modified rewriterule: RewriteEngine on RewriteRule (.*\.php)?$ - [L,E=Cache-Control:max-age=120]

this means 1024 bytes, too small. change it to 100k or leave it blank, the default size is 128k. to ensure /diskcache exists and writable for user which run litespeed(nobody for example)

please try: Enable Cache:No Cache Request with Query String:Yes Cache Request with Cookie:Yes Cache Response with Cookie:Yes Ignore Request Cache-Control:Yes
 Ignore Response Cache-Control:Yes Enable Private Cache: No* Private Cache Expire Time (seconds): 120 >I have recompiled...

how long will it take to send out 900 emails ? over 5 minutes ? try to increase Server->Tuning->Connection Timeout (secs) default is 300 seconds.

when PHP_INI_SCAN_DIR set, /home/xxxx/public_html/phpCopy.ini is read. comment out this line in phpCopy.ini /usr/local/Zend/lib/Guard-5.5.0/php-5.3.x/ZendGuardLoader.so phpinfo() works fine. and looks the whole site works too. so still this ZendGuardLoader.so issue.

Thanks for the update.

have you built matching php ? compare phpinfo() under litespeed and apache, to be sure first they matches.

litespeed + lsphp5 is optimized to reduce 500/503 errors. for example, if one request is failed to serve by lsphp5 process, lsphp5's parent process may try start another lsphp5 process to serve the request, thus to reduce 500/503 error the end user can see. when one lsphp5 has handled many...

can you do what suggested in previous post: 1.force-reinstall 4.1.11 to latest version 2.stop lsws completely, then start it, not restart gracefully use #/usr/local/lsws/bin/lswsctrl stop and / or #killall litespeed to stop it completely. and use #pstree -p | grep litespeed to check...

right. what's the value of Load Apache Configuration:Yes/No ? if No, all other settings under "Using Apache Configuration File" will be ignored.

Thanks for sharing. with 2-CPU license lsws, you may not need varnish -- to use litespeed page cache instead.

it's kind of hard-tracing issues ... it may due to other bug fixes in 4.1.11(e.g. memory-leak etc) which fix the issue as well. let's assume 4.1.11 has no such issue any more -- if still happen, please re-open this thread.

this indicates suExec is enabled. but also this should be impossible. this is the issue -- why you set to No, but lsphp5 running as ec2-user.

following output will help: #pstree -p #ps -ef|grep lsphp5

I think that'll work.

please refer http://www.litespeedtech.com/support/forum/showthread.php?t=5676 see if any helpful