ID: 13732
Title: mk_oracle on AIX, Solaris and UNIX: Solve sync. vs. async sections on hosts with systemd
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The agent plugin {{mk_oracle}} implements its own caching functionality because
of long running SQL statements (and custom SQLs with own cache interalls). But
the execution of synchronous and asynchronous SQls does not work properly with
systemd anymore if the plugin is installed to {{../check_mk_agent/plugins/}}
because the {{check-mk-agent-sync.service}} would wait for all child processes
and may take too long.
In order to solve this situation on hosts with systemd the {{mk_oracle}} must
be installed to {{../check_mk_agent/plugins/NUMBER}} and is now triggered by
the {{check-mk-agent-async.service}} (which runs permanently, every minute).
Details:
<ul>
<li>The plugin is now able to detect the installation folder</li>
<li>On distros without systemd you can keep the plugin below {{../check_mk_agent/plugins/}}</li>
<li>On distros with systemd you have to install the plugin to {{../check_mk_agent/plugins/NUMBER/}}</li>
<li>The recommended NUMBER for this folder is 60</li>
</ul>
If the {{mk_oracle}} is installed to {{../check_mk_agent/plugins/NUMBER}} the
result (which consists of the sync. and async. SQLs) is saved into the Checkmk
agent's spool directory
The limit of this spoolfile is three times the NUMBER (interval).
If the plugin is executed with any CL option, then the output is shown on
{{stdout}} as before.
ID: 14868
Title: Using of the rule 'Installation paths for agents' doesn't crash bake process
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
ID: 14868
Title: Using of the rule 'Installation paths for agents' doesn't crash bake process
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
ID: 14294
Title: Fix empty elements for frontmatter templates
Component: Reporting & Availability
Level: 1
Class: Bug fix
Version: 2.2.0i1
When trying to edit a report that is configured to be a front matter template,
the element and fixel tables were always empty, even when there were elements
configured.
ID: 13750
Title: Support Diagnostics: Add CMC dumps
Component: Setup
Level: 1
Class: New feature
Version: 2.2.0i1
The Support Diagnostics dumps now contain, if selected, the core history, config and state files,
as well as cmcdump files.
Having this information, the tribe29 support team is able to reproduce cmc core issues in your environment.
ID: 14760
Title: Fix "Restricted address missmatch" in "Analyze configuration"
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
The "Restricted address missmatch" option of the setup menu "Analyze
configuration" showed wrong results because it was linked to the previous
ruleset of the configuration option "State in case of restricted address
missmatch".
ID: 14434
Title: FIX chrony check no longer crashes if section is not available
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Chrony check no longer crashes if the section is not available and the service was previously discovered.
Instead of crashing, now it moves to an UNKWOWN state.
ID: 14759
Title: Fix stale services in tactical overview
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk changes the computation of stale services in the tactical overview
sidebar snapin.
So far, the computation was also based on down hosts.
>From now on, down hosts are no longer taken into acount for stale services.
ID: 14508
Title: profiling using "enable_by_var" in the REST API
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
When using the query string variable "_profile=1" to dynamically enable profiling,
the REST API complained about "_profile" being an unknown paramter. This is no longer
the case, as the argument is now removed before passing the request to the REST API.
There are no futher actions to be taken.
ID: 14876
Title: display host tag checkbox correctly in edit host properties
Component: Setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, host tags with single values (i.e. checkboxes) were reset when
the Edit Host Properties page was loaded. Although the save mechanism was
unaffected by this behaviour, the user was required to reclick on the checkbox
whenever the host was edited. This werk resolves this issue.