Search results

I think I know why it does not work with your plesk installation. standard edition has 5 hosts limit from apache configuration. Plesk create too many default vhosts, so the limit has been reached before a real vhost was configured. that's why you only see the default page. Enterprise edition...

I recommend you to try a fresh installation with 3.2.2 release by strictly following the tutorial. It should work.

Maybe try lynx from that server. When you see that message, means that the rails app works. You can move on.

Are you running in "production" mode or "development"? the properties page is not available for "production" for security reason.

You should try our easy configuration first, without the rewrite.

You should use the phpsuexec template, everything should be configured though Apache's httpd.conf. You should try LSWS on another port with "port offset" = 2000. And you can try our 3.2.2 build: http://www.litespeedtech.com/packages/3.0/lsws-3.2.2-std-i386-linux.tar.gz

I think it might be PHP memory limit issue, try increasing the "Process Soft/Hard limit" for the php external application, and there are a memory limit in php.ini, you should increase that as well.

Yeah, those are related. Max Connections around 2K is more than enough for your current usage. If every page contains new images, you may turn off smart keep-alive. But it is not that critical.

It should be /usr/local/lib/ruby/gems/1.8/gems/ruby-lsapi-2.7, something wrong with your gem installation.

Has the gem being properly installed. maybe it take for a while to have all rubyforge mirrors got synced. Can you compare the source files in the gem package and the tar.gz package from our site?

Yes, that will do it.

Uploaded the gem package again, should work now.

It is a global configuration, can only be adjusted from LSWS web console.

And you can read our documentation regarding installation as well.

Once you get your hand on the installer, you will know what you should do. very easy and painless. :)

No, just run the installer again to install the license key. All configurations are kept.

The request looks all right, mongrel does not like it, and close connection upon receiving it. 0x0030: 73ac aab4 4745 5420 2f61 6363 6f75 6e74 s...GET./account 0x0040: 2f6c 6f63 6174 696f 6e73 2f36 2f65 6469 /locations/6/edi 0x0050: 743f 0048 5454 502f 312e 310d 0a48 6f73...

Can try capturing the data going back and forth between LSWS and mongrel with tcpdump? something like "tcpdump -i lo -s 0 -X" Looks like mongrel does not like the request forwarded by LSWS, you can verify the request it with tcpdump output.

No, it is not.

Linux I/O scheduler is not priority aware, they have their own algorithm. One I/O intensive task will definitely affect other jobs doing disk I/O.