ID: 13506
Title: Fix possible unhandled exception if site connection is encrypted
Component: Setup
Level: 1
Class: Bug fix
Version: 2.1.0i1
If you used the option "Encrypt data using TLS" for remote sites, the
connection could not be established, showing the error "Unhandled exception:
30s while reading data from socket. Received data:
{data.getbuffer().nbytes}/{size} bytes".
This affected all encrypted livestatus connections in the Raw Edition and the
connections in the Enterprise edition that did not use the Livestatus proxy
daemon.
ID: 13334
Title: Drop support for Internet Explorer 11 (IE11)
Component: Multisite
Level: 2
Class: New feature
Version: 2.1.0i1
The support for IE11 is dropped beginning with version 2.1 of Checkmk. Since some of our
dependencies already dropped the support and we don't want to ship old/outdated versions
we are dropping support for IE11 as well, prior to the official end of life at 2022-06-15.
ID: 13275
Title: API: fix update host tag group endpoint to return correct status code
Component: REST API
Level: 1
Class: Bug fix
Version: 2.1.0i1
In the previous version, the host tag group update endpoint returned a
500 error status code when the user attempted to update a group which
was included by other entities, such as a host, without providing the
repair parameter.
ID: 13320
Title: omd update: Add version compatibility barrier
Component: Site Management
Level: 2
Class: New feature
Version: 2.1.0i1
For some time now, we have been recommending that, in the case of major updates
over several versions, the updates to the individual versions should be made in
stages, e.g. in the case of a migration from 1.5 to 2.0, the version 1.5 should
first be updated to 1.6 and then to 2.0.
Furthermore, <tt>omd update</tt> does support downgrades to older major
versions. However, a lot of manual adjustments are necessary to make the
configuration and runtime data of the site compatible to an older major version
again. So we don't recommend to do this step either.
This change now introduces a hard barrier in the <tt>omd update</tt> command,
which forces the above recommendations.
Examples:
<ul>
<li>1.6 to 2.0 is allowed</li>
<li>1.6 to 2.1 is blocked</li>
<li>2.0 to 2.1 is allowed</li>
<li>2.0 to 2.2 is blocked</li>
<li>2.0 to 3.0 is allowed</li>
<li>2.1 to 3.1 is allowed</li>
</ul>
You can disable this new check by using the <tt>omd -f update [site]</tt>
command. However, sites that have been updated this way will no longer be
supported by us.
ID: 11822
Title: mk_logwatch crashes in debug mode
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In case the agent plugin mk_logwatch was started in debug mode, it was crashing due to the not-yet created state file.
This is fixed now.
ID: 13190
Title: veritas_vcs: cluster behaviour regresses from Checkmk version <= 1.6
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The veritas_vcs check determines the state of its service in the following
way:<br>
<br>
OK: All nodes are running<br>
OK: At least one node is online or running, others may be offline<br>
WARN: All nodes are offline<br>
CRIT: At least one node is faulted<br>
UNKNOWN: At least one node is unknown<br>
<br>
(Of course this can be configurable).<br>
<br>
The cluster functionality of this check did not adhere to these priorities to
determine the overall state of the clustered service. This has been fixed.
ID: 13189
Title: ps: irregular line continuation in Windows agent output leads to crash
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
In some cases, the agent output of the ps section contains processes that have
a newline character in the process description, which caused the ps check to
crash. This has been observed when an executable is run with parameters, e.g.
<tt>myscript.exe -param1 val1 -param2 val2</tt>. This has been fixed
ID: 13399
Title: RESTAPI: Endpoint for downloading agent by host name
Component: Core & setup
Level: 1
Class: New feature
Version: 2.1.0i1
Agent can now be downloaded by operating system and host name:
<tt>/check_mk/api/1.0/domain-types/agent/actions/download_by_host/invoke?os_type=linux_tgz&host_name=example.com</tt>
The previous URL used to download agents via the agent hash:
<tt>/check_mk/api/1.0/objects/agent_binary/80e99ba3a66d4880?os_type=linux_tgz</tt>
is replaced by
<tt>/check_mk/api/1.0/domain-types/agent/actions/download_by_hash/invoke?os_type=linux_tgz&agent_hash=80e99ba3a66d4880</tt>
In checkmk raw edition the packaged agents can now be downloaded by the following URL:
<tt>/check_mk/api/1.0/domain-types/agent/actions/download/invoke?os_type=linux_deb</tt>
Full description can be found in the built in REST API Documentation.