Module: check_mk
Branch: master
Commit: 49aef0607610cedc69423e847546f7b205554845
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=49aef0607610ce…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Wed May 17 10:18:41 2017 +0200
4720 FIX The settings of the MK Notify daemon could be lost when saving other global settings
When a problem occurs during plugin loading of WATO plugins, which should only occur when
working with local modifications, it could happen that the global settings of the MK notification
daemon were lost when editing any global configuration variable.
Change-Id: Ib2fdb2bcba5749e7246243f2008f03c048258d12
---
.werks/4720 | 13 +++++++++++++
web/htdocs/watolib.py | 12 ++++++++++--
2 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/.werks/4720 b/.werks/4720
new file mode 100644
index 0000000..b6b2053
--- /dev/null
+++ b/.werks/4720
@@ -0,0 +1,13 @@
+Title: The settings of the MK Notify daemon could be lost when saving other global settings
+Level: 1
+Component: wato
+Class: fix
+Compatible: compat
+Edition: cee
+State: unknown
+Version: 1.5.0i1
+Date: 1495008952
+
+When a problem occurs during plugin loading of WATO plugins, which should only occur when
+working with local modifications, it could happen that the global settings of the MK notification
+daemon were lost when editing any global configuration variable.
diff --git a/web/htdocs/watolib.py b/web/htdocs/watolib.py
index 661a5a2..fac4fc9 100644
--- a/web/htdocs/watolib.py
+++ b/web/htdocs/watolib.py
@@ -260,7 +260,15 @@ class ConfigDomain(object):
@classmethod
def all_classes(cls):
- return cls.__subclasses__() # pylint: disable=no-member
+ subclasses = cls.__subclasses__() # pylint: disable=no-member
+
+ # Classes may be registered twice, only store one of the occurances.
+ # TODO(lm): Find the reason for this and solve this issue in the plugin mechanism.
+ classes = {}
+ for subclass in subclasses:
+ classes.setdefault(subclass.__name__, subclass)
+
+ return classes.values()
@classmethod
@@ -270,7 +278,7 @@ class ConfigDomain(object):
@classmethod
def get_class(cls, ident):
- for domain_class in cls.__subclasses__(): # pylint: disable=no-member
+ for domain_class in cls.all_classes():
if domain_class.ident == ident:
return domain_class
raise NotImplementedError(_("The domain \"%s\" does not exist") % ident)
Module: check_mk
Branch: master
Commit: 8fa77febaeacc4142264e2fa5a80ec575c817c85
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=8fa77febaeacc4…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Tue May 16 13:57:44 2017 +0200
4718 FIX Fixed memory leak in Check_MK check helpers when started in verbose mode
When the Check_MK helpers are configured with a higher log level than the default
Notice log level the Check_MK helpers were leaking memory. This can be configured
by changing the option "Check_MK check helpers" of the global setting "Logging of the core"
to e.g. Informational.
In this mode the helper gathers information about some changed variables during runtime
and the memory usage. It also allows to debug different mechanics of the helpers.
If you enabled this, each reload of the core (not restart) was triggering the memory
leak in the helpers. In extreme situations this could lead to duplication of the memory
usage on each reload.
Change-Id: I561abfdffd2f10d88a277d2c3267915a68e8ab7c
---
.werks/4718 | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/.werks/4718 b/.werks/4718
new file mode 100644
index 0000000..4025c3a
--- /dev/null
+++ b/.werks/4718
@@ -0,0 +1,20 @@
+Title: Fixed memory leak in Check_MK check helpers when started in verbose mode
+Level: 2
+Component: core
+Compatible: compat
+Edition: cee
+Version: 1.5.0i1
+Date: 1494935598
+Class: fix
+
+When the Check_MK helpers are configured with a higher log level than the default
+Notice log level the Check_MK helpers were leaking memory. This can be configured
+by changing the option "Check_MK check helpers" of the global setting "Logging of the core"
+to e.g. Informational.
+
+In this mode the helper gathers information about some changed variables during runtime
+and the memory usage. It also allows to debug different mechanics of the helpers.
+
+If you enabled this, each reload of the core (not restart) was triggering the memory
+leak in the helpers. In extreme situations this could lead to duplication of the memory
+usage on each reload.
Module: check_mk
Branch: master
Commit: 51146ebe5340ba457526aece86f3c4ac0e5fa719
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=51146ebe5340ba…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Tue May 16 11:27:48 2017 +0200
4717 FIX Fixed "corrupted package" archive messages when installing DEB packages baked on SLES
When installing debian agent packages baked with the Check_MK Agent Bakery running on a SLES 12
server this could lead to this message during installation:
dpkg: error processing archive check-mk-agent_1.4.0b5-88de67ef934c3774_all.deb (--install):
corrupted filesystem tarfile - corrupted package archive
Background information: The <tt>tar</tt> files built into the debian package were created with
a tar format that is not supported for the debian package format. We create the packages with
the <tt>gnu</tt> format now on all platforms.
Change-Id: I9444ead7ba81828611f5af1a69ecb97b18ff2c7d
---
.werks/4717 | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/.werks/4717 b/.werks/4717
new file mode 100644
index 0000000..c378ed6
--- /dev/null
+++ b/.werks/4717
@@ -0,0 +1,19 @@
+Title: Fixed "corrupted package" archive messages when installing DEB packages baked on SLES
+Level: 1
+Component: agents
+Class: fix
+Compatible: compat
+Edition: cee
+State: unknown
+Version: 1.5.0i1
+Date: 1494926687
+
+When installing debian agent packages baked with the Check_MK Agent Bakery running on a SLES 12
+server this could lead to this message during installation:
+
+dpkg: error processing archive check-mk-agent_1.4.0b5-88de67ef934c3774_all.deb (--install):
+ corrupted filesystem tarfile - corrupted package archive
+
+Background information: The <tt>tar</tt> files built into the debian package were created with
+a tar format that is not supported for the debian package format. We create the packages with
+the <tt>gnu</tt> format now on all platforms.