Werk 16274 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Unusable services for "HPE Proliant Servers: Raid Status"
key | value
--- | ---
compatible | no
version | 2.3.0b1
date | 2023-12-15T10:35:33+00:00
level | 1
class | fix
component | checks
edition | cre
This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin.
This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade.
In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below.
We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`).
Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like.
We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero').
As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions.
If this affects you, you might also want to fix the services in the monitoring history by running
```
sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/*
```
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Unusable services for "HPE Proliant Servers: Raid Status"
key | value
--- | ---
compatible | no
version | 2.3.0b1
date | 2023-12-15T10:35:33+00:00
level | 1
class | fix
component | checks
edition | cre
This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin.
This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade.
In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below.
- We observed some devices to send `""` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`).
+ We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`).
? ++++
Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like.
- We now replace all null-bytes with `"\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero').
+ We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero').
? +
As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions.
If this affects you, you might also want to fix the services in the monitoring history by running
```
- sed -i 's||\x00|' var/check_mk/core/history var/check_mk/core/archive/*
? -
+ sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/*
? ++++++
```
Title: Validate empty settings for "Maximum long output size"
Class: fix
Compatible: compat
Component: wato
Date: 1692626179
Edition: cre
Knowledge: undoc
Level: 1
Version: 2.1.0p38
It was possible to unset the settings for the global option "Maximum long
output size" leading to an error on activating of changes.
Title: Fix PDF export of host- and servicegroup views
Class: fix
Compatible: compat
Component: reporting
Date: 1704188131
Edition: cee
Level: 1
Version: 2.1.0p38
If you exported a view with host- or servicegroup context, an error like "Error
while rendering element type" was shown because of missing context information.
Title: Fix PDF export of host- and servicegroup views
Class: fix
Compatible: compat
Component: reporting
Date: 1704188131
Edition: cee
Level: 1
Version: 2.2.0p18
If you exported a view with host- or servicegroup context, an error like "Error
while rendering element type" was shown because of missing context information.
Title: pandacom_psu: New PSU types added
Class: fix
Compatible: compat
Component: checks
Date: 1704373672
Edition: cre
Level: 1
Version: 2.1.0p38
Pandacom devices with PSU types 65025-65033 caused a crash during
section parsing.
Now, Checkmk recognizes the new type codes and reports the correct
PSU type.
Title: Validate empty settings for "Maximum long output size"
Class: fix
Compatible: compat
Component: wato
Date: 1704191612
Edition: cre
Level: 1
Version: 2.2.0p18
It was possible to unset the settings for the global option "Maximum long
output size" leading to an error on activating of changes.
Title: pandacom_psu: New PSU types added
Class: fix
Compatible: compat
Component: checks
Date: 1704373672
Edition: cre
Level: 1
Version: 2.2.0p18
Pandacom devices with PSU types 65025-65033 caused a crash during
section parsing.
Now, Checkmk recognizes the new type codes and reports the correct
PSU type.
Title: mssql_backup: fix 'no backup found' for case-insensitive databases
Class: fix
Compatible: compat
Component: checks
Date: 1702370026
Edition: cre
Level: 1
Version: 2.2.0p18
In certain circumstances it was possible that the <code>mssql.vbs</code> agent plugin
returned <code>no backup found</code> because it could not map the found backup to the
database.
The reason for that was, that the comparison between the backups database name
and the database name was case sensitive, but its possible to configure mssql
in a way that backups database name and database name does not match case
sensitive.
We now compare both names on the mssql server so the configured case
sensitivity is respected.
[//]: # (werk v2)
# Fix PDF export of host- and servicegroup views
key | value
---------- | ---
date | 2024-01-02T09:35:31+00:00
version | 2.3.0b1
class | fix
edition | cee
component | reporting
level | 1
compatible | yes
If you exported a view with host- or servicegroup context, an error like "Error
while rendering element type" was shown because of missing context information.
[//]: # (werk v2)
# Validate empty settings for "Maximum long output size"
key | value
---------- | ---
date | 2024-01-02T10:33:32+00:00
version | 2.3.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
It was possible to unset the settings for the global option "Maximum long
output size" leading to an error on activating of changes.