We run into this problem a lot as well. The problem can be exacerbated when a mongrel has a backlog of work, or has bloated to a point that it is heavily swapped. The mongrels always get the shutdown signal, but they don't act on it fast enough to clear their pid file by the time the start is actioned.
In our case those mongrels will eventually quit and monit will restart them, but its not ideal. If cluster::restart supported a --delay parameter that would go some way to fixing the problem. Cheers Dave On 22/01/2008, at 6:05 AM, John Joseph Bachir wrote: > Is my problem typical? Is there a solution? Seems like mongrel_rails > and/or the capistrano recipes should wait for the processes to stop > before attempting to restart them. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
