ID: 14589
Title: apache_status: Handle Permission Errors
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
If {ENABLE_OMD_SITE_DETECTION} is set to True and the file
/opt/omd/sites/{site_name}/etc/apache/listen-port.conf is not accessible, then
the agent plugin apache_status.py would not produce parseable data. With this
werk, the respective data is skipped.
ID: 15442
Title: df_netscaler: wrong unit shown in graphs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The check "df_netscaler" shows information on filesystem size and usage. The
metrics themselves are correct, but the wrong units were shown in the
associated graphs. This has been fixed.
ID: 15409
Title: Agent receiver crashes on IPv4-only Checkmk servers (regression introduced by werk 15416)
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
<a href="https://checkmk.com/werk/15416">Werk 15416</a> introduced a regression which caused the
agent receiver to crash on IPv4-only Checkmk servers. After starting, the receiver was initially
reported as `running` for a brief amount of time by <tt>omd status</tt>, however, it then crashed
with the following error message:
F+:var/log/agent-receiver/error.log
[ERROR] Can't connect to ('::', 8000)
F-:
ID: 15417
Title: mk_logwatch: Correctly handle UNIX paths with non-UTF-8 characters
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
On UNIX, filenames may consist of arbitrary bytes.
To display filenames in Checkmk, the mk_logwatch plugin assumes a UTF-8 encoding and previously replaced each non-UTF-8
(hence non-printable) byte with the replacement character �.<br>
This lead to the problem that multiple filenames were represented by the same name in Checkmk.<br>
As a result, the logfiles got displayed in one service, with the logfile contents merged to one log view.
In order to handle this situation, mk_logwatch now uses a backslash escape sequence instead of the replacement character.<br>
Non-UTF-8 bytes are now represented by their hexadecimal value with a <tt>\x</tt> prefix.<br>
E.g., monitoring the two files (as shown with <tt>ls</tt>, i.e., with octal escape sequence) <tt>'my'$'\300\201''file'</tt> and
<tt>'my'$'\300\200''file</tt> now yields two services <i>Log my\xc0\x80file</i> and <i>Log my\xc0\x81file</i>,
while it used to yield only one service <i>Log my��file</i> before.
Due to the new service name, you have to discover the newly named services if you are affected by this change.<br>
ID: 15241
Title: Drop configuration variable `ignored_checktypes`
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
This Werk only affects users that use handcrafted .mk files to configure disabled check plugins.
The configuration variable used to do this, <tt>ignored_checktypes</tt>, has no effect anymore.
Please use the host ruleset <i>"Disabled checks"</i> in the <i>Setup</i> menu.
ID: 15153
Title: azure_virtual_machine: Redesign service rule
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, if a mapping for power or provisioning states was configured for some,
but not for all states, the unconfigured states would always be mapped to WARN.
This behavior was confusing and forced the users to configure mapping for all
the states even when they wanted to change the behavior of only one. Moreover,
since the parameters of the rule used to be groups of states, the rule matching
could not take place at the state level.
With this werk, if you configure the state mapping for a single state the state
mapping of all other states will be unaffected.
Previously existing rules are updated to keep the same functionality as before.
ID: 15155
Title: sap_hana_status: Handle WARNING status correctly
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, SAP HANA Database Status service would go to CRIT in case of
database status 'WARNING'.
Now, the service goes to Checkmk state WARN.
ID: 14797
Title: Enable recursive look-up for Samba shares
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
It is now possible to search for files recursively with the agent_smb_share.
The recursion is started if "**" is found within the pattern and the option
"Recursive pattern search" is enabled.
The search is only started from the needed directory on.