ID: 7326
Title: "Update DNS cache" action is now really cleaning up the cache
Component: WATO
Level: 2
Class: Bug fix
Version: 1.6.0i1
As written in the documentation
(https://mathias-kettner.com/cms_wato_hosts.html) Check_MK is keeping an
internal DNS cache for the hosts that have configured no static IP address in
Check_MK:
---
With the host name method Check_MK uses cached data in order to minimise
repeated DNS requests during an Activate Changes – which is very important for
accelerating the activation procedure. Furthermore, the cache ensures that a
changed configuration can still be activated if the DNS stops working.
The catch is that Check_MK doesn't automatically notice the change to an
address in DNS. For this reason, in the host details there is the button which
deletes the entire DNS cache and forces a new resolution at the next Activate
changes. This file is found under ~/var/check_mk/ipaddresses.cache in your
instance, by the way. Deleting this file has the same effect as the button as
described above.
---
The problem was that previous versions did not really delete the entire cache,
but only updated it. We have now changed this to make the cache invalidation
work as intended.
ID: 7247
Title: ps.perf: Fixed incomplete counter cleanup routine, leading to ever-growing counter state files
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The ps check regularly creates counter values with dyamic names and save them into the counter state file.
There is a cleanup routine which removes outdated counters.
This cleanup routine failed at cleaning up counter values from the deprecated ps.perf check.
As a result the check counters file did steadily grow. This has been fixed. The cleanup now also
checks for outdated ps.perf counters.
ID: 7246
Title: Prevent automatic discovery of duplicate services with the same service description
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Hosts using snmp as well as tcp checks may run into a scenario where discovered snmp checks share the same service description as the tcp based checks.
One example is the service description <tt>Uptime</tt>, which is created by the <tt>snmp_uptime</tt> and <tt>uptime</tt> check.
In case of identical service descriptions, the tcp based check wins and the snmp based check is ignored.
ID: 6988
Title: netstat: Fix crashing check on AIX 7
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The netstat command separates the port from the IP address with a dot (.) instead
of a colon (:) on some AIX versions, which the check previously could not parse
correctly. This has been fixed.
ID: 7219
Title: agent_vsphere: Missing data in case of mutliline snapshot description
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
In case a description of a VM snapshot consisted of multiple lines, no
data about the corresponding VM has been obtained.
ID: 7325
Title: check_bi_aggr: Improve GUI application error handling
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
When the webservice detects an error -- such as an authentication problem -- it
does not output the expected data structure, but a string starting with
"ERROR:". This is now correctly being detected and the error is output as check
output, rather than a nasty parsing exception.
ID: 7242
Title: Unreachable site errors respect site filters
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 1.6.0i1
When reports are being created while some distributed site is offline, the
report is prefixed by a "error report" page that is added to inform the user
that the report was created in such a situation and some data may be missing
for this reason.
The error message looks like this: "Not all sites have been queried. Some
information is missing."
The errors were shown for all sites, even when a specific site was queried.
This was a problem, especially in Check_MK Managed Services Edition
environments when creating customer specific reports in the management sites.