ID: 8780
Title: mknotifyd: fix race condition in distributed setups
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.7.0i1
In a distributed setup a slave site may try to deliver
notifications locally during an activate changes even
though the slave site should forward notifications to
the master site.
This effect appears when the option "Notification Spooling"
is set to "Asynchronous local delivery by notification
spooler" in the global settings and to "Forward to
remote site by notification spooler" in the "Site specific
global settings" of the slave site.
This werk fixes this issue by locking the Checkmk
configuration when a configuration snapshot is installed
on the remote site. This way the "cmk --notify"
command and the mknotifyd cannot use a partially installed
Checkmk configuration.
As a workaround the "Notification Spooling" can be set to
"Forward to remote site by notification spooler" in the
global settings and to "Asynchronous local delivery by
Notification spooler" in the "Site specific global settings"
of the slave site.
ID: 7966
Title: Web API: Fix broken set_hosttags API call
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The API call for updating the tag configuration did not work in previous 1.6 releases.
Calls did always fail with an error like this: "AttributeError: 'Rule' object has no attribute 'tag_specs'\n".
ID: 7967
Title: Fix blocked liveproxy after executing livestatus commands
Component: Livestatus Proxy
Level: 2
Class: Bug fix
Version: 1.7.0i1
The 1.6.0b3 release introduced an regression which made the liveproxyd treat
channels to sites as blocked after executing a livestatus command. When
executing multiple commands this resulted in a busy site and finally GUI
timeouts, because all channels were blocked.
ID: 7948
Title: mk_logwatch: process new files from the beginning
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
If a new logfile is found we usually skip to its end to avoid processing ancient log messages.
You can now configure mk_logwatch to start processing the file from the beginning and see all
messages that may already be present.
To enable this behaviour, either set the corresponding flag in the agent bakery rule, or add
'fromstart=True' to your configuration file.
ID: 7753
Title: esx_vsphere_counters: Fixed crash on missing values
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
We have seen cases in which the counter "disk.numberWrite" was missing and a
KeyError was raised. This has been fixed.
ID: 7264
Title: Added new metric painter: Displays the value of a single configurable metric
Component: Multisite
Level: 1
Class: New feature
Version: 1.7.0i1
ID: 7947
Title: ps: Missing services for non-matching subexpressions
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
If you are discovering services with a process name pattern that included non-matching
subexpressions, the check could not see the corresponding services, resulting in a process
count of zero.
If you are affected by this, please rediscover the affected services.
ID: 7912
Title: Fix host tag update problem
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
With 1.6 the data structure of tag definitions has been changed
and also moved to another file. WATO is now saving the tags in
<tt>etc/check_mk/conf.d/wato/tags.mk</tt> instead of
<tt>etc/check_mk/conf.d/wato/hosttags.mk</tt>.
There is no manual action needed for migration. During update
from previous versions the old configuration is read and saved
in the new format and file.
In previous 1.6 versions the migration did not correctly delete
the <tt>etc/check_mk/conf.d/wato/hosttags.mk</tt> after saving
it in the new file which is fixed now.