Module: check_mk
Branch: master
Commit: 6b5946ed5070f2865ec0cbc6e7fd6657b92e69ca
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=6b5946ed5070f2…
Author: Marcel Arentz <ma(a)mathias-kettner.de>
Date: Tue Jul 4 15:52:49 2017 +0200
new odd bug
Change-Id: I9fcff1446b1822f99e3bcf171ac7415f5f135749
---
.bugs/2512 | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/.bugs/2512 b/.bugs/2512
new file mode 100644
index 0000000..4e563af
--- /dev/null
+++ b/.bugs/2512
@@ -0,0 +1,22 @@
+Title: failed service discovery in rare situations
+Component: checks
+State: open
+Date: 2017-07-04 15:21:44
+Targetversion: 1.5.0
+Class: bug
+
+Situation:
+In rare situation the service discovery will fail and discover no new snmp checks. Even
if these are correctly implemented and the services are discovered on a different check_mk
site.
+This behaviour is rare and possibly hard to reproduce. Several different forms has been
discovered:
+1. Services are not discovered on commandline (cmk -IIv hostname) but in WATO Service
Discovery.
+2. Services are not discovered on cmd and not in WATO Service Discovery. The Discovery
Check of the hosts see the missing services.
+3. Nothing is discovered except forcing the check plugin with --checks=pluginname
+
+In some cases a workaround can be to discover the services in WATO. After that the
discovery on cmd is working again. This is not working all the time.
+
+To reproduce the first occurance of this bug:
+
+cmk --flush hostname
+cmk -IIv
+
+There is no known way to reproduce the third occurance nor to get it working again.