Search results

It is likely caused by PHP crash. You can add environment variable LSAPI_ALLOW_CORE_DUMP to lsphp5 external app configuration to let PHP dump a core file. http://www.litespeedtech.com/php-litespeed-sapi.html restart LSWS, then try the request causes 503 error, if core file produced under...

You need to increase http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout The request takes longer than that.

Please switch back to Apache, see if you get the same error. Looks like that there are some kind of syntax error with the rewrite rule. the error is from Apache. You can check the current .htaccess, there might be a syntax error on line 29 when user add a rewrite rule, when cPanel append...

Does DirectAdmin run on port 2222? I think port 2222 is hard coded in DirectAdmin response, LiteSpeed does not change the response at all. If DirectAdmin do not use absolution URL it should work fine.

Pleaes try chmod a+w /usr/local/lsws/logs/ap_cmd_param.log from command line, then try update .htaccess again.

If it still happen with 4.0.13, I may need to login to the server and take a look what exactly happened. Maybe cPanel killed all lshttpd process with signal 9(sigkill).

Can you dump the entire ENV hash array? It should be set if it is in the request header. ENV has been replaced with a hash table during LSAPI initialization, all request headers should have been added to the hash table.

We have improved LSWS 4.0.13 a little bit, it may help with your 503 errors. Please upgrade to 4.0.13, if you have done that before, please upgrade again with "Force reinstall" from web console, or upgrade manually from command line.

Maybe it require register_long_arrays http://www.litespeedtech.com/support/forum/showthread.php?t=3757

There was a bug in LiteSpeed PHP-lsapi 5.3 release that may cause 503 errors. If you build PHP from our web console, please remove php-litespeed-5.3.tgz from /path/to/lsws/phpbuild/ directory then rebuild PHP. If you use WHM plugin to build PHP, you need t remove...

You can change /path/to/lsws/admin/conf/php.ini locate "allow_url_fopen" and change it to "allow_url_fopen = On" This has been addressed in 4.0.13 .

This is not right. prefix should be /usr/local/lsws/lsphp5 You can try add configuration parameter see if it can be fixed. Or, you can install lsphp5 to /usr/local

Maybe it related to http://www.litespeedtech.com/support/forum/showthread.php?t=3757

suphp is CGI based, it always pickup the php.ini under current directory. LiteSpeed SuEXEC follows mod_php, you can use php_value directive in .htaccess to override some php configuration.

You can try let PHP dump a core file with setting LSAPI_ALLOW_CORE_DUMP environment in lsphp5 external app. http://www.litespeedtech.com/php-litespeed-sapi.html with the core file, you can get an idea what causes PHP to crash, then file bug report to the vendor.

Check the CPU utilization of lshttpd from "top" output. If you serve a lot of static content or HTTPS traffic, or your server is under heavy attack, you may need to upgrade the license.

It is controlled at server side. Auto upgrade to 4.0.13 has been enabled now

Please try the latest 4.0.13 release. if 503 still happens, we can take a look at your server.

Please give detail steps in order for us to reproduce the problem in our lab.

directadmin create too many useless vhosts. you can custom a httpd.conf without those vhosts for Litespeed.