Module: check_mk
Branch: master
Commit: 5fac9c7ad6bddae12cedd1f513b05f741baed5d8
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=5fac9c7ad6bdda…
Author: Mathias Kettner <mk(a)mathias-kettner.de>
Date: Tue Oct 9 15:00:30 2012 +0200
Updated bug entries #0065, #0802, #0771, #0060, #0790
---
.bugs/60 | 7 ++++++-
.bugs/65 | 6 ++++++
.bugs/771 | 10 ++++------
.bugs/790 | 22 ++++++++++++++++++++++
.bugs/802 | 11 +++++------
5 files changed, 43 insertions(+), 13 deletions(-)
diff --git a/.bugs/60 b/.bugs/60
index 6633c82..2a3c554 100644
--- a/.bugs/60
+++ b/.bugs/60
@@ -1,4 +1,4 @@
-Title: Warnung im Logfile, wenn environment_macros an sind
+Title: Livestatus-Warnung im Logfile, wenn environment_macros an sind
Component: livestatus
State: open
Date: 2010-12-21 22:18:56
@@ -6,3 +6,8 @@ Class: feature
Analog zu den broker options wäre das eine für die Stabilität wichtige
Sache.
+
+Diese Variable kann man sicher irgendwie als globale Variable auslesen
+und dann ins Nagios-Log schreiben (da wo auch die broker-Options
+getestet werden).
+
diff --git a/.bugs/65 b/.bugs/65
index e08634d..0a8b0ed 100644
--- a/.bugs/65
+++ b/.bugs/65
@@ -7,3 +7,9 @@ Class: feature
Ählich zu den expandierten notes_url. Damit könnte man sehen, welches Kommando
wirklich ausgeführt wird. Und das zum rausschneiden und auf der Kommandozeile
pasten.
+
+Dazu einen passenden Multisite-Painter, damit man das Kommando ansehen
+kann. Diesen könnte man evtl. auch direkt in der Service-Details-View
+anzeigen anstelle des jetzigen?
+
+Das gleiche dann natürlich auchbei den Host.
diff --git a/.bugs/771 b/.bugs/771
index b342a7a..51c9dc1 100644
--- a/.bugs/771
+++ b/.bugs/771
@@ -5,9 +5,7 @@ Date: 2012-06-14 13:29:43
Targetversion: 1.2.0
Class: nastiness
-When adding service columns to host tables the column
-headers of those columns should be the service name,
-not the title of the painter. The latter one is
-for example "Perf-O-Meter". Better would be "CPU load".
-(if this is not specified by the user in the first
-place).
+When adding service columns to host tables the column headers of those
+columns should be the service name, not the title of the painter. The latter
+one is for example "Perf-O-Meter". Better would be "CPU load". (if this is
+not specified by the user in the first place).
diff --git a/.bugs/790 b/.bugs/790
new file mode 100644
index 0000000..5e8b21f
--- /dev/null
+++ b/.bugs/790
@@ -0,0 +1,22 @@
+Title: Three Livecheck issues
+Component: livecheck
+State: open
+Date: 2012-10-09 14:20:28
+Targetversion: 1.2.0
+Class: bug
+
+1. In livecheck.c:53, int bytes_read = read(fd[0], output, sizeof(output));
+does not guarantee a valid 0-byte terminated string. I propose a single
+codeline after it: if (bytes_read > 0) output[bytes_read - 1] = 0; This
+fixed an issue for me, where there was a lot of garbage behind output lines.
+
+2. In livecheck.c:190, check_type should always be 0. check_type determines
+wether it is active(0) or passive(1), not host/service. Since livecheck is
+always run actively on the host that it puts the checkfile. This doesn't
+have to be variable.
+
+3. Somewhere before livecheck.c:188 the output charbuffer needs to be newline
+escaped, there is a nagios function for this called escape_newlines. This
+is necessary for long plugin output to be functional.
+
+Ticket #442
diff --git a/.bugs/802 b/.bugs/802
index 4098a21..1674986 100644
--- a/.bugs/802
+++ b/.bugs/802
@@ -5,9 +5,8 @@ Date: 2012-09-20 18:17:19
Targetversion: future
Class: nastiness
-If you add a simulated state for a given service (using foldable)
-it will be reflected on the top-level, but not on the nodes.
-So you see a lot of green items and but the main state stays as
-configured to be simulated
-it's very irritating, since the correct subaggrs and services
-are in fact displayed, just not with their simulated states.
+If you add a simulated state for a given service (using foldable) it will be
+reflected on the top-level, but not on the nodes. So you see a lot of green
+items and but the main state stays as configured to be simulated it's very
+irritating, since the correct subaggrs and services are in fact displayed,
+just not with their simulated states.
Module: check_mk
Branch: master
Commit: c9035dd9af22af384ba96761568a9d1b918a0616
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c9035dd9af22af…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Tue Oct 9 10:33:57 2012 +0200
Add new bug entry
---
.bugs/805 | 19 +++++++++++++++++++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/.bugs/805 b/.bugs/805
new file mode 100644
index 0000000..a4b6505
--- /dev/null
+++ b/.bugs/805
@@ -0,0 +1,19 @@
+Title: Custom notification text does not show up
+Component: core
+State: open
+Date: 2012-10-09 10:30:07
+Targetversion: 1.2.0
+Class: todo
+
+If you create a custom notification using Multisite it allwos you to include some text in there
+This text is not passed through to the actual notification, either missing from the
+template or not handled in notify.py
+
+
+Address: 149.154.154.26
+State: UP -> UP (RECOVERY)
+Command: check-mk-ping!-n 9 -t 20 -w 1500.00,80.00% -c 3000.00,100.00%
+Output: OK - 149.154.154.26: rta 22.841ms, lost 0%
+Perfdata: rta=22.841ms;1500.000;3000.000;0; pl=0%;80;100;; rtmax=28.768ms;;;; rtmin=20.972ms;;;;
+
+We could generally enable those comments, right?
Module: check_mk
Branch: master
Commit: 899d7f84e5e1e910a61f00b5e3ad62da15004deb
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=899d7f84e5e1e9…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Mon Oct 8 17:28:14 2012 +0200
Checks cbl_airlaser: Handle cases where one of two main PSUs is missing
---
checks/cbl_airlaser | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/checks/cbl_airlaser b/checks/cbl_airlaser
index 8fef745..650bc58 100644
--- a/checks/cbl_airlaser
+++ b/checks/cbl_airlaser
@@ -145,6 +145,12 @@ def check_cbl_airlaser_hw(item, params, info):
# if this sensor wasn't in the params, then we don't alert on it.
perfdata.append(("%s" % sensor, "%d" % val, '', '', 0, 90)),
+ # HACK: for the main PSUs the status 3 is not "warning" but
+ # not_detected (3)
+ if sensor in [ "psStatus48V", "psStatus230V" ] \
+ and val == "warning":
+ state = max(state, 0)
+
else:
if val == "failure":
state = 2