Search results

add this to our to-do list.

How big the uploaded file? Have you adjusted the request body limit under "Server"->"tuning" tab?

Have you followed this http://www.litespeedtech.com/how-tos.html#qa_perld

If you are using latest Rails release with Rack 1.0.1, you need to downgrade rack to rack 1.0 or patch rack 1.0.1, please search related discussions on this forum.

Just like Tony suggested, build Apache 2.2 or 2.0 with prefork should fix it.

Yes, the bandwidth stats graphs will be affected. We plan to implement something similar to mod_watch, but it has lower priority and could take for a while.

That's working in progress for 4.1 release.

LSLB is a generic HTTP load balancer, does not require backend to be LiteSpeed web server only, it works with any web server. There should not be any issue with vbulletin and drupal. LSLB add "X-Forwarded-For" request header, as long as backend server can correctly acknowledge that header...

yes, enable it in LSWS web console and restart.

It wont fix the problem. You should turn on debug logging and rewrite log, and analyze why from the log.

That's a bug fixed in latest 4.0.12 build. Please download manually and run install.sh to upgrade.

Seems your DB server has very high I/O wait, that could the cause of the slow down. You should check DB server with mysqladmin processlist when I/O wait is high, maybe it is caused by a bad SQL, or missing index of a large table.

Interworx works with LiteSpeed, just interworx uses a special apache module called mod_watch which is not supported by LiteSpeed, so some statistical feature may not work properly.

It is a good idea, we will try that route.

Most browser wont send ":80" in the URL, just strip it. it might be the reason why. Not something wrong with the rewrite rule, just browser do not want to do what you want and causes looping redirect between web server and browser.

Please check error log for the reason of 403 error. Should be a permission/ownership issue.

That's the way to do it. Currently, a bug broke the upgrade link in our web console, fixed in the latest 4.0.12 build, with that working, you still need to login to web console of each server then click it. Maybe a little easier for some people.

Or, you can turn on PHP output_buffer in php.ini .

I think the Rails team need to address the compatibility with Ruby 1.9 first. If you know a Rails version works properly with Ruby 1.9, we can start to test and make ruby-lsapi work properly if it is not.

You need to ask your host to manually add a FastCGI application for each of your FCGI application in LiteSpeed web console, then add a script handler for you. like your hello app is called "hello_fcgi", the script handler suffix is "hello_fcgi". Then you use directive. <Files hello.fcgi>...