Jimmy Soho <[email protected]> wrote: > > Hi Jimmy, Are you deploying with Capistrano and you originally started > > Unicorn in a working_directory that no longer exists on the filesystem? > > > > Under Linux, you can check the working directory of any process > > with `ls -l /proc/$PID/cwd` > > Ah! Yes. I use Capistrano, and it pruned releases. But definitely > /after/ a new version was deployed. > > What I don't understand then though is that I have this in my unicorn > config file: > > working_directory "/srv/app1/current" > > How could the new master / workers still be pointing to the old > directory? Isn't what this working_directory directive is for?
In your Capistrano deploy tasks, do you create/update the current symlink before you send USR2? You should have the symlink updated before sending USR2.. Other folks here may have more experience with Capistrano+Unicorn, maybe they have portable recipes they can share. -- Eric Wong _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
