GitHub User: andreteves
Very nice episode! But why does rubber upload code to all instance? I would expect it to upload the files only for the instance with the app role.
Thanks a lot Ryan! This episode is just amazing! I was looking for a tutorial like this for months!
I think I followed every step of this screencast, but I could not start unicorn. It seems that the pid files are busy (?). Any idea on how to solve this problem?
I'm using unicorn 4.2.0, which is the newest version of the gem.
When I run " sudo service unicorn restart" I get:
kill: 71: No such process
Couldn't reload, starting '/vagrant/bin/unicorn -D -c /vagrant/config/unicorn.rb -E development' instead
master failed to start, check stderr log for details
And here is my sderr log:
I, [2012-02-02T16:29:54.313595 #2007] INFO -- : unlinking existing socket=/tmp/unicorn.todo.sock
I, [2012-02-02T16:29:54.316860 #2007] INFO -- : listening on addr=/tmp/unicorn.todo.sock fd=3
/home/vagrant/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/unicorn-4.2.0/lib/unicorn/http_server.rb:202:in `rename': Text file busy - (/vagrant/tmp/pids/0.933261511233375.2007, /vagrant/tmp/pids/unicorn.pid) (Errno::ETXTBSY)
from /home/vagrant/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/unicorn-4.2.0/lib/unicorn/http_server.rb:202:in `pid='
from /home/vagrant/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/unicorn-4.2.0/lib/unicorn/http_server.rb:133:in `start'
from /home/vagrant/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/unicorn-4.2.0/bin/unicorn:121:in `<top (required)>'
from /vagrant/bin/unicorn:16:in `load'
from /vagrant/bin/unicorn:16:in `<main>'