[//]: # (werk v2)
# jenkins: Remove character limitation in special agent configuration
key | value
---------- | ---
date | 2024-07-24T15:09:54+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously the "Jenkins instance to query" and "Username" fields were limited to 32 characters.
This limitation has been removed.
Werk 14235 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fixed bug during activating changes if the main versions differed between central and remote site
key | value
---------- | ---
date | 2024-07-19T09:59:43+00:00
version | 2.3.0p12
class | fix
edition | cre
component | wato
level | 1
compatible | yes
The following error message was displayed during the activation of changes if the remote site had a newer major version than the central site.
```
cmk.utils.exceptions.MKGeneralException: Configuration update failed
ERROR: The Checkmk site is still running. Please stop the site before updating the configuration.
You can stop the site using 'omd stop'.". Please note that the site configuration has been synchronized partially.
```
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Fixed bug during activating changes if the main versions differed between central and remote site
key | value
---------- | ---
date | 2024-07-19T09:59:43+00:00
- version | 2.3.0p11
? ^
+ version | 2.3.0p12
? ^
class | fix
edition | cre
component | wato
level | 1
compatible | yes
The following error message was displayed during the activation of changes if the remote site had a newer major version than the central site.
```
cmk.utils.exceptions.MKGeneralException: Configuration update failed
ERROR: The Checkmk site is still running. Please stop the site before updating the configuration.
You can stop the site using 'omd stop'.". Please note that the site configuration has been synchronized partially.
```
Werk 16865 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# discovery: Update discovered parameters
key | value
---------- | ---
date | 2024-07-19T15:01:34+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
With the rework of `Bulk discovery` and `Periodic service discovery` in 2.3,
discovered parameters weren't updated anymore if `Refresh all services and host labels (tabula rasa)`
option was used.
With this werk, tabula rasa option works like in the version 2.2.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# discovery: Update discovered parameters
key | value
---------- | ---
date | 2024-07-19T15:01:34+00:00
- version | 2.3.0p11
? ^
+ version | 2.3.0p12
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
With the rework of `Bulk discovery` and `Periodic service discovery` in 2.3,
discovered parameters weren't updated anymore if `Refresh all services and host labels (tabula rasa)`
option was used.
With this werk, tabula rasa option works like in the version 2.2.
Werk 15336 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Add support for MariaDB 11
key | value
---------- | ---
compatible | yes
version | 2.3.0p12
date | 2024-06-10T07:54:55+00:00
level | 1
class | fix
component | checks
edition | cre
MariaDB 11 deprecated mysql* binaries and shows an error message like:
```
mysqladmin: Deprecated program name. It will be removed in a future release, use ‘/usr/bin/mariadb-admin’ instead
```
The agent plugin now checks if the MariaDB binaries are available and prefers them over the mySQL binaries.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Add support for MariaDB 11
key | value
---------- | ---
compatible | yes
- version | 2.3.0p11
? ^
+ version | 2.3.0p12
? ^
date | 2024-06-10T07:54:55+00:00
level | 1
class | fix
component | checks
edition | cre
MariaDB 11 deprecated mysql* binaries and shows an error message like:
```
mysqladmin: Deprecated program name. It will be removed in a future release, use ‘/usr/bin/mariadb-admin’ instead
```
The agent plugin now checks if the MariaDB binaries are available and prefers them over the mySQL binaries.
Werk 16441 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# omd cleanup: Remove Version 2.3.0.cee
key | value
---------- | ---
date | 2024-07-16T13:04:53+00:00
version | 2.3.0p12
class | fix
edition | cre
component | omd
level | 1
compatible | yes
Previously, the command `omd cleanup` would show the following message.
```
2.3.0.cee Could not determine package. Keeping this version.
```
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# omd cleanup: Remove Version 2.3.0.cee
key | value
---------- | ---
date | 2024-07-16T13:04:53+00:00
- version | 2.3.0p11
? ^
+ version | 2.3.0p12
? ^
class | fix
edition | cre
component | omd
level | 1
compatible | yes
Previously, the command `omd cleanup` would show the following message.
```
2.3.0.cee Could not determine package. Keeping this version.
```
Werk 17082 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fixed another instance of hanging processes
key | value
---------- | ---
date | 2024-07-05T06:55:15+00:00
version | 2.3.0p11
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
As explained in werk [#17080](https://checkmk.com/werk/17080) the wrong conditions could lead to processes not releasing crucial file locks and the site subsequently freezing.
However, the werk did not address all the conditions.
With this werk, the cleanup of open resources was improved, which together with werk [#17081](https://checkmk.com/werk/17081) fixes another instance of processes not releasing their locks.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Fixed another instance of hanging processes
key | value
---------- | ---
date | 2024-07-05T06:55:15+00:00
version | 2.3.0p11
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
As explained in werk [#17080](https://checkmk.com/werk/17080) the wrong conditions could lead to processes not releasing crucial file locks and the site subsequently freezing.
However, the werk did not address all the conditions.
With this werk, the cleanup of open resources was improved, which together with werk [#17081](https://checkmk.com/werk/17081) fixes another instance of processes not releasing their locks.
+
[//]: # (werk v2)
# agent_netapp_ontap: fix SSL certificate verification
key | value
---------- | ---
date | 2024-07-10T14:47:31+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This werk impacts who monitors Netapp Filers.
Previously, the connection to the Netapp endpoint
was only possible by excluding the SSL certificate check.
This was because the agent used the endpoint's IP address instead of its hostname,
preventing certificate verification.
Now the agent validates the certificate by comparing the common name with the host name as known to Checkmk.
[//]: # (werk v2)
# pse_poe: Handle missing SNMP data
key | value
---------- | ---
date | 2024-07-10T09:53:43+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
If any of the OIDs used to monitor the power usage are missing, the check currently crashes with
```
ValueError (invalid literal for int() with base 10: '')
```
This has been changed so that the service is no longer discovered/will go to UNKNOWN if already present.