Module: check_mk
Branch: master
Commit: c900c4aab9e7b20a9a9f39b0f620b092bfaf5f5b
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c900c4aab9e7b2…
Author: Marcel Arentz <ma(a)mathias-kettner.de>
Date: Wed Jul 5 15:23:45 2017 +0200
obsolete bugreport
Change-Id: Iaaa6f73404c611ac731326957ab643128e021afc
---
.bugs/2512 | 22 ----------------------
1 file changed, 22 deletions(-)
diff --git a/.bugs/2512 b/.bugs/2512
deleted file mode 100644
index 4e563af..0000000
--- a/.bugs/2512
+++ /dev/null
@@ -1,22 +0,0 @@
-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.