K
K
Ka4a2015-11-16 17:11:23
linux
Ka4a, 2015-11-16 17:11:23

How to run sidekiq?

Good afternoon. Please advise with this problem. There are 2 servers. With a customized environment. I want to `GOD`add sidekiq, on one server I did it without problems, but on the second I don’t want to and I don’t understand why.
What we have:

god status
    god status
    sidekiq: unmonitored
    unicorn: up
    unicorn_rails: up

When I do I god start sidekiq
see sidekiq: up
But I do not see it in the processes. in the logs
INFO: sidekiq moved 'up' to 'up'
    INFO: sidekiq [trigger] process is not running (ProcessRunning)
    INFO: sidekiq move 'up' to 'start'
    INFO: sidekiq before_start: no pid file to delete (CleanPidFile)
    INFO: sidekiq start: cd /var/www/myproject/current && rvm use ruby-2.2.2 do bundle exec sidekiq --index 0 --pidfile /var/www/myproject/shared/tmp/pids/sidekiq.pid --environment production --logfile /var/www/myproject/shared/log/sidekiq.log --daemon
    WARN: sidekiq start command exited with non-zero code = 127

I repeat that on another server I launched it in 1 minute.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
K
Ka4a, 2016-12-16
@ka4a

sobsno it was necessary to execute from the project cap stagename sidekiq:restart

O
Oleg Tsilyurik, 2015-11-16
@Olej

It seems to me that you have a problem with /var/www/myproject/shared/tmp/pids/sidekiq.pid (I don't want to go into details).
This happens when, at the start of daemons, their pid-files are not deleted after the previous start (after an abnormal termination).
Try deleting this file, or see what it has with the permissions flags... Or, on the contrary, you don't have the path where it wants to write the pid file.

V
vsuhachev, 2015-11-17
@vsuhachev

sidekiq starts and exits with code 127, see what it is missing in its logs (/var/www/myproject/shared/log/sidekiq.log)

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question