Getting Lots of Ruby Processes

[jp_n9]

I reset the "Max Connections" under the "Rails" tab to 3. I restarted, and a few hours later I now have 12 ruby processes. This is kind of crazy.

Under the "Security" tab there is a setting "Max CGI Instances" which is left at the original 20. Could that or anything else be causing this issue?

Any other ideas?

[mistwang]

"Max CGI instances" does not matter.
If possible, please PM me temp root access and admin for LSWS web interface to your server, I'd like to take a look.

[amalik]

Can you post to this thread what the problems was when it is resolved?

thanks,

Amr

[mistwang]

OK, caught the bug on jp_n9's server, it only happens when ruby processes are started in suEXEC mode, user id is different from that of web server, and "max_idle_time" under "Rails" tab has been set.

When there is no request to ruby process for "max_idle_time", LSWS will try to kill this process group, but failed due to permission problem, but LSWS think the process group has been killed, when next request comes in, LSWS will start another group of ruby process, and so on.

I have updated ruby-lsapi-1.8 package to address this issue, please update your installation then and add an environment variable "LSAPI_PGRP_MAX_IDLE=xxx" under "Rails" tab to tell the ruby process to quit, the value should match "max idle time" value under rails tab.

We will fix this problem on LSWS side as well in 2.2.2, by finding a workaround for the permission problem of killing suEXEC processes, as well as setting "LSAPI_PGRP_MAX_IDLE" automatically.

[jp_n9]

Originally Posted by mistwang

OK, caught the bug on jp_n9's server, it only happens when ruby processes are started in suEXEC mode, user id is different from that of web server, and "max_idle_time" under "Rails" tab has been set.

Did you fix this bug on my server? Because I just checked and there are 14 processes right now.

If you didn't fix it, what do I need to do?

[mistwang]

No, I did not. You need to download ruby-lsapi-1.8 package and install it again and add an environment variable "LSAPI_PGRP_MAX_IDLE=xxx" under "Rails" tab to tell the ruby process to quit, the value should match "max idle time" value under rails tab.

[amalik]

mistwang, thanks for posting it back here. Hopefully we'll get the gem soon enough. I'm just going to keep killing the processes as it is in dev anyway.

thanks,

Amr

[jp_n9]

Well the server has been left unchecked all weekend, and today I only have one Ruby process running. Looks like it worked. Thanks!

[mistwang]

Thank you for the update, we will release LSWS 2.2.2 and ruby LSAPI 1.8 soon.