It would be good if it were redesigned to listen for the mongrel to finish before starting it again, every time I stop our front end mongrels one or two of them don't stop quick enough (there are a lot of 1/2-1 sec pages) and i'm pressing up/enter/up/enter/up/enter to start them up again as fast as possible. (anyway, what i meant to add was its not a Capistrano issue alone)
On 10/27/07, Andrew Vit <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm calling restart from my Capistrano task. I have this in my deploy.rbfile: > > # until mongrel_cluster updates to cap2... > namespace :deploy do > task :start, :roles => :app do start_mongrel_cluster end > task :stop, :roles => :app do stop_mongrel_cluster end > task :restart, :roles => :app do restart_mongrel_cluster end > end > > (What's the scoop on mongrel_cluster with Capistrano 2 by the way?) > > The command that's executed with a restart is: > > sudo mongrel_rails cluster::restart -C /etc/mongrel_cluster/staging.yml > > ** [out :: 208.75.84.228] stopping port 8010 > ** [out :: 208.75.84.228] already started port 8010 > > > At this point the server is not running -- I conclude that it has been > stopped successfully. Now if I call on "start" it starts properly > without an "already started" warning. > > This happens intermittently. Sometimes it restarts fine. If I call > stop/start manually, it works because I guess I'm leaving enough time > in between for it to shut down. > > Any thoughts on this? > > capistrano 2.0.0 > mongrel 1.0.1 > mongrel_rails 1.0.2 > > --Andrew Vit > > > _______________________________________________ > Mongrel-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/mongrel-users >
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
