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.

Sign up for GitHub

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

Jump to bottom

In case of icinga2 reload businessprocesses end with critical #7068

Closed
emanuel-b-q opened this issue Nov 22, 2018 · 2 comments
Closed

In case of icinga2 reload businessprocesses end with critical #7068

emanuel-b-q opened this issue Nov 22, 2018 · 2 comments
Labels
area/checks Check execution and results

Comments

@emanuel-b-q
Copy link

Reload of icinga2 kills all child processes and the end with return value CRITICAL

Expected Behavior

Icinga2 shouldn't kill the processes, or in should delay them until the reload/restart is finish and then start the checks

Current Behavior

Whenever there is a reload/restart of icinga2, all business processes end with a cirtical error.
The businessprocesses are child processes of the icinga2 process, so in case there is - e.g. a deployment done by director, this results worst case in a broken SLA - which is wrong!

Possible Solution

Not sure how to solve this ....

Your Environment

  • Module version (System - About): 2.1.0
  • Icinga Web 2 version and modules (System - About): 2.5.3
  • Icinga 2 version (icinga2 --version): 2.8.4
  • Operating System and version: RHEL 7.5
  • Webserver, PHP versions: Apache 2.4.6 , PHP 7.1.8
@dnsmichi dnsmichi transferred this issue from Icinga/icingaweb2-module-businessprocess Apr 1, 2019
@dnsmichi
Copy link
Contributor

dnsmichi commented Apr 1, 2019

Please do the following

  • Verify which checks are running for such a long time, being killed then
  • Either test the snapshot packages or wait for 2.11 which provides improvements in this region

@dnsmichi dnsmichi added needs feedback We'll only proceed once we hear from you again area/checks Check execution and results labels Apr 1, 2019
@dnsmichi
Copy link
Contributor

Somehow a duplicate of #6873.

@dnsmichi dnsmichi removed the needs feedback We'll only proceed once we hear from you again label Jul 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/checks Check execution and results
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dnsmichi @emanuel-b-q