ID: 12932
Title: <tt>df</tt>: Show volume name in service output
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.1.0i1
It is now possible to see the volume name in the output of a Filesystem service
for Linux and Windows hosts.
To configure this set the option <tt>Show volume name in service output</tt> in Setup -> Services ->
Service monitoring rules -> Filesystems (used space and growth) to enabled.
ID: 13271
Title: timesyncd increase warn default level for last synchronisation period
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The previous default warn level for the last synchronisation period was
deemed slightly too short. This werk increases this default value.
ID: 13213
Title: real-time-checks: fix decryption if agent encryption is anabled
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Since version 1.2.9 the real time check encryption did not work if
the agent encryption was activated, as the agent also uses
the corresponding secret to encrypt the payload of the real-time
UDP packets in this case.
The Checkmk server now follows this logic when encrypting the
packets.
ID: 13239
Title: Fix possibility to activate changes in read only mode
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
Users with a role with the permission "Activate Foreign Changes" could activate
changes even if the read only mode was set.
ID: 13238
Title: Fix possible core restart of remote sites on every activating of changes
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
If you used local plugins within
"~/local/lib/python3/cmk/base/plugins/agent_based/", the folder "__pycache__"
was always synchronized from the central to the remote site. This caused
problems if the timestamps of the plugins differed on central and remote site.
The remote site would than need a core restart on every activating of changes.
Therefore, this folder is not synched anymore.
Workaround was, to delete the files located within
"~/local/lib/python3/cmk/base/plugins/agent_based/" on the affected site, do a
dummy change for that site on the central site and activate changes again.
ID: 13251
Title: netapp_api_temp: crash on access to non-existing key 'temp-sensor-current-temperature'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The check function assumes there's a key 'temp-sensor-current-temperature' for every `netapp_api_temp`
section element and runs into a KeyError if that isn't the case.
This change preprocesses all entries in a way that only valid entries containing
'temp-sensor-current-temperature' will be processed.
ID: 13162
Title: check_mk_active: fix "AttributeError: 'NoneType' object has no attribute 'split'
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
This werk fixes the following issue with the check_mk_active:
- When the option warn/crit-age-oldest or warn/crit-age-newest was used the following error could occur:
"AttributeError: 'NoneType' object has no attribute 'split'"
ID: 12931
Title: <tt>mk_docker</tt>: Fix crash in mk_docker agent for Python2
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Docker agent plugin for Python2, mk_docker_2.py crashed when fetching df data.
This resulted with an UNKNOWN state in docker_node_info check.
ID: 13231
Title: Fix source of painter "Docker node"
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
The painter, used in views like e.g. "Docker containers", used host labels as
its source. That could lead to wrong results, if the container is already
running on another node but the host label was not updated yet.
We now take the service "Docker container status" to determine the current node
of a container.
ID: 13211
Title: Fix 'only from' monitoring in Check_MK services for systemd hosts
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The <i>Check_MK</i> service did not report the <i>only-from</i>
configuration if the used super server was <tt>systemd</tt> and
the socket unit name did not start with 'check-mk-agent'.
This can either be the case if you are using the Checkmk <b>raw</b>
edition, or you have changed the agent package name via the WATO.
While the <i>only-from</i> setting was enforced correctly,
the agent did not report it back to the monitoring server.
If the agent reports back the effective <i>only-from</i>, the
monitoring server will compare it to the configured value,
and issues a WARNING if the allowed IP addresses deviate from
the expected ones.