Forum: Ruby on Rails dispatch.fcgi processes not killed properly

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
85f8b7bbe07bff22e0b38cca818cf692?d=identicon&s=25 Luke Pearce (kule)
on 2007-02-05 17:08
Hi Guys

I've had this error come up a couple of times now - If it was just a one
off every now and again I'd understand it and look at caching.

It seems the site is up and running no probs for about 30 days each time
then my max processes are used up and the site goes down until my host
(Site5) can clear the processes down.

I got a list of processes from support which interestingly enough seem
to be all around midnight or thereabouts which seems to me this is
probably when they are doing a scheduled kill of the dispatch process.

... S Nov13 0:02 /usr/bin/ruby dispatch.fcgi
... S Nov14 0:21 /usr/bin/ruby dispatch.fcgi
... S Nov16 0:21 /usr/bin/ruby dispatch.fcgi

From the rails point of view the logs have no errors until the site goes
down then I get the mySQL max_user_connections error until I get the
processes cleared by support.

Has anyone else had the same problems? Is this just a configuration
problem from my end? Or is there some way I can clear any dispatch.fcgi
processes that haven't properly died?

Thanks in advance!

20139de0a00fc8675e86d52f12f988ad?d=identicon&s=25 Jamez (Guest)
on 2007-02-06 11:11
(Received via mailing list)
Try posting your question on You might get your answer

On Feb 5, 5:08 pm, Luke Pearce <>
This topic is locked and can not be replied to.