Module: check_mk
Branch: master
Commit: c77ed4045cec58fab1ca955b344ea4350935e6bf
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c77ed4045cec58…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Tue Jan 22 09:56:37 2013 +0100
Updated bug entries #0898
---
.bugs/898 | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/.bugs/898 b/.bugs/898
new file mode 100644
index 0000000..434e964
--- /dev/null
+++ b/.bugs/898
@@ -0,0 +1,16 @@
+Title: Unresolvable host prevents loading configuration (bad behaviour)
+Component: core
+State: open
+Date: 2013-01-22 09:44:36
+Targetversion: 1.4.0
+Class: nastiness
+
+It seems strange, I am able to add a host to Check_MK by the host name and
+while the name can be resolved everything is OK. But once the name is not
+resolvable anymore (for whatever reason), the monitoring still works but
+if I want to rewrite the config and restart nagios, the process is blocked
+by that unresolvable host.
+
+This seems a bit nasty. It would be better to have a warning message or just
+no message while applying the config. The monitoring will show me the fact
+that the host is not resolvable.