Module: check_mk
Branch: master
Commit: c27ca73393c9b3b397e73c44e92fd34a78e778bc
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=c27ca73393c9b3…
Author: Bernd Stroessenreuther <bs(a)mathias-kettner.de>
Date: Thu Aug 8 12:47:50 2013 +0200
Updated bug entries #0962, #0963, #0964
---
.bugs/962 | 43 ++++++++++++++++++++++++++++++++++
.bugs/963 | 17 ++++++++++++++
.bugs/964 | 76 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 136 insertions(+)
diff --git a/.bugs/962 b/.bugs/962
new file mode 100644
index 0000000..b597c43
--- /dev/null
+++ b/.bugs/962
@@ -0,0 +1,43 @@
+Title: Restore per GUI not successful
+Component: multisite
+State: open
+Date: 2013-08-08 12:01:30
+Targetversion: 1.2.3
+Class: bug
+
+kam per feedback@ rein, Orginal-Mail im folder feedback/gitbug eroeffnet noch vorhanden
+
+FROM: <t.baer(a)dokom21.de>
+TO: <feedback(a)check-mk.org>
+SUBJECT: [Bug]: Restore ohne Funktion - System nach Restore ohne Funktion
+DATE: Thu, 25 Jul 2013 16:00:05 +0200
+
+Hallo,
+
+ein Restore eines Snapshots für über die Gui zu einem "internal error" und das
System ist nicht mehr nutzbar. Über die Kommandozeile wird zwar kein Fehler ausgegeben,
hat aber den gleichen Effekt.
+Nach dem Restore ist das Verzeichnis ~/etc/check_mk/conf.d/wato nicht mehr vorhanden.
Nach manuellem auspacken des Tarballs (wato-snapshot-xxxx-xx-xx-xx-xx-xx.tar.gz) und
manuellem erstellen des "wato" Verzeichnisses und manuellen kopieren der *.mk
Dateien, ist das System wieder funktionstüchtig.
+
+
+OMD[dokom21]:~$ uname -a
+Linux dkmcheckmk 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64
x86_64 GNU/Linux
+
+OMD[dokom21]:~$ cat /etc/redhat-release
+CentOS release 5.5 (Final)
+
+OMD[dokom21]:~$ check_mk -V
+This is check_mk version 1.2.2p2
+
+
+
+
+Mit freundlichen Grüßen
+Torsten Bär
+
+DOKOM Gesellschaft für Telekommunikation mbH
+Systemadministration und Sicherheit
+
+Stockholmer Allee 24
+44269 Dortmund
+Fon: +49 231.930-10 71
+Fax: +49 231.930-10 64
+E-Mail: t.baer(a)dokom21.de
diff --git a/.bugs/963 b/.bugs/963
new file mode 100644
index 0000000..9d7315f
--- /dev/null
+++ b/.bugs/963
@@ -0,0 +1,17 @@
+Title: Package for CentOS 6.4 (64bit): missing dependency
+Component: core
+State: open
+Date: 2013-08-08 12:35:54
+Targetversion: 1.2.3
+Class: todo
+
+came in to mk@ / original mail is still available in feedback/gitbug folder
+
+FYI (the least I could do helping your team continue to do a great job with distro
integration):
+
+On CentOS 6.4 (64bit), Perl module=Time::HiRes was missing after updating to OMD 1.2.3.i1
from 1.01.20130705.
+
+
+On Fri, Jul 12, 2013 at 9:30 PM, Brian Hargrave <brian(a)flipbit.com> wrote:
+
+ Thanks for the tip. We installed the OMD 1.2.3i1 RPM and then updated our
"site" and now monitoring our ESXi hosts! Unfortunately, all of the PNP graphs
stopped updating. Thoughts?
diff --git a/.bugs/964 b/.bugs/964
new file mode 100644
index 0000000..2746ffc
--- /dev/null
+++ b/.bugs/964
@@ -0,0 +1,76 @@
+Title: make vsphere monitoring work with ESX 4.0
+Component: checks
+State: open
+Date: 2013-08-08 12:41:52
+Targetversion: 1.2.3
+Class: feature
+
+came in via feedback@ / original mail is still available in folder feedback/gitbug
+
+
+From: Maarten Vanraes <maarten(a)ba.be>
+To: feedback(a)mathias-kettner.de
+Subject: ESX4.0 vspere patch
+Date: Tue, 09 Jul 2013 13:30:26 +0200
+
+vsphere agent works on ESX4.0 with this patch:
http://pastebin.com/E6mw9t3s
+--
+BA NV
+IT & Security
+
+
+From: Maarten Vanraes <maarten(a)ba.be>
+To: Check_MK Feedback <feedback(a)mathias-kettner.de>
+Subject: updated ESX4.0 vsphere patch
+Date: Tue, 09 Jul 2013 13:50:23 +0200
+
+needs some patching for the memory check too
+-- BA NV IT & Security
+
+
+0009-vsphere-check-works-for-ESX-4.0.patch
+
+--- a/share/check_mk/agents/special/agent_vsphere 2013-07-09 10:07:33.000000000 +0200
++++ b/share/check_mk/agents/special/agent_vsphere 2013-07-09 11:31:36.000000000 +0200
+@@ -672,7 +672,6 @@
+ vm_propertys = {
+ "name": str,
+ "guestHeartbeatStatus": str,
+- "summary.quickStats.uptimeSeconds": str,
+
+ # CPU Statistics
+ "summary.quickStats.overallCpuUsage": str,
+@@ -690,7 +689,6 @@
+ "summary.quickStats.swappedMemory": str,
+ "summary.quickStats.balloonedMemory": str,
+ "summary.quickStats.consumedOverheadMemory": str,
+- "summary.quickStats.compressedMemory": str,
+
+ # Virtual machine configuration
+ "config.hardware.memoryMB": str,
+@@ -705,6 +703,10 @@
+ "guest.toolsVersionStatus" : str,
+ }
+
++if esx_version_num > 4.0:
++ vm_propertys["summary.quickStats.uptimeSeconds"] = str
++ vm_propertys["summary.quickStats.compressedMemory"] = str
++
+ if esx_version_num > 4.1:
+ vm_propertys["config.hardware.numCoresPerSocket"] = str
+
+--- a/share/check_mk/checks/esx_vsphere_vm 2013-07-09 13:37:56.000000000 +0200
++++ b/share/check_mk/checks/esx_vsphere_vm 2013-07-09 13:44:12.000000000 +0200
+@@ -53,9 +53,9 @@
+ #active guest memory
+ guest_memory_usage =
savefloat(data["summary.quickStats.guestMemoryUsage"][0]) * 1024 * 1024
+ #size of the balloon driver in the VM
+- ballooned_memory =
savefloat(data["summary.quickStats.balloonedMemory"][0]) * 1024 * 1024
++ ballooned_memory =
savefloat(data.get("summary.quickStats.balloonedMemory",[0])[0]) * 1024 * 1024
+ #The portion of memory, in MB, that is granted to this VM from non-shared host
memor(musst not be set)
+- shared_memory =
savefloat(data["summary.quickStats.sharedMemory"][0]) * 1024 * 1024
++ shared_memory =
savefloat(data.get("summary.quickStats.sharedMemory",[0])[0]) * 1024 * 1024
+ #The portion of memory, in MB, that is granted to this VM from host memory that is
shared between VMs.
+ private_memory =
savefloat(data.get("summary.quickStats.privateMemory",[0])[0]) * 1024 * 1024
+
+