This repository has been archived by the owner on Dec 31, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 93
monit restart not really restarting services on deploy #29
Comments
Resolved in #33 |
ajgon
added a commit
that referenced
this issue
Sep 14, 2016
Before this change, `monit restart` was invoked before `monit reload` which cased problems on initial setup of an instance. The `monit restart` command was expecting already defined service, which was in fact, configured, but not loaded by monit, since `monit reload` never occured. This change ensures, that every time a `*.monitrc` file changes, `monit reload` is inoked. Fixes #29 properly
ajgon
added a commit
that referenced
this issue
Sep 14, 2016
Before this change, `monit restart` was invoked before `monit reload` which cased problems on initial setup of an instance. The `monit restart` command was expecting already defined service, which was in fact, configured, but not loaded by monit, since `monit reload` never occured. This change ensures, that every time a `*.monitrc` file changes, `monit reload` is inoked. Fixes #29 properly
ajgon
added a commit
that referenced
this issue
Sep 14, 2016
Before this change, `monit restart` was invoked before `monit reload` which cased problems on initial setup of an instance. The `monit restart` command was expecting already defined service, which was in fact, configured, but not loaded by monit, since `monit reload` never occured. This change ensures, that every time a `*.monitrc` file changes, `monit reload` is inoked. Fixes #29 properly
dotnofoolin
pushed a commit
to dotnofoolin/opsworks_ruby
that referenced
this issue
Nov 23, 2021
Before this change, `monit restart` was invoked before `monit reload` which cased problems on initial setup of an instance. The `monit restart` command was expecting already defined service, which was in fact, configured, but not loaded by monit, since `monit reload` never occured. This change ensures, that every time a `*.monitrc` file changes, `monit reload` is inoked. Fixes ajgon#29 properly
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, sidekiq on deploy is doing a monit reload before doing a monit restart
https://github.com/ajgon/opsworks_ruby/blob/master/libraries/drivers_worker_sidekiq.rb#L14
This does not restart the sidekiq service. Here is a log.
When checking the process timestamps, i realize sidekiq didnt restart.
I suspect it might be because the http service for monit is shut down when the restart service command is issued. From the documentation, command line features are disabled when the http service is disabled https://mmonit.com/monit/documentation/monit.html#MONIT-HTTPD.
I feel like reloading monit is only necessary when monit itself has some configuration changes.
suggestions, advice, thoughts?
The text was updated successfully, but these errors were encountered: