ID: 6387
Title: Fixed staleness of services on piggybacked hosts
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
The VSphere special agent may provide piggyback data for other hosts.
Sometimes all piggybacked services on these hosts became stale because
the piggyback files were incorrectly detected as outdated.
Other piggyback hosts may also be affected.
Internal notes:
A piggyback host writes piggyback files and an additional status file.
The age of each piggyback file is compared to the age of the status file
in order to detect the validity of the piggyback file.
Wihtin the cachefile_age function the timestamp of 'now' is initialized
every time for every file. This may result in disregarded time deltas.
ID: 6377
Title: Bulk discovery was not taking selected options into account
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
The options selected to be performed during bulk discovery were not
used correctly. For example the operation mode was always "Add unmonitored services",
even when other options were selected.
ID: 6376
Title: Analyze configuration: Fixed "Apache number of processes" on SLES
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
An exception could occur for the test "Apache number of processes" on at
least SLES12:
CRIT:
Failed to execute the test ACTestApacheNumberOfProcesses: Traceback (most recent call last):
File "/omd/sites/TESTSITE/share/check_mk/web/htdocs/watolib.py", line 9591, in run
total_result = ACResult.merge(*list(self.execute()))
File "/omd/sites/TESTSITE/share/check_mk/web/plugins/wato/ac_tests.py", line 388, in execute
average_process_size = self._get_average_process_size()
File "/omd/sites/TESTSITE/share/check_mk/web/plugins/wato/ac_tests.py", line 408, in _get_average_process_size
sizes.append(int(summary_line.split()[3][:-1])*1024.0)
ValueError: invalid literal for int() with base 10: 'readonly-private'
ID: 6374
Title: Fixed wrong Check_MK service execution time calculation with special agents
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.6.0i1
When hosts are checked using multiple agents the times of special agents
was not accounted correctly. This resulted in wrong numbers being reported
in the "execution time" output and wrong values in the graphs.
ID: 6375
Title: Fixed sidebar folding when "Show Check_MK edition & version in sidebar" is disabled
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.6.0i1
When the global setting "Show Check_MK edition & version in sidebar" is disabled
the folding of the sidebar was not possible in previous releases. Additionally,
unacknowledged incompatible werks were shown while they should be hidden just
like the version information.
ID: 6205
Title: hp_proliant_psu: HP ProLiant Power Supply Unit
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
Add information on the currently used capacity,
per PS Unit and in total. Apply warning/critical levels to
capacity in percent.
ID: 6140
Title: mssql_blocked_sessions: This check is now instance aware
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.6.0i1
In order to make this check work take the following steps:
<ul>
<li>Install the newest agent plugin {{mssql.vbs}}.</li>
<li>Transform all configured parameters from the old deprecared ruleset
{{MSSQL Blocked Sessions}} into the new ruleset of the same name.</li>
<li>Perform a rediscovery on the affected hosts.</li>
</ul>
ID: 6373
Title: Fixed UnicodeEncodeError when piping "cmk -M" to stream or file
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.6.0i1
The output of e.g. "cmk -M" was not correctly encoded when the output
was written to streams or files leading to a "UnicodeEncodeError: 'ascii' codec can't encode character" error.
ID: 6120
Title: cisco_nexus_cpu: use the ruleset "CPU utilization for simple devices"
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0i1
Since Werk 5748 cisco_nexus_cpu is preferred over cisco_cpu on all Nexus
devices. As a result short peaks in CPU utilization might result in a WARN or
CRIT on devices that used cisco_cpu before, since the cisco_nexus_cpu check
does not deliver averaged values. To add the possibility of averaging to the
cisco_nexus_cpu check the ruleset "CPU utilization for simple devices" is now
used. With this ruleset it is possible to define arbitrary averaging periods.
The old ruleset "CPU utilization for Appliances" is not supported anymore for
the cisco_nexus_cpu check.
To accommodate for this change affected hosts have to be rediscovered and all
rules for devices that use the cisco_nexus_cpu checks have to be moved to the
new ruleset.