Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conflict between sidekiq and sidekiq-scheduler #24

Closed
mikeni opened this issue Oct 15, 2013 · 1 comment
Closed

conflict between sidekiq and sidekiq-scheduler #24

mikeni opened this issue Oct 15, 2013 · 1 comment

Comments

@mikeni
Copy link

mikeni commented Oct 15, 2013

regarding this issue
#8

is both sidekiq and sidekiq-scheduler supposed to be using tmp/pids/sidekiq.pid?

this is what is happening in my capistrano log when i deploy
is this supposed to be happening?

  • 2013-10-14 17:05:35 executing `sidekiq:stop'
    • executing "if [ -d /app/current ] && [ -f /app/current/tmp/pids/sidekiq.pid ] && kill -0 cat /app/current/tmp/pids/sidekiq.pid> /dev/null 2>&1; then cd /app/current && bundle exec sidekiqctl stop /app/current/tmp/pids/sidekiq.pid 10 ; else echo 'Sidekiq is not running'; fi"
      • 2013-10-14 17:05:36 executing `sidekiq:start'
    • executing "cd /app/current ; nohup bundle exec sidekiq -e production -C /app/current/config/sidekiq.yml -i 0 -P /app/current/tmp/pids/sidekiq.pid >> /app/current/log/sidekiq.log 2>&1 &"
    • 2013-10-14 17:05:37 executing `sidekiq_scheduler:restart'
      then sidekiq-scheduler stops sidekiq which was just started
    • 2013-10-14 17:05:37 executing `sidekiq_scheduler:stop'
    • executing "cd /app/current && if [ -f /app/current/tmp/pids/sidekiq.pid ]; then bundle exec sidekiqctl stop /app/current/tmp/pids/sidekiq.pid 10 ; fi"
    • 2013-10-14 17:05:38 executing `sidekiq_scheduler:start'
    • executing "cd /app/current ; nohup bundle exec sidekiq-scheduler -e production -C /app/current/config/sidekiq.yml -P /app/current/tmp/pids/sidekiq.pid >> /app/current/log/sidekiq.log 2>&1 &"
@mikeni
Copy link
Author

mikeni commented Oct 15, 2013

is it true that if you are doing this
require 'sidekiq-scheduler/capistrano'
you should NOT do this
require 'sidekiq/capistrano' ?

i think this is my problem, im trigger 2 processes instead of 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants