Search results

After we belive that the too much ruby process problem has been truely fixed. :)

No need to lower it. Web admin interface or the error log file has the version number of LSWS. "gem list" will show the LSAPI version if installed through RubyGem, if installed manually, you should know it. ;-)

that's because the second request condition has not been met, maybe you should add an extra flag [OR] to the first rewrite condition, when either condition has been met, the rule will be executed.

You can try LSAPI 1.8 at http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.8.tar.gz , proc manager is disabled when 1 connection allowed for each app.

We improved the process manager in LSAPI, the spawning extra processes problem should be fixed completely. You can try LSAPI 1.8 at http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.8.tar.gz .

Rails framework causes the high CPU usage. We believe rubylsapi is the fastest IPC implementation for ruby. just take a look at our comparison between LSAPI and FCGI on our blog. http://blog.litespeedtech.com/. ruby itself is pretty fast, should be comparable to PHP, it will become pretty slow...

OK, the bug has been identified and fixed. The reason is the customized error page for 401, the authentication header is lost when LSWS perform a internal redirection. I will PM you when a package available for you to try. Thanks for your bug report.

Yes, proc manager should not be used when only 1 process is allowed per rails application. So, you think that only allow 1 ruby process is allowed for each application hosted in shared environment?

IM does not relate to LSWS directly, as it is called by PHP as a shell command. It should be OK if "process limit" for lsphp external application has not been set too low. You can check lsws/logs/stderr.log and lsws/logs/error.log for runtime errors produced by PHP or IM, if any.

OK, thanks! I will investigate.

LSWS alone cannot do monthly limit, it only throttle the realtime bandwidth usage, something like 12KB/second that. For monthly limit, you need to run a bandwidth statistic job to calculate the bandwidth useage based on access log or bandwidth log. CPanel has this kind of feature and LSWS...

Can you please post the whole .htaccess file if there are more configuration directives.

Please upgrade to Ruby LSAPI 1.7 if you have not done so. What you observed is normal for current release because the way rails process being started. There is one ruby process which only fork/manage children ruby worker process to handle requests. The process manager in the parent process is...

Yes, that true. LSAPI 1.7 should do much better job.

OK, good. Please double check the php.ini, make sure the same configuration as that of Apache has been used.

I think you may need to build your own PHP binary with similar options like that of apache mod_php, if you have not done so yet. How to is available in our Wiki.

jp_n9: Please upgrade ruby LSAPI to 1.7. Your 'Max connection' is way too high, your VPS does not have enough memory to start 300 ruby processes. your server could be DoS attacked by a simple request flood. please try '10' first. I I will take a look at your server if the problem persist with...

PHP4 & PHP5 should be started in suEXEC mode with 2.2.1 release.

Yes, the fix is in 2.2.1 release, forgot to add that in the change log as it has been for a while. :)

When LSWS being started gracefully, all associated ruby processes should be killed after all pending requests has been served. The new LSWS instance will start it own group of ruby processes. The problem is that ruby processes won't die after being killed by LSWS. We spent some time on work...