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.
Werk 16176 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: postfix: Fix Postfix status monitoring for agents run in Docker
Class: fix
Compatible: compat
Component: checks
Date: 1710323821
Edition: cre
Level: 1
Version: 2.2.0p26
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
------------------------------------<diff>-------------------------------------------
Title: postfix: Fix Postfix status monitoring for agents run in Docker
Class: fix
Compatible: compat
Component: checks
Date: 1710323821
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
Werk 16174 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: mongodb_replica_set: Fix replication lag and last replication time
Class: fix
Compatible: compat
Component: checks
Date: 1709804918
Edition: cre
Level: 1
Version: 2.2.0p26
Checkmk previously assumed that timestamps collected from MongoDB oplog
are provided in ms. This wasn't the case, which led to wrong values for
replication lag and last replication time being shown in
the 'MongoDB Replication Lag' service.
------------------------------------<diff>-------------------------------------------
Title: mongodb_replica_set: Fix replication lag and last replication time
Class: fix
Compatible: compat
Component: checks
Date: 1709804918
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
Checkmk previously assumed that timestamps collected from MongoDB oplog
are provided in ms. This wasn't the case, which led to wrong values for
replication lag and last replication time being shown in
the 'MongoDB Replication Lag' service.
Werk 16485 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: host_config: Create hosts in folder with umlauts
Class: fix
Compatible: compat
Component: rest-api
Date: 1710161510
Edition: cre
Level: 1
Version: 2.2.0p26
When creating hosts in a folder with umlauts in the name via one of the
<code>host_config</code> endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.
------------------------------------<diff>-------------------------------------------
Title: host_config: Create hosts in folder with umlauts
Class: fix
Compatible: compat
Component: rest-api
Date: 1710161510
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
When creating hosts in a folder with umlauts in the name via one of the
<code>host_config</code> endpoints the endpoint would return an error 400 even though
the query was correct.
Now the hosts are created correctly.
Werk 16484 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Crash when creating combined graphs with empty time filter
Class: fix
Compatible: compat
Component: multisite
Date: 1709884230
Edition: cre
Level: 1
Version: 2.2.0p26
When creating a combined graph with an empty time filter (e.g. Last service check),
the creation of the combined graph would crash.
This behavior is not consistent with the view filtering behavior,
where the filter is not applied if it is empty.
Now the filter is not applied to combined graphs either.
------------------------------------<diff>-------------------------------------------
Title: Crash when creating combined graphs with empty time filter
Class: fix
Compatible: compat
Component: multisite
Date: 1709884230
Edition: cre
Level: 1
- Version: 2.2.0p25
? ^
+ Version: 2.2.0p26
? ^
When creating a combined graph with an empty time filter (e.g. Last service check),
the creation of the combined graph would crash.
This behavior is not consistent with the view filtering behavior,
where the filter is not applied if it is empty.
Now the filter is not applied to combined graphs either.