Module: check_mk
Branch: master
Commit: 63beea91233ec154dfe6b9162d8624e5d49c66bf
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=63beea91233ec1…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Sat Jan 22 14:23:13 2011 +0100
Updated bug entries
---
.bugs/98 | 16 ++++++++++++++++
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/.bugs/98 b/.bugs/98
new file mode 100644
index 0000000..71ab2a2
--- /dev/null
+++ b/.bugs/98
@@ -0,0 +1,16 @@
+Title: Restart of Nagios makes Multisite murk
+Component: multisite
+Benefit: 2
+State: open
+Cost: 2
+Date: 2011-01-22 14:20:58
+Class: bug
+
+When Nagios is restarted (e.g. via WATO), then for a short time the
+Livestatus socket is gone. This leads to error messages in various
+places - e.g. snapins and also AJAX functions which produce jQuery
+errors.
+
+We need to find a solution for a cleaner handling of this. Couldn't
+be a site in the state "restarting". If yes - how can we detect such
+a state. The livestatus socket is missing in such a case.