ID: 10142
Title: mk_logwatch: Explicitly specify encoding of logfiles
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
mk_logwatch tries its best to determine the correct encoding of a file,
and to recover from errors if it is wrong.
If that does not work for you, you can configure a specific encoding using
the bakery rule or by adding e.g. "encoding=latin1" to the options in the
config file (see config examples in {{~MySITE/share/check_mk/agents/cfg_examples/}}).
ID: 10208
Title: check_traceroute: Fixed detection of routers which led to wrong service results
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Routers were not detected correctly if options like '-w', '-W', '-c' or '-C'
were configured. The service status might have been OK instead of WARN or CRIT.
ID: 10242
Title: Fix possible XSS using titles of custom snapins
Component: Multisite
Level: 1
Class: Security fix
Version: 1.7.0i1
Authenticated users that are allowed to configure and share custom snapins
could inject arbitrary JS code to all users which are permitted to view this
snapin.
ID: 10241
Title: Report scheduler: The scheduler and stored report cleanup jobs were not triggered
Component: Reporting & Availability
Level: 2
Class: Bug fix
Version: 1.7.0i1
The scheduled reports were not triggered in previous 1.6 releases.
ID: 10113
Title: heartbeat_crm check: Add "Failed Actions" part to main check, which can now warn if any are present.
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
By default there is no behaviour change. A new GUI-rule was introduced to allow the user to
switch to the new behaviour. When the user activates "show Failed Actions", any Failed Action
entries will be listed in the status-detail column of the Heartbeat CRM General check and the
check will transition to the WARNING level. If no Failed Action is present, the check will be
in the OK state.
ID: 10239
Title: Fix agent host diagnose mostly affecting windows hosts
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
The "Agent" box of the host diagnose page was not returning a result
when contacting some hosts. This was mostly affecting windows hosts,
but could also affect other hosts.
The problem was caused by non ASCII characters in the agent output,
which made the processing fail.
We now first try to decode the agent output with UTF-8, in case this fail we
fallback to the "fallback agent output encoding", which is latin-1. When this
also fails we replace the non decodable characters with some place holder.
ID: 10144
Title: cisco_temperature.dom: Do not crash if no device levels are present
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
>From version 1.6.0 to 1.6.0p2 the check crashed if no warn/crit levels
where provided by the device.
ID: 10022
Title: checkman: Addition of checkman pages for check-mk services
Component: WATO
Level: 1
Class: New feature
Version: 1.7.0i1
Checkman pages for two check-mk services (Check_MK and Check_MK Discovery) have been added.
In addition, the checkman link in the options dropdown of the service has been added for both
checks along with the Check_MK Inventory SW/HW service. The checkman description is also shown
in the table within the service details.
ID: 10240
Title: Removed checks could make discovery page fail
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
In case a host had services configured where the Checkmk check was removed from
an installation, e.g. by uninstalling an MKP, this could break the service
discovery page showing an exception instead of the expected service.
ID: 10188
Title: Windows Agent: Fix possible update / downgrade problems
Component: Checks & agents
Level: 2
Class: Bug fix
Version: 1.7.0i1
Previously Windows Agent used only the file timestamp to determine whether
the file have to be reinstalled.
This may lead to impossibility to update the file if for some reason the
file timestamp was wrong(downgrade, invalid time).
Now Windows Agent compares file content too. If content mismatches,
then the file should be installed even if timestamp is ok.