ID: 10120
Title: Fixed error handling in automation calls
Component: WATO
Level: 2
Class: Bug fix
Version: 1.7.0i1
Under various circumstances, diagnostic output from automation calls (like
warnings etc.) got mangled with the result of the automation call itself.
This could break various things, e.g. activation on changes on local and
remote sites. This has been fixed, the diagnostic output is redirected
to var/log/web.log now.
ID: 10253
Title: Fix possible AttributeError exception on "Parameters of service" page
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
When trying to view the parameters of a "Number of threads" service while
having locally configured rules that were saved with Checkmk before version
1.6, an "AttributeError" crash occurred.
The reason is that this ruleset was converted from a single WARN/CRIT parameter
set to a more complex set of parameters. The check and rule editor are correctly
transforming the old values, but this is not possible on the "Parameters of service"
page.
Instead of the crash Checkmk now prints an error message with a hint that you can
open the rule in question for editing and save it again to fix this issue.
ID: 10252
Title: Fix broken "Start livestatus proxy" global setting after update from CRE to CEE
Component: Site Management
Level: 1
Class: Bug fix
Version: 1.7.0i1
The global setting "Start livestatus proxy" is used to enable the livestatus proxy
daemon in Checkmk sites. It is a "omd config" setting which can also be set using
the Checkmk GUI.
Previous 1.6 versions did not correctly initialize new OMD configuration settings
after "omd update". When updating from CRE to CEE the new configuration option
<tt>CONFIG_LIVEPROXYD='on'</tt> should be added to <tt>etc/omd/site.conf</tt>,
because this file needs to hold the current effective config options for all
available OMD settings. The missing update of this file resulted in a
"KeyError ('site_liveproxyd')" exception in the GUI when trying to edit this
setting.
ID: 10254
Title: Improve error handling of incompatible discovery functions
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.7.0i1
In previous 1.6 versions it could happen that 3rd party checks raise
a TypeError exception resulting in a crash report with a message like
this: <tt>TypeError (inventory_sslcertificates() takes exactly 2 arguments</tt>
This issue occurs because we have removed some compatibility code that
dealt with older discovery function syntax. This was planned to be removed
since 1.2.6 and has now been finally done.
Discovery functions of Checkmk checks take a single argument these days.
This is either the agent <tt>info</tt> structure or, in case a check has
a parse function defined, the output of the parse function <tt>parsed</tt>.
Instead of a crash Checkmk produces an error message that should lead you to
the check plugin in question. You will have to either remove or update the
plugin. Normally you simply need to remove the first argument of the discovery
function.
ID: 10250
Title: Mail graphs: Do not render in dark theme style
Component: Notifications
Level: 1
Class: Bug fix
Version: 1.7.0i1
The graphs in HTML mails were rendered in dark theme style when
the dark theme was configured as default theme in the global
settings. These graphs should not be themed, just like the graphs
in the PDF reports.
ID: 10216
Title: IPMI Management Board: Fixed missing services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
If a host is a no-agent host with an IPMI management board configuration then
the discovery page found some IPMI services. During the check phase these
services were incorrectly filtered out such that no service was checked.
ID: 10083
Title: check_traceroute: Add performance data
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
The traceroute check now displays the number of hops in a graph.
ID: 10331
Title: mk_mysql: set instance alias
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
Instead of using the path to the socket file as instance name, you can define your own instance alias.
You have to re-install your agent to use this feature.