Search results

Please do a manual download and upgrade for this time. it has been addressed in 4.0.13.

Or, use php_value engine off and php_value engine on in .htaccess to control PHP support.

Please download 1.7 release again and do a manual update, see if the problem goes away.

Does it start to happen with 1.7. Looks like something wrong with OpenSSL. Which platform are you using? linux i386/x86_64 or something else.

So, you think it is safe to remove those. it was in the original RailsRunner.

150 is too high, you should try something like 10 or 20 at most for shared hosting server. check the number of PHP processes running. Check real time status report see if WaitQ stay at zero at peak hours. It is completely between PHP and MySQL, make sure you use the same PHP mysql client library...

User can only override less important configuration via .htaccess with php_value just like with mod_php. php.ini in user's home directory does not work.

It is one large vb forum, you need to increase "PHP suEXEC Max conn" http://www.litespeedtech.com/docs/webserver/config/general/#phpSuExecMaxConn

After trouble shooting an issue with radiantCMS, I come up a new RailsRunner to address following issues: 1. Failed to detect Rails version when application bundled with Rails like radiantCMS. use Rails::VERSION::STRING to get rails_ver now 2. Add our own rack handler into RailsRunner, so...

scgi is not supported.

http://www.litespeedtech.com/support/forum/showthread.php?t=2814

Try a force reinstall from LSWS web console. Or download the package and run the install.sh from command line, no service interruption either way.

try quoting "/usr/bin/php -q"

Maybe you should use remove "#!/usr/bin/php -q" from sample.php

Just login to shell, and tail -1000 /usr/local/apache/logs/error_log to show the last 1000 lines. change the number to make sure it include the log related to 500 error.

You need to check /usr/local/apache/logs/error_log, Looks like some require feature was not compiled into apache, you need to fix it with easyapache.

Have you download and upgrade to the latest build of 4.0.13? It will reduce false alarms. Usually "Connection reset" is caused by PHP crash in middle of processing a request.

It is a PHP feature, not directly related to LiteSpeed. should work fine if corresponding PHP module is available.

Maybe you need to use #!/usr/local/bin/php -q to silence PHP header output.

You can copy admin/conf/php.ini from a expanded installation package.