Search results

I think should strace the lsphp5 doing the backup to find out exactly what happened. strace -tt -T -p <pid_of_lsphp5_doing_backup> whether it is killed by LSWS, or due to PHP internal limit.

It looks like CloudLinux resource limit was hit, and causes 503 errors in your case. You should be careful with "PHP suEXEC max conn", if set it too high, while CageFS/LVE limit was not high enough, it will cause trouble during traffic surge.

If you still experiencing this problem http://www.litespeedtech.com/support/forum/showthread.php?t=6412 should upgrade again. It may not have any effect on memory limit though.

update to the latest 4.2.1 release may address this. /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

It is recommended to update 4.2.1 installation to the latest build, either force reinstall from web console, or from command line, do /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1 With the latest build, you may need to explicitly set "Auto Start" to "Through CGI daemon" for lsphp5 external...

4.2.1 release has been updated to address this issue. Please do force reinstall or update manually from command line with command /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

there is a new update of 4.2.1 release, please upgrade /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

If still have problem, please send temp root access to bug@litespeed..., we will investigate.

Please send error.log and stderr.log during the 503 problem to us, or let our staff to collect those log files from your server.

Can you also send us the error log around that time? Need to know what happened by that time. Or, let our staff login to take a look. send email to bug@litespeed... or PM temp root access.

403 status is triggered by , instead, avoid using "-indexes", use .htaccess could be disabled by your server configuration.

Please email to bug@litespeed... or PM us temp root access, we can take a look.

Please email to bug@litespeed... or PM us a temp root access, we will take a look.

Please add following rewrite rules to .htaccess under public/ folder

That's normal, once we push version 4.2.1 through our auto-update system, it will be labeled as the latest release. Just ignore that for now.

Please try 4.2.1 /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

Seems you have directory autoindexing enabled. turn off directory index should fix this.

Due to the relatively high cost of checking against mod_security rules for each every request, LiteSpeed selectively skips mod_sec for static files. if you check the web site against a dynamic page (PHP page), it should work.

Yes, there is a updated version of RailsRunner.rb, please manually upgrade to 4.2.1 release with command /usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

Those errors are due to Ruby/Gem/Rails update. It was working well in production for many years. For the "require lsapi" error, you need to locate the gem folder, like /usr/lib64/ruby/gems/1.9.1/gems/ruby-lsapi-4.0/ Just follow the instruction in README to manually install it into ruby system...