Werk 16179 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: size_trend: Treat negative free space as 0 in all cases
Class: fix
Compatible: compat
Component: checks
Date: 1710929049
Edition: cre
Level: 1
Version: 2.2.0p26
Before the version 2.2.0p21, 'Time left until full' was reported to be 0 in case of
devices reporting negative free space.
With werk 16330, we stopped reporting the metric in case of very small size changes
because it lead to infinite values. With this change the behavior was unintentionally
also changed for negative free space values.
This werk restores the same functionality in case of negative free space.
------------------------------------<diff>-------------------------------------------
Title: size_trend: Treat negative free space as 0 in all cases
Class: fix
Compatible: compat
Component: checks
Date: 1710929049
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Before the version 2.2.0p21, 'Time left until full' was reported to be 0 in case of
devices reporting negative free space.
With werk 16330, we stopped reporting the metric in case of very small size changes
because it lead to infinite values. With this change the behavior was unintentionally
also changed for negative free space values.
This werk restores the same functionality in case of negative free space.
Werk 16404 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy
Class: fix
Compatible: compat
Component: omd
Date: 1707904094
Edition: cre
Level: 1
Version: 2.2.0p26
Since Checkmk 2.2.0 there is a agent CA located in <code>etc/ssl/agents/</code>. This CA is
different from the site CA. In particular, if updating from 2.1.0 to 2.2.0,
Checkmk will create a symlink <code>etc/ssl/agents/legacy_ca.pem</code>, which points to
<code>etc/ssl/ca.pem</code>. After performing an <code>omd cp</code>. This symlink would still point
to the site, which was the source of the copy. The symlink is now relative. If
the site was created with version 2.2.0 or above no symlink is needed.
------------------------------------<diff>-------------------------------------------
Title: omd cp: Fix etc/ssl/agents/legacy_ca.pem Points to Source of Copy
Class: fix
Compatible: compat
Component: omd
Date: 1707904094
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Since Checkmk 2.2.0 there is a agent CA located in <code>etc/ssl/agents/</code>. This CA is
different from the site CA. In particular, if updating from 2.1.0 to 2.2.0,
Checkmk will create a symlink <code>etc/ssl/agents/legacy_ca.pem</code>, which points to
<code>etc/ssl/ca.pem</code>. After performing an <code>omd cp</code>. This symlink would still point
to the site, which was the source of the copy. The symlink is now relative. If
the site was created with version 2.2.0 or above no symlink is needed.
Werk 16340 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: docker_node_images: KeyError: 'VirtualSize'
Class: fix
Compatible: compat
Component: checks
Date: 1709742514
Edition: cre
Level: 1
Version: 2.2.0p26
In newer versions of the Docker API the information about the 'VirtualSize' of a node image is not available, because it has been deprecated.
From now on the plugin will use 'VirtualSize' if available, and 'Size' if not.
------------------------------------<diff>-------------------------------------------
Title: docker_node_images: KeyError: 'VirtualSize'
Class: fix
Compatible: compat
Component: checks
Date: 1709742514
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
In newer versions of the Docker API the information about the 'VirtualSize' of a node image is not available, because it has been deprecated.
From now on the plugin will use 'VirtualSize' if available, and 'Size' if not.
Werk 16240 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Crash on missing thread count on AIX
Class: fix
Compatible: compat
Component: checks
Date: 1709129579
Edition: cre
Level: 1
Version: 2.2.0p26
You're affected if you want to monitor your CPU and the cpu check crashes with something like:
C+:
File "/omd/sites/YOURSITE/lib/python3/cmk/base/plugins/agent_based/cpu.py", line 48, in parse_cpu
count=int(row[3].split("/")[1]),
ValueError (invalid literal for int() with base 10: '')
C-:
We saw this happening on AIX system when the ps information cannot be obtained due to low memory.
The parsing is now more resilient against such missing data.
------------------------------------<diff>-------------------------------------------
Title: Crash on missing thread count on AIX
Class: fix
Compatible: compat
Component: checks
Date: 1709129579
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
You're affected if you want to monitor your CPU and the cpu check crashes with something like:
C+:
File "/omd/sites/YOURSITE/lib/python3/cmk/base/plugins/agent_based/cpu.py", line 48, in parse_cpu
count=int(row[3].split("/")[1]),
ValueError (invalid literal for int() with base 10: '')
C-:
We saw this happening on AIX system when the ps information cannot be obtained due to low memory.
The parsing is now more resilient against such missing data.
Werk 16080 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: mssql_datafiles/transactionlogs: Regression in maximum size calculation
Class: fix
Compatible: compat
Component: checks
Date: 1694589964
Edition: cre
Level: 1
Version: 2.2.0p26
This is a follow-up to Werk #14421.
Since Checkmk 2.1.0p5, we calculate the maximum size as the sum of available
and used size for unlimited instances.
However, in some cases, we accidentally drop explicit thresholds for the
maximum size if avaiable, falling back to the unlimited case.
------------------------------------<diff>-------------------------------------------
Title: mssql_datafiles/transactionlogs: Regression in maximum size calculation
Class: fix
Compatible: compat
Component: checks
Date: 1694589964
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
This is a follow-up to Werk #14421.
Since Checkmk 2.1.0p5, we calculate the maximum size as the sum of available
and used size for unlimited instances.
However, in some cases, we accidentally drop explicit thresholds for the
maximum size if avaiable, falling back to the unlimited case.
Werk 16468 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: RabbitMQ: extend help text for instance name with macro option
Class: feature
Compatible: compat
Component: wato
Date: 1707728977
Edition: cre
Level: 1
Version: 2.2.0p26
------------------------------------<diff>-------------------------------------------
Title: RabbitMQ: extend help text for instance name with macro option
Class: feature
Compatible: compat
Component: wato
Date: 1707728977
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Werk 16237 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Path to mysql.ini under Windows for mk_sql
Class: fix
Compatible: compat
Component: checks
Date: 1708687568
Edition: cre
Level: 1
Version: 2.2.0p26
If you've been using mysql and the corresponding agent plugin <em>mk_sql</em>
under Windows, the plugin may have crashed and the agent output would then
show the following error:
C+:
<<<mysql_ping>>>
[[MySQL83]]
mysqladmin: File '\etc\check_mk\mysql.local.ini' not found (OS errno 2 - No such file or directory)
mysqladmin: [ERROR] Stopped processing the 'include' directive in file C:\ProgramData\checkmk\agent\config\mysql.ini at line 8.
C-:
Under Windows, the plugin config path <code>C:\ProgramData\checkmk\agent\config</code> is now used.
In contrast to the corresponding Linux plugin <code>mk_mysql</code>, the config path under Windows cannot be changed.
------------------------------------<diff>-------------------------------------------
Title: Path to mysql.ini under Windows for mk_sql
Class: fix
Compatible: compat
Component: checks
Date: 1708687568
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
If you've been using mysql and the corresponding agent plugin <em>mk_sql</em>
under Windows, the plugin may have crashed and the agent output would then
show the following error:
C+:
<<<mysql_ping>>>
[[MySQL83]]
mysqladmin: File '\etc\check_mk\mysql.local.ini' not found (OS errno 2 - No such file or directory)
mysqladmin: [ERROR] Stopped processing the 'include' directive in file C:\ProgramData\checkmk\agent\config\mysql.ini at line 8.
C-:
Under Windows, the plugin config path <code>C:\ProgramData\checkmk\agent\config</code> is now used.
In contrast to the corresponding Linux plugin <code>mk_mysql</code>, the config path under Windows cannot be changed.
Werk 16379 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Allow disabling of bulk walks on inline SNMPv3 hosts
Class: fix
Compatible: compat
Component: checks
Date: 1710141228
Edition: cre
Level: 1
Version: 2.2.0p26
It was impossible to disable bulkwalks for SNMP version 3 hosts using the inline SNMP backend.
It is fixed now in the sense that it works as in the classic backend:
In order to disable bulkwalks <b>for SNMP version 3</b> hosts, you need to make sure they do <b>not</b> match the ruleset "Enable SNMPv2c and bulkwalk for host".
A more thorough fix for this bug and the related phrasing in the rulesets is implemented in for Checkmk 2.3, but it was too risky to port into the stable releases.
See <a href="https://checkmk.com/werk/16382">Werk #16382</a> for more on that.
------------------------------------<diff>-------------------------------------------
Title: Allow disabling of bulk walks on inline SNMPv3 hosts
Class: fix
Compatible: compat
Component: checks
Date: 1710141228
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
It was impossible to disable bulkwalks for SNMP version 3 hosts using the inline SNMP backend.
It is fixed now in the sense that it works as in the classic backend:
In order to disable bulkwalks <b>for SNMP version 3</b> hosts, you need to make sure they do <b>not</b> match the ruleset "Enable SNMPv2c and bulkwalk for host".
A more thorough fix for this bug and the related phrasing in the rulesets is implemented in for Checkmk 2.3, but it was too risky to port into the stable releases.
See <a href="https://checkmk.com/werk/16382">Werk #16382</a> for more on that.
Werk 16414 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Migrate Old Configuration Format For 'Disable notifications'
Class: fix
Compatible: compat
Component: notifications
Date: 1710770356
Edition: cre
Level: 1
Version: 2.2.0p26
In Werk #6417, we announced that some changes to <code>etc/check_mk/conf.d/wato/contacts.mk</code> are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
C+:
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
C-:
With this Werk, the configuration is migrated automatically.
------------------------------------<diff>-------------------------------------------
Title: Migrate Old Configuration Format For 'Disable notifications'
Class: fix
Compatible: compat
Component: notifications
Date: 1710770356
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
In Werk #6417, we announced that some changes to <code>etc/check_mk/conf.d/wato/contacts.mk</code> are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
C+:
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
C-:
With this Werk, the configuration is migrated automatically.
Werk 16420 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: jolokia_info: Support Version 2.0
Class: feature
Compatible: compat
Component: checks
Date: 1712568535
Edition: cre
Level: 1
Version: 2.2.0p26
Jolokia 2.0 was released 2023-12-19. With the release some changes to the Jolokia Protocol have been
introduced. If a user installed this version of Jolokia, the check plugin <code>jolokia_info</code> showed
<code>unknown</code> instead of the product information. After updating the agent plugin <code>mk_jolokia.py</code>, the
correct information will be shown again.
------------------------------------<diff>-------------------------------------------
Title: jolokia_info: Support Version 2.0
Class: feature
Compatible: compat
Component: checks
Date: 1712568535
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Jolokia 2.0 was released 2023-12-19. With the release some changes to the Jolokia Protocol have been
introduced. If a user installed this version of Jolokia, the check plugin <code>jolokia_info</code> showed
<code>unknown</code> instead of the product information. After updating the agent plugin <code>mk_jolokia.py</code>, the
correct information will be shown again.