Module: check_mk
Branch: master
Commit: df0fe1f79454156e5e170a938e905b4cb715c343
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=df0fe1f7945415…
Author: Tom Baerwinkel <tb(a)mathias-kettner.de>
Date: Fri Nov 9 11:05:19 2018 +0100
6416 FIX mknotifyd: set a default timeout if no value is given for a method
If the option "Timing settings for specific methods" was used for a
notification
method and no explicit timeout was given an exception was raised in the mknotifyd
if a timeout occured. As a result notification processes that run in a timeout
are not killed, the list of notifications that are in progress are not updated
as long as the timed out process exists and the output of the timed out process
is discarded.
The issue is now fixed and the default timeout of 60s is set if no timeout
is specified in the global settings.
If you use the option "Timing settings for specific methods" in versions prior
to 1.5.0p8 please set a timeout explicitlyto circumvent this issue.
Change-Id: I25de48609ab6c00cd594374ffca2c1698c9ed253
---
.werks/6416 | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/.werks/6416 b/.werks/6416
new file mode 100644
index 0000000..69c7fc6
--- /dev/null
+++ b/.werks/6416
@@ -0,0 +1,22 @@
+Title: mknotifyd: set a default timeout if no value is given for a method
+Level: 1
+Component: notifications
+Class: fix
+Compatible: incomp
+Edition: cee
+State: unknown
+Version: 1.6.0i1
+Date: 1541754179
+
+If the option "Timing settings for specific methods" was used for a
notification
+method and no explicit timeout was given an exception was raised in the mknotifyd
+if a timeout occured. As a result notification processes that run in a timeout
+are not killed, the list of notifications that are in progress are not updated
+as long as the timed out process exists and the output of the timed out process
+is discarded.
+
+The issue is now fixed and the default timeout of 60s is set if no timeout
+is specified in the global settings.
+
+If you use the option "Timing settings for specific methods" in versions prior
+to 1.5.0p8 please set a timeout explicitlyto circumvent this issue.