ID: 15865
Title: Aruba 2930M: Fix detection
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0p31
Some devices that include the product code in their system description have not been discovered.
ID: 15980
Title: user: return 400 status code when trying to create or edit an user specifying a non existing customer
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, the user setup endpoint returned a 500 status code whenever
the user tried to create or update an user specifiying a non-existing customer.
This werk fixes this and returns a 400 status code instead
ID: 15863
Title: Add default aggregation modes for some clustered services during update
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0p31
This Werk affects all users that monitor Checkmk clusters using the services listed below.
It mitigates some of the incompatibilites listed in <a href="https://checkmk.com/werk/12908">Werk #12908</a> (please read the werk for full context).
During upgrade from Checkmk 2.0 to 2.1 we add some rules to restore the former behavior of clustered services.
<b>Note:</b>
We can not do this for all affected plugins.
The rules match on the service description, not on the plugin names.
Consider for instance <tt>mrpe</tt>: we can't know what your service description looks like.
The following cluster aggregation modes are configured during update (service description pattern / aggregation mode):
LI: "Apache .* Status": <i>failover</i>
LI: "Site .* statistics": <i>failover</i>
LI: "BIG-IP vCMP Guests": <i>worst</i>
LI: "Node service .*": <i>best</i>
LI: "OMD .* performance": <i>failover</i>
LI: "MSSQL .* File Sizes": <i>worst</i>
LI: "MSSQL .* Locks": <i>worst</i>
LI: "MSSQL .* Locks per Batch": <i>worst</i>
LI: "MSSQL .* Page Activity": <i>worst</i>
LI: "MSSQL .* Transactions": <i>worst</i>
LI: "MSSQL .* Sizes": <i>failover</i>
LI: "MSSQL Datafile .*": <i>failover</i>
LI: "MSSQL Transactionlog .*": <i>failover</i>
LI: "SSL Certificate .*": <i>worst</i>
LI: "SAP HANA Disk .*": <i>best</i>
LI: "SAP HANA ESS .*": <i>best</i>
LI: "SAP HANA Events .*": <i>best</i>
LI: "SAP HANA Instance Status .*": <i>best</i>
LI: "SAP HANA Memory .*": <i>best</i>
LI: "SAP HANA Process .*": <i>best</i>
LI: "SAP HANA Replication Status .*": <i>best</i>
Please review the rules to see if they suit your needs.
ID: 15702
Title: UNIX agents/mk_oracle: Validate termination of cached plugins
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Many UNIX agents (linux, solaris, aix, freebsd, openwrt) as well as the mk_oracle agent plugin
share the same functionality when running asynchronous/cached plugins:<br>
After they got invoked as subprocesses, they will be watched by subsequent calls of the agent.<br>
If they're still running after twice the cache time, they'll be terminated with <tt>kill -9</tt>.
Previously, the termination has not been verified.<br>
As a result, in situations where a processes couldn't be terminated with <tt>kill -9</tt>,
the agent created new processes unlimitedly.
This situation is now mitigated by checking for success after terminating a timed out process.<br>
If the termination failed, no further process of the same plugin will be started.
ID: 15907
Title: check_disk_smb: Now supports password store for setting passwords
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
The corresponding ruleset for configuring the check_disk_smb active check now supports the use of the password store.
Using this new possibility is recommended for all users because of security reasons.
ID: 15820
Title: REST API now accepts '24:00' as a time in time ranges
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Unlike the GUI, the REST API rejected '24:00' as a valid time when handling time ranges.
This is no longer the case.
ID: 15888
Title: folder_config: update endpoint now requires which update option you want
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously when calling update folder, you could pass any combination of
replace all attributes
update some attributes
delete some attributes
Some of these combinations didn't make much sense and could lead to errors.
This werk simplifies this by only allowing one of the options when calling
update folder or bulk update folders.
For update_folder, previously you could do the following
C+:
{
"title": "Virtual Servers.",
"attributes": {"tag_networking": "wan"},
"update_attributes": {"tag_criticality": "prod"},
"remove_attributes": ["tag_foobar"],
}
C-:
This werk modifies this behaviour by forcing the client to select only one action.
C+:
{
"title": "Virtual Servers.",
"attributes": {"tag_networking": "wan"},
}
C-:
OR
C+:
{
"title": "Virtual Servers.",
"update_attributes": {"tag_criticality": "prod"},
}
C-:
OR
C+:
{
"title": "Virtual Servers.",
"remove_attributes": ["tag_foobar"],
}
C-:
ID: 15404
Title: mk_inventory: Fix persistence of inventory data on Solaris
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 2.2.0p7
The <tt>mk_inventory</tt> agent plugin outputs inventory data every four hours (by
default). This output is marked as <tt>persisted</tt> and stored on a Checkmk site
for longer use.
If the persisted option is missing, especially for only-inventory data, then
there might be a flapping effect of the HW/SW Inventory service and superfluous
history entries are added.
ID: 15703
Title: Linux agent updater - Fix missing libcrypt.so.1
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, when running the agent updater, either manually or automatically, it may crash immediately with error message:
C+:
Error loading Python lib '/tmp/_MEIc9TJOz/libpython3.7m.so.1.0': dlopen: libcrypt.so.1: cannot open shared object file: No such file or directory
C-:
Future versions of the agent updater will include the missing library.
Technical background:<br>
This happens on Linux systems that don't come with a <tt>libcrypt.so.1</tt> any longer.<br>
The <tt>cmk-update-agent</tt> executable is supposed to include all needed libraries.<br>
However, in this case, the build mechanism failed to find the linked library.
If you ran into this problem, you will have to reinstall the Checkmk agent (including the agent updater)
on affected hosts after updating your Checkmk site and baking agents.<br>