How to detect orphaned sidekiq process after capistrano deploy?

Question

We have a Rails 4.2 application that runs alongisde a sidekiq process for long tasks.

Somehow, in a deploy a few weeks ago something went south (the capistrano deploy process didn't effectively stopped it, wasn't able to figure out why) and there was left an orphaned sidekiq process running that was competing with the current one for jobs on the redis queue. Because this process source became outdated it started giving random results on our application (depending on which process captured the job) and we got a very hard time until we figured this out..

How I can stop this from happenning ever again? I mean, I can ssh into the VPS after every deploy and run ps aux | grep sidekiq ps aux | grep sidekiq to check if there is more than one.. but it's not practical.

Answer 1

Use your init system to manage Sidekiq, not Capistrano.

https://github.com/mperham/sidekiq/wiki/Deployment#running-your-own-process