Unicorn workers are being reaped after rebooting the server

I recently updated my rails droplet (it is a one-click Ubuntu 14.0.4 droplet set up a while back) to use chruby for ruby management, and updated ruby.

I source chruby in /etc/profile.d/ and I removed RVM. Everything appeared to be working as intended.

However I noticed that after rebooting unicorn wasn’t restarting. I fixed the /etc/default/unicorn to remove the rvm paths, and I created a unicorn_wrapper to source chruby, switch to the rails app dir, then bundle exec unicorn.

Starting and stopping unicorn via /etc/init.d/unicorn and service unicorn both succeed and the workers run. However after a reboot the workers are immediately “reaped”.

Any pointers would be much appreciated.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi @ryanbooker , My understanding is that unicorn run properly but not running after reboot? if this is correct you can use update-rc.d to make unicorn run on boot

update-rc.d unicorn defaults

Thank you.