Skip to content
This repository has been archived by the owner on Dec 31, 2022. It is now read-only.

Monit doesn't stop sidekiq 6.0 #217

Closed
betesh opened this issue Apr 29, 2019 · 0 comments
Closed

Monit doesn't stop sidekiq 6.0 #217

betesh opened this issue Apr 29, 2019 · 0 comments

Comments

@betesh
Copy link
Contributor

betesh commented Apr 29, 2019

This is a follow-up to #215. After resolving the issue there, I ran into later issues with monit failing to stop sidekiq.

The next at

next unless File.file?(pid_file) && pid_exists?(File.open(pid_file).read)
is always executed because sidekiq 6 does not create a pid file.

Expected Behavior

Monit should stop sidekiq

Actual Behavior

Monit does not stop sidekiq

Custom JSON

{
    "ruby-ng": {
        "ruby_version": "2.6"
    },
    "deploy": {
        "my_app": {
            "database": { ...  },
            "worker": {
                "adapter": "sidekiq"
            }
        }
    }
}

Chef log including error

This is from /var/log/syslog:

monit[1054]: 'sidekiq_myappshortname-2' failed to stop (exit status 2) -- '/bin/su - deploy -c \ ps -ax | grep bundle exec sidekiq | grep sidekiq_2.yml | grep -v grep | awk {print $1} | xargs kill\ ': /bin/su: invalid option -- 'a'#012Usage: su [options] [LOGIN]#012#012Options:#012  -c, --command COMMAND         pass COMMAND to the invoked
monit[1054]: 'sidekiq_myappshortname-2' restart action done
@ajgon ajgon closed this as completed in 59198b9 May 7, 2019
aschuster3 pushed a commit to Experity/opsworks_ruby that referenced this issue Jun 6, 2019
yurivm pushed a commit to homeday-de/opsworks_ruby that referenced this issue Apr 16, 2020
dotnofoolin pushed a commit to dotnofoolin/opsworks_ruby that referenced this issue Nov 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant