ID: 13693
Title: Dedicated agent updater systemd units
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
In case the linux agent is managed by systemd, the agent
updater now comes with dedicated systemd units to trigger
the update.
This was required by the new agent conroller architecture,
but it also has the advantage that the agent update is
triggered indenpendently from the monitoring data transport.
A misconfigured agent transport no longer locks you out of
the host.
ID: 13539
Title: lnx_thermal: Fix wrong temperature scaling and flapping vanished/new services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
>From kernel docs: on Linux the temperature is reported in milli degrees. On
SunXI the temperature value is measured in degrees.
Moreover the temperature services were seen as vanished if related trip points
were missing. This has also been fixed.
ID: 13577
Title: Service creation when pinging all IPv4/v6
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
When using the rule "Check hosts with PING (ICMP Echo Request)" in combination with
"Ping all IPv4/6 addresses", only a service for the first matching rule was created.
As a result, only one protocol on a dual-stack host was monitored. This is fixed now.
ID: 13562
Title: win_dhcp_pools: Free or used leases statistics are average values not absolute
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Via the command {{netsh dhcp server show mibinfo}} in the agent plugin
{{win_dhcp_pools.bat}} the collected statistics about free or used leases are
average and not absolute values. These average values refer to the last
execution interval, see also the official docs in {{DHCP Service POG.docx}}:
<br>
Task: Capture DHCP services scope usage statistics
<br>
Purpose
<br>
The following activity captures empirical data on DHCP service utilization.
This data, which is collected daily (or multiple times a day) should be
reviewed weekly. It will also be used to create monthly reports that are
reviewed quarterly for SLA/OLA compliance. Service utilization statistics are
different from system performance in that they measure the usage
characteristics of the DHCP service, not the underlying infrastructure such as
disk, memory, or processor.
<br>
Procedure Option 2: Capture DHCP services scope usage statistics using Netsh
command line utility
<br>
This collection should be performed on a consistent schedule, during key times
of the day, such as 08:00, 12:00, and 17:00. The information should be recorded
in a log file with the date appended to the name, such as
“DHCPScopeStats_200305.csv” (indicates a comma separated log for the month of
May 2003). Enterprise environments with many DHCP servers can adopt this option
into a parsing script feeding a SQL Server database.
<br>
1. Open a command shell by clicking the Start menu. Click Run, type cmd and click OK.
2. Type the netsh command: Netsh DHCP Server \\<servername> show mibinfo where
you replace <servername> with the name of an authorized DHCP server.
3. Open the month’s csv log using WordPad and manually record the data as follows:
<br>
“DATE TIME”,”DHCPServer Name”,”Scope IP”,”Total Addresses”,”IPs in Use”, “IPs Available”
<br>
For example:
<br>
05/24/2003 16:58:00.000,sea_dhcpsvr01,192.168.12.0,200,140,60
05/24/2003 16:59:00.000,sea_dhcpsvr02,192.168.13.0,200,10,190
ID: 13340
Title: view: sort perf-o-meter with missing value
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
When sorting the perf-o-meter missing values used
to be treated as equal to all other values. This
lead an incorrect sorting in a view.
The missing entries are now treated as smaller
than all other values.
ID: 13669
Title: Fix syntax error if display name is used in notifications on appliances
Component: Notifications
Level: 1
Class: Bug fix
Version: 2.2.0i1
This problem only occured on Checkmk appliances.
If the option "From" - "Display name" was used in notifications, mails could
not be sent. The mail log showed "Bad recipient address syntax" errors
instead.
ID: 13636
Title: Fix xinetd installation problem on SLES15
Component: Other Components
Level: 1
Class: Bug fix
Version: 2.2.0i1
When trying to install Checkmk on SLES15 this failed, because the package
dependency 'xinetd' could not be provided by the official package repositories.
It is not possible to get xinetd from official SLES package repositories,
because it has been dropped in favour of systemd.
The switch to systemd is possible, if you can register regular services to the
systemd unit system and let systemd manage your units. But in our case, where
we have an xinetd process that is managed as part of an OMD site, this way will
not work.
Users were able to solve the situation locally by installing xinetd from 3rd
party sources, like for example OpenSUSE.org repositories. However, this
approach is not supported by SLES nor straight forward for users.
To make the installation more straight forward again, we now drop the xinetd
package dependency for all supported SLES distributions from our Checkmk
packages and ship xinetd together with Checkmk.
ID: 13576
Title: Quoting of mk_redis commandline arguments
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The section of the agent plugin mk_redis may contain the following error message:
<<<redis_info:sep(58)>>>
[[[127.0.0.1;6379|127.0.0.1|6379]]]
Unrecognized option or bad number of args
This was caused by invalid quoting of the command line arguments and is fixed now.
ID: 13692
Title: Checkmk agent: do not support systemd versions prior to 220
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The Checkmk agent no longer uses systemd versions prior to 220.
These systemd versions either do not support features the agent may need
(e.g. setting of the REMOTE_ADDR environment variable) or they are buggy
(e.g. <a href="https://github.com/systemd/systemd/issues/1742">ExecStopPost</a>)
On theses systems, the agent will try to use xinetd.