I am using Check_MK to generate checks to make Icinga (a Nagios fork) monitor a bunch of machines. After starting up Icinga, after some time, Check_MK starts to collect data from the configured machines. The order and the amount of time in between the machines which are checked by Check_MK feels very random and sometimes it takes several minutes until the checks start and even more time until all the machines have been checked once. Also it seems that commanding Icinga to recheck all hosts doesn't start the Check_MK checks.

How can I force Check_MK to process the checks for a specific or all of the configured machines in a way so that Icinga becomes aware of the results instantly after this happens?

The machines run Debian 7 "Wheezy" with Icinga version 1.7 and Check_MK 1.2.2.

  • Why are you restarting Icinga so often? And forcing host checks doesn't force service checks. They're different. – Keith Feb 4 '16 at 16:22
  • I restart every now and then after a kernel update, and then it takes ages before I get anything useful out of Icinga again. – aef Feb 4 '16 at 19:11
  • There is a meta-service, that is actually calling the check-mk execution, it's the service that is not marked as "passive" – lazyfrosch Feb 8 '16 at 6:36

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.