Graham Christensen <gra...@grahamc.com> wrote: > I'm deploying Unicorn on a Rails application with RUnit. Technically > I'm using Chef's deployment tools, if any of you are familiar with > it (https://github.com/opscode-cookbooks/application_ruby) but to be > clear they aren't doing anything magical, so this is purely an issue > with RUnit and Unicorn. > > The TL;DR of the following post, which has lots of pastes (linking > to pastebins for easier reading:) when I run /etc/init.d/myzippykid > restart, the old unicorn master fails to die, causing the new master > to be stuck in a loop waiting to own port 8080. The new master never > takes over, as the old master never dies. When I manually kill the > master, the new one takes over just fine. > > What am I missing in my restart process to make the old master exit?
It seems you're missing /etc/init.d/myzippykid in your pastes. Are you sending SIGQUIT (or SIGTERM) to the old unicorn master? If you have old workers servicing requests, the old master will wait until all the old workers are done. Since your timeout is 60s, everything (workers and master) should exit around that time period if you have stalled/long-running requests, though. _______________________________________________ Unicorn mailing list - mongrel-unicorn@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
