Hi folks.

Using mongrel_rails and the mongrel_cluster capistrano recipes, I
often encounter a situation where some of the mongrel processes don't
die in time to be restarted. The output of capistrano will tell me
something like "mongrel on port 8001 is already up", but that's only
because capistrano/mongrel_rails failed to take it down in the first
place.

The solution is to do a full deploy:stop a couple times to make sure
they are all down, and then do a deploy:start.

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.

Thanks for any insight,
John


-- 
John Joseph Bachir
http://blog.johnjosephbachir.org
http://lyceum.ibiblio.org
http://dissent.cc
http://jjb.cc
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users

Reply via email to