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
[dev.icinga.com #11076] Reload on stoppped instance always successful #3894
Comments
Updated by mfriedrich on 2016-02-03 10:04:08 +00:00
Please look into that, this affects the Debian/Ubuntu specific initscript. |
Updated by formorer@formorer.de on 2016-02-03 10:09:26 +00:00 On Wed, 03 Feb 2016, development@icinga.org wrote:
|
Updated by bazz on 2016-02-03 10:41:28 +00:00 formorer@formorer.de wrote:
I agree with you, but for me, if icinga is down, right behaviour - try to up it.
|
Updated by formorer@formorer.de on 2016-02-03 10:46:28 +00:00 On Wed, 03 Feb 2016, development@icinga.org wrote:
I committed this in the meanwhile: diff --git a/debian/icinga2-common.icinga2.init b/debian/icinga2-common.icinga2.init **+ b/debian/icinga2-common.icinga2.init
Alex |
Updated by formorer on 2016-02-03 10:47:46 +00:00
Fix committed in git. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11076
Created by bazz on 2016-02-03 10:02:30 +00:00
Assignee: formorer
Status: Resolved (closed on 2016-02-03 10:47:46 +00:00)
Target Version: (none)
Last Update: 2016-02-03 10:47:46 +00:00 (in Redmine)
Steps to reproduce:
What expected - service reload should generate an error or start service.
What actual - nothing - we just say "OK", that service is down.
Icinga2 version - r2.4.1-1
OS Ubuntu 14.04.3 LTS
Quick and dirty fix:
The text was updated successfully, but these errors were encountered: