Search results

The log shows that the RailsRunner.rb failed to start. You should check other Rails 2.3.x discussion. I think your RailsRunner.rb need to be updated with the one coming from 4.0.3 release to get Rails 2.3.x support.

This problem has been confirmed in our lab. released ruby-lsapi 3.5 to reinitialize the random generator automatically.

I think it is the rand() function in Rails, the random generator has been initialized only once when the Rails Application starts, then RailsRunner for LSWS will fork() from the parent process, to process a request, then exit if idle for a while, then fork() another process when a new request...

You should not use chroot with a hosting control panel unless the control panel support chroot. For the security rule, if you want to block something like a URL "/blabla" Just add a rule in modsec2.user.conf like SecRule REQUEST_URI "/blabla" then create a file to serve url "/blabla"...

First, please upgrade to 4.0.3, Second, add a testing mod_security rule, third, try to hit the testing rule with a crafted request fourth, checklogs/modsec_audit.log

It appear that some WordPress blog has a plugin talks to remote servers at the end of loading the home page. the plugin has a directory name "wassup". I think disable that plugin will speed things up.

It is complicated, anyway, 4.0.4 build should have this addressed. You can give it a try.

Yes, please keep us posted when it is available, so we can add som generic code like "clear_active_connections!" to address it in RailsRunner.rb .

Yes, you should set "Instances" to "1". Also try adding environment variable LSAPI_PGRP_MAX_IDLE=86400 The ruby process should be started when LSWS start and stay alive. so the slow start should be avoided.

It is a <LocationMatch /index.php> configuration in mod_security configuration, exclude.conf, causing trouble. It works properly after commenting it out.

maybe it is too early as the connection to memcache was established after loading environment.rb. Please try to patch RailsRunner.rb, at where "ActiveRecord::Base.clear_active_connections!" is called.

Maybe too many running PHP process, reduced "max idle" time to 10 seconds for lsphp4 and lsphp5 external app. see how it goes. site loading speed is fine to me, unless you PM me the site that are very slow.

It should be fine. environment.rb only get loaded once I think.

Please PM the admin console login, I will take a quick look.

Just manually patch /usr/local/lsws/conf/httpd_config.xml, found <perClientConnLimit>, check the value of <softLimit> and <hardLimit>, set it to a large number like "1000". Please let me know the current value, your OS? 32bit? 64bit? "-1" is not a valid value.

Yes, need to reset the connection to memcache. Just close all connections after the initialization.

has the issue resolved? Maybe you need to reset your serial number and reinstall from scratch. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:license:all_about_licenses

It will be much more efficient if DOCman can use "Internal redirect" instead of streaming the file through PHP. http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed:wiki:feature:internal_redirect Just test if it is a LiteSpeed Web Server, send back a "X-LiteSpeed-Location: ..."

If you use PHP suEXEC, and your site get high traffic volume, you probably need to increase "PHP suEXEC max conn". http://www.litespeedtech.com/docs/webserver/config/general/#phpSuExecMaxConn check the real time statistics report, for the external application report. If "WaitQ" is not zero...

I could not reproduce what you described. the PHP version is consistent. You can give it a try. For subdomain, you should put the .htaccess under the document root, that's right way, not in the subdomain root directory. LiteSpeed does not like Apache which go through all .htaccess along the...