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.
Werk 16416 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Make scp command work as site userr on SLES 15
Class: fix
Compatible: compat
Component: omd
Date: 1711615092
Edition: cre
Level: 1
Version: 2.2.0p26
On SUSE Linux Enterprise Server 15 systems, the <code>scp</code> command could crash with
C+:
/usr/bin/ssh: symbol lookup error: /usr/bin/ssh: undefined symbol: EVP_KDF_CTX_free, version OPENSSL_1_1_1d lost connection
C-:
when executed as a site user.
------------------------------------<diff>-------------------------------------------
Title: Make scp command work as site userr on SLES 15
Class: fix
Compatible: compat
Component: omd
Date: 1711615092
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
On SUSE Linux Enterprise Server 15 systems, the <code>scp</code> command could crash with
C+:
/usr/bin/ssh: symbol lookup error: /usr/bin/ssh: undefined symbol: EVP_KDF_CTX_free, version OPENSSL_1_1_1d lost connection
C-:
when executed as a site user.
Werk 16242 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Kill forked processes by mk_oracle under AIX
Class: fix
Compatible: compat
Component: checks
Date: 1709728993
Edition: cre
Level: 1
Version: 2.2.0p26
The agent plugin <code>mk_oracle</code> creates forked processes, e.g. from <code>sqlplus</code>.
In order to reliable clean up stale processes, we kill now the whole process chain under AIX
which corresponds to the stored <code>PID</code>.
We introduce this only for <code>AIX</code> now as we have customers which are affected under that OS.
------------------------------------<diff>-------------------------------------------
Title: Kill forked processes by mk_oracle under AIX
Class: fix
Compatible: compat
Component: checks
Date: 1709728993
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
The agent plugin <code>mk_oracle</code> creates forked processes, e.g. from <code>sqlplus</code>.
In order to reliable clean up stale processes, we kill now the whole process chain under AIX
which corresponds to the stored <code>PID</code>.
We introduce this only for <code>AIX</code> now as we have customers which are affected under that OS.
Werk 16238 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Add m7i.large as aws resource type
Class: feature
Compatible: compat
Component: checks
Date: 1709038229
Edition: cre
Level: 1
Version: 2.2.0p26
You're affected if your aws_ec2_limits check reported "Unknown resource" and you're using "m7i.large".
The aws resource names are changing from time to time and we will need to find a more stable solution for that in the future.
But for now, this will be fixed by adding the resource name "m7i.large" to our internal list of aws resources.
------------------------------------<diff>-------------------------------------------
Title: Add m7i.large as aws resource type
Class: feature
Compatible: compat
Component: checks
Date: 1709038229
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
You're affected if your aws_ec2_limits check reported "Unknown resource" and you're using "m7i.large".
The aws resource names are changing from time to time and we will need to find a more stable solution for that in the future.
But for now, this will be fixed by adding the resource name "m7i.large" to our internal list of aws resources.
Werk 16424 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: omd start redis: Don't Start If Process Already Running
Class: fix
Compatible: compat
Component: omd
Date: 1713456408
Edition: cre
Level: 1
Version: 2.2.0p26
With this Werk, <code>omd start</code> will no longer create a new redis process if redis is already started.
This aligns the behaviour with the other services of a site.
------------------------------------<diff>-------------------------------------------
Title: omd start redis: Don't Start If Process Already Running
Class: fix
Compatible: compat
Component: omd
Date: 1713456408
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
With this Werk, <code>omd start</code> will no longer create a new redis process if redis is already started.
This aligns the behaviour with the other services of a site.
Werk 16456 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Fix licensing recording and verification due to missing instance IDs on remote sites
Class: fix
Compatible: compat
Component: omd
Date: 1710148230
Edition: cme
Level: 1
Version: 2.2.0p26
This situation can be fixed by stopping and starting remote sites via 'omd stop'
and 'omd start',
------------------------------------<diff>-------------------------------------------
Title: Fix licensing recording and verification due to missing instance IDs on remote sites
Class: fix
Compatible: compat
Component: omd
Date: 1710148230
Edition: cme
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
This situation can be fixed by stopping and starting remote sites via 'omd stop'
and 'omd start',
Werk 16319 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Reduce context/search filter for "Metrics graph of a single service"
Class: fix
Compatible: incomp
Component: reporting
Date: 1709025058
Edition: cee
Level: 1
Version: 2.2.0p26
Since 2.2 the content element "Metrics graph of a single service" allowed to
configure multiple context/search filters.
This was wrong because this element is limited to e specific host and service.
This change should have no effect on your configuration but we recommend to
check reports with such content elements.
------------------------------------<diff>-------------------------------------------
Title: Reduce context/search filter for "Metrics graph of a single service"
Class: fix
Compatible: incomp
Component: reporting
Date: 1709025058
Edition: cee
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Since 2.2 the content element "Metrics graph of a single service" allowed to
configure multiple context/search filters.
This was wrong because this element is limited to e specific host and service.
This change should have no effect on your configuration but we recommend to
check reports with such content elements.