Apache Takes 10mins to Reboot

Rails
1

I have 5 FastCgiServer processes running on my Rails app (specified in
httpd.conf) in Apache 2. When I restart Apache - I timed it - it takes
just over 10 minutes to reboot. What up with that?

The FastCgiServer processes also have the RAILS_ENV variable set to
production.

Of course, once it reboots the app is lightning fast and all is well.

Is this just something I have to deal with by using Apache/FastCGI?

2

Are you on Linux or Windows? What are the specs on your server?

Why 5 dispatchers? Got a big app?

Apache will start all 5 ruby processes at the same time. On Linux, use
TOP
after you start Apache
On Windows, use task manager.

This is why I don’t like FastCGI.

On 14 Jul 2006 20:45:24 -0000, Jeff W.
[email protected]

3

I’m using 5 processes because eventually this will be a big app as it is
a CMS that hosts many websites on one Rails application. Maybe I should
set it to 2 processes for now and scale in a little while. But, making
any changes in production is such a pain to do as I have to wait each
time.

This is a dedicated server, Intel Celeron 1.3 GHZ, 512mb RAM. Running
RHEL. I don’t know what TOP is so I’ll check that out.

Jeff

4

On 14 Jul 2006 20:45:24 -0000, Jeff W.
[email protected] wrote:

I have 5 FastCgiServer processes running on my Rails app (specified in
httpd.conf) in Apache 2. When I restart Apache - I timed it - it takes
just over 10 minutes to reboot. What up with that?

The FastCgiServer processes also have the RAILS_ENV variable set to
production.

Of course, once it reboots the app is lightning fast and all is well.

Is this just something I have to deal with by using Apache/FastCGI?

That sounds a lot like apache timing out trying to do dns lookups.
Do you see any “Can’t resolve xxxx” messages in your log files? In
any case the log files should give some clue. Something is definitely
wrong.