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.

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

No notification for service in down state when host changes state #857

Closed
eliaz opened this issue May 24, 2013 · 4 comments
Closed

No notification for service in down state when host changes state #857

eliaz opened this issue May 24, 2013 · 4 comments

Comments

@eliaz
Copy link

eliaz commented May 24, 2013

I have tested the following

  1. I configure a service with check_dummy|0|... and restart shinken
  2. I force the service the host are attached to to down state I(Now I get a notification about host down after some recheck's)
  3. I force the service to down state by reconfiguring it to check_dummy|2... - and I restart shinken. I wait for some rechecks and dont get notification( as expected)
  4. I make the host go to UP state. Now I get notification about recovery of the host, but I never get notification about the service being down!

(It seems the service maybe never leaves state its in(soft). e.g 1/2(hard/state. After the host has recovered the service just gets stuck in the state, even if I do manual rechecks.)

@naparuba
Copy link
Contributor

not good indeed. I'll give a look for 1.6

@naparuba naparuba added the Bug label Mar 14, 2014
@Seb-Solon
Copy link
Contributor

Still the case? It may be related to retention I think, otherwise onthe step 3 and 4 a relevant to the issue.

@naparuba naparuba modified the milestones: 2.4 (Noteworthy Nagapie) **we will find :)**, 2.2 (Maleable Muskrat) **doc, cli & arbiters** Nov 12, 2014
@naparuba
Copy link
Contributor

I postpone until more news :)

@Seb-Solon
Copy link
Contributor

Case is not enough clear. Reopen if you can provide configuration sample in the current Shinken version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants