Module: check_mk
Branch: master
Commit: 168cbcc2dc0ac4df8e71cf15dc133a493c5792d2
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=168cbcc2dc0ac4…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Mon Apr 16 13:42:04 2018 +0200
5978 FIX Fixed possible exception when user has invalid idle timeout value configured
The login session idle timeout can be configured individually per user. This setting
is stored in the file <tt>var/check_mk/web/[user]/idle_timeout.mk</tt>. When this
file contains an invalid value, the global default value is used instead of raising
an error message.
Change-Id: I7bbec234d0dcd8acb467b1422fbc2e458ec60116
---
.werks/5978 | 14 ++++++++++++++
web/htdocs/userdb.py | 8 +++++++-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/.werks/5978 b/.werks/5978
new file mode 100644
index 0000000..3018567
--- /dev/null
+++ b/.werks/5978
@@ -0,0 +1,14 @@
+Title: Fixed possible exception when user has invalid idle timeout value configured
+Level: 1
+Component: multisite
+Class: fix
+Compatible: compat
+Edition: cre
+State: unknown
+Version: 1.6.0i1
+Date: 1523878776
+
+The login session idle timeout can be configured individually per user. This setting
+is stored in the file <tt>var/check_mk/web/[user]/idle_timeout.mk</tt>. When this
+file contains an invalid value, the global default value is used instead of raising
+an error message.
diff --git a/web/htdocs/userdb.py b/web/htdocs/userdb.py
index be52ffa..b8139a5 100644
--- a/web/htdocs/userdb.py
+++ b/web/htdocs/userdb.py
@@ -912,7 +912,13 @@ def contactgroups_of_user(user_id):
def convert_idle_timeout(value):
- return value != "False" and int(value) or False
+ if value == "False":
+ return False # Idle timeout disabled
+
+ try:
+ return int(value)
+ except ValueError:
+ return None # Invalid value -> use global setting
#.
Module: check_mk
Branch: master
Commit: faf55a5cf94147003251d62e38984770ea8009e5
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=faf55a5cf94147…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Mon Apr 16 13:27:51 2018 +0200
5977 FIX Fixed broken dropdown fields in several places
Some dropdown (select) fields were broken in Check_MK 1.5.0 for a longer time,
especially in WATO configuration dialogs. This issue existed in all previous
1.5.0 releases.
E.g. when setting the "Match syslog priority" option in a Event Console rule,
the selected option was not persisted as expected.
Change-Id: I68d266e1e12fdbd6249c4c5cc5741112fc84381b
---
.werks/5977 | 16 ++++++++++++++++
web/htdocs/htmllib.py | 4 ++--
2 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/.werks/5977 b/.werks/5977
new file mode 100644
index 0000000..1c90837
--- /dev/null
+++ b/.werks/5977
@@ -0,0 +1,16 @@
+Title: Fixed broken dropdown fields in several places
+Level: 2
+Component: multisite
+Class: fix
+Compatible: compat
+Edition: cre
+State: unknown
+Version: 1.6.0i1
+Date: 1523877884
+
+Some dropdown (select) fields were broken in Check_MK 1.5.0 for a longer time,
+especially in WATO configuration dialogs. This issue existed in all previous
+1.5.0 releases.
+
+E.g. when setting the "Match syslog priority" option in a Event Console rule,
+the selected option was not persisted as expected.
diff --git a/web/htdocs/htmllib.py b/web/htdocs/htmllib.py
index 3692a82..0357c31 100644
--- a/web/htdocs/htmllib.py
+++ b/web/htdocs/htmllib.py
@@ -2430,8 +2430,8 @@ class html(HTMLGenerator, RequestHandler):
if error:
self.open_x(class_="inputerror")
- if "read_only" in attrs:
- attrs["disabled"] = "disabled" if attrs.pop("read_only") else None
+ if "read_only" in attrs and attrs.pop("read_only"):
+ attrs["disabled"] = "disabled"
self.hidden_field(varname, current, add_var=False)
self.open_select(name=varname, id_=varname, **attrs)
Module: check_mk
Branch: master
Commit: 4962375029dde72e3347b38507f70eeddb59d893
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=4962375029dde7…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Thu Apr 12 21:26:11 2018 +0200
5975 FIX Agent output / SNMP walk download: Now processed asynchronously
The download of the agent output or SNMP walks, that can be triggered from the
hosts or Check_MK service context menus could run into time out situations with
bad error messages like "Gateway timeout" in case the destination devices need
more than ~110 seconds to respond.
We have now changed the process of fetching the data to be executed as
background job. The GUI is displaying the progress during processing and
presenting a download icon on the progress page to finally download the created
file.
Change-Id: Ia3fc705454d2b5409bc852421202b8df5bf104ad
---
.werks/5975 | 19 ++++++
web/htdocs/wato.py | 151 ++++++++++++++++++++++++++++++++++++-------
web/plugins/icons/builtin.py | 1 +
web/plugins/icons/wato.py | 18 ++++--
web/plugins/pages/wato.py | 1 +
5 files changed, 164 insertions(+), 26 deletions(-)
Diff: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commitdiff;h=4962375029…
Module: check_mk
Branch: master
Commit: 49518478a90ae071e54dd54a90ff4dd1b03acbb9
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=49518478a90ae0…
Author: Sven Panne <sp(a)mathias-kettner.de>
Date: Mon Apr 16 11:54:36 2018 +0200
5836 FIX Event Console messages without a service level can be matched against service level 0 now.
Various message sources, e.g. syslog messages or SNMP traps, do not carry a
service level with them. If an event console rule specified a matching
criterion including the service level value 0 (meaning "no service level
specified"), the rule didn't fire for such messages. This behavior was
confusing and inconsistent with the rule matching for notifications.
Messages not carrying a service level have an implicit service level 0 now,
so EC rules can match for this case.
Change-Id: I1d77bbb86e610c1b1b61ed910fb3716a6259a646
---
.werks/5836 | 17 +++++++++++++++++
cmk/ec/main.py | 7 +------
2 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/.werks/5836 b/.werks/5836
new file mode 100644
index 0000000..3db21e8
--- /dev/null
+++ b/.werks/5836
@@ -0,0 +1,17 @@
+Title: Event Console messages without a service level can be matched against service level 0 now.
+Level: 1
+Component: ec
+Compatible: compat
+Edition: cre
+Version: 1.6.0i1
+Date: 1523871989
+Class: fix
+
+Various message sources, e.g. syslog messages or SNMP traps, do not carry a
+service level with them. If an event console rule specified a matching
+criterion including the service level value 0 (meaning "no service level
+specified"), the rule didn't fire for such messages. This behavior was
+confusing and inconsistent with the rule matching for notifications.
+
+Messages not carrying a service level have an implicit service level 0 now,
+so EC rules can match for this case.
diff --git a/cmk/ec/main.py b/cmk/ec/main.py
index 241c211..7bc7013 100644
--- a/cmk/ec/main.py
+++ b/cmk/ec/main.py
@@ -2420,12 +2420,7 @@ class EventServer(ECServerThread):
sl_from, sl_to = rule["match_sl"]
if sl_from > sl_to:
sl_to, sl_from = sl_from, sl_to
- p = event.get("sl")
- if p is None:
- if self._config["debug_rules"]:
- self.logger.info(" did not match, because no service level is set in event")
- return False
-
+ p = event.get("sl", 0)
if p < sl_from or p > sl_to:
if self._config["debug_rules"]:
self.logger.info(" did not match because of wrong service level %d (need %d..%d)" %