Module: check_mk
Branch: master
Commit: 70a9f187f60a028eeda50b9f172f81b4f348e856
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=70a9f187f60a02…
Author: Andreas Boesl <ab(a)mathias-kettner.de>
Date: Tue Sep 19 10:41:57 2017 +0200
5230 FIX logwatch/logwatch.ec: fixed "no forwarding" option in rule "Logwatch Event Console Forwarding"
If you configured a "Logwatch Event Console Forwarding" rule and used the
setting "No forwarding" (Messages are handled by logwatch), the logfiles weren't handled
by logwatch at all. They simply got dropped.
This has been fixed. If you update to this version you might see an increase
in logwatch checks, if you used the "No forwarding" setting.
---
.werks/5230 | 17 +++++++++++++++++
checks/logwatch | 2 +-
2 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/.werks/5230 b/.werks/5230
new file mode 100644
index 0000000..470f1bc
--- /dev/null
+++ b/.werks/5230
@@ -0,0 +1,17 @@
+Title: logwatch/logwatch.ec: fixed "no forwarding" option in rule "Logwatch Event Console Forwarding"
+Level: 1
+Component: checks
+Compatible: compat
+Edition: cre
+Version: 1.5.0i1
+Date: 1505810291
+Class: fix
+
+If you configured a "Logwatch Event Console Forwarding" rule and used the
+setting "No forwarding" (Messages are handled by logwatch), the logfiles weren't handled
+by logwatch at all. They simply got dropped.
+
+This has been fixed. If you update to this version you might see an increase
+in logwatch checks, if you used the "No forwarding" setting.
+
+
diff --git a/checks/logwatch b/checks/logwatch
index ec4b69c..88434e4 100644
--- a/checks/logwatch
+++ b/checks/logwatch
@@ -82,7 +82,7 @@ def logwatch_select_forwarded(info):
logfile_name = line[3:-3]
# Is forwarding enabled in general?
- if forward_settings and forward_settings[0] != None:
+ if forward_settings and forward_settings[0]:
if logwatch_ec_forwarding_enabled(forward_settings[0], logfile_name):
forwarded_logs.append(logfile_name)
else:
Module: check_mk
Branch: master
Commit: 059ac9eb408aa20832c254be5986902d9ef1e505
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=059ac9eb408aa2…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Mon Sep 18 16:10:32 2017 +0200
3919 FIX PDF: Improved handling of long words in text wrapping
Added some word wrapping functionality to the text wrapping algorithm
that is used to fit texts into areas of PDF documents. For example
when adding text to table cells words may now be wrapped if needed.
---
.werks/3919 | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/.werks/3919 b/.werks/3919
new file mode 100644
index 0000000..cda563a
--- /dev/null
+++ b/.werks/3919
@@ -0,0 +1,12 @@
+Title: PDF: Improved handling of long words in text wrapping
+Level: 1
+Component: reporting
+Compatible: compat
+Edition: cre
+Version: 1.5.0i1
+Date: 1505743729
+Class: fix
+
+Added some word wrapping functionality to the text wrapping algorithm
+that is used to fit texts into areas of PDF documents. For example
+when adding text to table cells words may now be wrapped if needed.
Module: check_mk
Branch: master
Commit: 895412861e5f5d8dd49b0614286b74211b8d4666
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=895412861e5f5d…
Author: Marcel Arentz <ma(a)mathias-kettner.de>
Date: Mon Sep 18 14:51:25 2017 +0200
5016 FIX hp_proliant_temp: Fixed crash if thresholds are set manually
The device delivers optionally thresholds for it's parts. If not, -99 will
be that value. A service with that device threshold crashed if a user would
set up thresholds for it's own. This is now fixed.
Change-Id: I97b3a3a8d068453b86c66cf3a29814cb94e22cba
---
.werks/5016 | 12 ++++++++++++
checks/hp_proliant_temp | 2 +-
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/.werks/5016 b/.werks/5016
new file mode 100644
index 0000000..6c0eadc
--- /dev/null
+++ b/.werks/5016
@@ -0,0 +1,12 @@
+Title: hp_proliant_temp: Fixed crash if thresholds are set manually
+Level: 1
+Component: checks
+Compatible: compat
+Edition: cre
+Version: 1.5.0i1
+Date: 1505738884
+Class: fix
+
+The device delivers optionally thresholds for it's parts. If not, -99 will
+be that value. A service with that device threshold crashed if a user would
+set up thresholds for it's own. This is now fixed.
diff --git a/checks/hp_proliant_temp b/checks/hp_proliant_temp
index 557094e..627fbd2 100644
--- a/checks/hp_proliant_temp
+++ b/checks/hp_proliant_temp
@@ -41,7 +41,7 @@ def check_hp_proliant_temp(item, params, info):
# This case means no threshold available and
# the devices' web interface displays "N/A"
if threshold == "-99" or threshold == "0":
- devlevels = (None, None)
+ devlevels = None
else:
threshold = float(threshold)
devlevels = (threshold, threshold)
Module: check_mk
Branch: master
Commit: a81eb5711d55882e5ebb57068a0dc0b9bc3ef245
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=a81eb5711d5588…
Author: Andreas Boesl <ab(a)mathias-kettner.de>
Date: Mon Sep 18 14:16:44 2017 +0200
5229 FIX Rename host: fixed exception when having more than 1024 users configured
For each configured user, WATO kept a file open during the rename procedure.
Having more than 1024 users breached the <tt>ulimit -n</tt> option and a <tt>Too many open files</tt> exception occurred.
---
.werks/5229 | 12 ++++++++++++
web/htdocs/wato.py | 1 +
2 files changed, 13 insertions(+)
diff --git a/.werks/5229 b/.werks/5229
new file mode 100644
index 0000000..637da3d
--- /dev/null
+++ b/.werks/5229
@@ -0,0 +1,12 @@
+Title: Rename host: fixed exception when having more than 1024 users configured
+Level: 1
+Component: wato
+Class: fix
+Compatible: compat
+Edition: cre
+State: unknown
+Version: 1.5.0i1
+Date: 1505736767
+
+For each configured user, WATO kept a file open during the rename procedure.
+Having more than 1024 users breached the <tt>ulimit -n</tt> option and a <tt>Too many open files</tt> exception occurred.
diff --git a/web/htdocs/wato.py b/web/htdocs/wato.py
index a05d0b8..4887948 100644
--- a/web/htdocs/wato.py
+++ b/web/htdocs/wato.py
@@ -1971,6 +1971,7 @@ def rename_host_in_multisite(oldname, newname):
store.save_data_to_file(favpath, favorites)
users_changed += 1
total_changed += num_changed
+ store.release_lock(favpath)
if users_changed:
return [ "favorites" ] * total_changed