Support

mistwang · #11 09-12-2006, 08:07 AM

Quote:

Even still, it would seem that something was wrong if it keeps spawning new processes when at most two users are ever accessing it at once (most likely only one at a time).

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

mistwang · #12 09-12-2006, 09:23 PM

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/package...api-1.8.tar.gz .

jp_n9 · #13 09-13-2006, 05:54 AM

Quote:

Originally Posted by mistwang

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/package...api-1.8.tar.gz .

Ok. I downloaded and installed the patch.

In the Rails tab, the Environment setting includes the value:

LSAPI_MAX_REQS=1000

Does that need to be lowered too, or is that OK?

Also, is there any way to verify the version of LiteSpeed or LSAPI installed on a system - just to make sure everything installed correctly? Thanks!

Hopefully the 1.8 will do the trick, because the system had spawned crazy processes again last night.

mistwang · #14 09-13-2006, 10:11 AM

Quote:

In the Rails tab, the Environment setting includes the value:

LSAPI_MAX_REQS=1000

Does that need to be lowered too, or is that OK?

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. ;-)

jp_n9 · #15 09-13-2006, 11:11 AM

Quote:

Originally Posted by mistwang

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. ;-)

When will the ruby-lsapi gem be online for auto installation?

Also, any word on when the Capistrano wiki How-To will be available?

mistwang · #16 09-13-2006, 11:26 AM

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

amalik · #17 09-13-2006, 01:07 PM

Quote:

Originally Posted by mistwang

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/package...api-1.8.tar.gz .

1.7 barfed all over itself last night. I woke up this morning and it had been spawning until I think it ran out of memory. I have 18 rubly lsap and 3 lsphp (didn't have this prob before) sitting there. 1.21 maybe contributing to it?

I dunno.

I'll try the 1.8 lsapi and see how that goes. Thanks.

amalik · #18 09-13-2006, 01:14 PM

Regarding 1.8, do you recommend building a gem and then installing or just use setup.rb? I'm wondering if this will interfere with a gem-only strategy I've been following.

thanks,

mistwang · #19 09-13-2006, 02:10 PM

The problem should be mainly in
gem package will be available when we officially announce this release.
Yes, packages installed via gem and setup.rb may interfere with each other, remove the other one when switch the package. I think the gem one may has lower priority, not 100% sure.

Be careful not to over configure your rails application like setting "max connections" to 100 when you hardware cannot take 100 ruby processes.

jp_n9 · #20 09-14-2006, 10:08 AM

Ok. I downloaded and installed LSAPI 1.8 as instructed in the README:

ruby setup.rb config
ruby setup.rb setup
ruby setup.rb install

Is that it?

It would be nice to be able to run something like "lsws -v" and have LiteSpeed verify what versions are being used of both the server and LSAPI.top

I don't recall seeing anything in the instructions, but is there any need to modify any files within the individual Rails applications?