Search results

Not possible with LiteSpeed. Custom logging probably will be supported in enterprise edition in the future.

Why not use our easy rails setup, check out the wiki.

Most issue listed above should have been addressed in 3.0RC1 release. Except #4, mod_perl suexec has not been added, I think it might take too much memory in shared hosting environment, Perl uses a lot of memory.

3.0RC1 release is available now.

You can try other opcode caches, switching to 32bit PHP binary, etc.

1.11 is the latest.

Please check your "Max Idle time" under "ruby" tab. Leave it not set or increase it.

Anything in stderr.log? 503 error usually is caused a PHP error.

Please try the fix in http://www.litespeedtech.com/support/forum/showthread.php?p=3710#post3710 with your original code, see if it works. :)

The fix actually turn out to be very simple. :) Add Dir.chdir( ENV['RAILS_ROOT'] ) at the beginning of RailsRunner.rb, before the first "require ..." Please let me know it fixes your problem or not.

Yes, it is a bug in current ruby-lsapi. Will be address in next release. Which directory should be set as CWD in Rails? $RAILS_ROOT/public or something else?

Alex, Better stay with PHP 4 if PHP5 is not really required. PHP4 is faster. What you need is to setup a opcode cache like APC. APC binary for php 4.4.4 is available under lsws/lib/ directory. You can modify the php.ini showed in the phpinfo page to load the APC extension. The APC related...

Glad you find the problem, we will address the compatibility issue in next ruby-lsapi release for sure. :) What exactly is the result of getcwd() under other environment? #{RAILS_ROOT}/public?

I tried your configuration, proper 404 page was returned. LSWS only start one ruby process, this process will fork children process to handle all requests. This way, the startup cost of RoR framework is the lowest. To get PID of the children process, send a normal request without resulting in...

The lsws log shows that, ruby just simply closed the connection, not sending anything back. The ruby process you straced is the parent ruby process which does nothing but accept a connection and fork a child ruby process to handle the request. I really interested is what happened in the child...

The install script should prompt: Setup up PHP [Y/n]: Default is yes. It should be enabled unless you select "n". Please make sure to select "Reinstall" when you run the install.sh, "Upgrade" will not show that option.

After a few minor fixes, LSWS 3.0 works well with the httpd.conf generated by directadmin. Please wait for 3.0RC1 release.

Are you using a 404 error page? Is it a static file or handled by rails as well. That could be the cause of 503 problem.

We need more information to figure out what exactly causing the problem. Please try turn on LSWS debug logging by changing debug level to "high", post the section of error.log for the failed request. Strace the ruby process. First send a good request to let the ruby process start, then do...

That's "Connection Timeout", how long the server keep a idle client connection alive, has nothing to do with ruby process idle time. You should change "Server"->"Tuning"->"Connection timeout" instead.