Werk 14049 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: cmk-agent-ctl: Agent controller can be disabled on Linux
Class: feature
Compatible: incomp
Component: agents
Date: 1652429684
Edition: cee
Knowledge: undoc
Level: 1
State: unknown
Version: 2.1.0b9
It was possible to disable agent controller in agent bakery for Windows.
Now, it's also possible for the Linux distributions.
Disabling the agent controller is not advised unless you experience
problems with it. In this case, the agent will work in legacy pull mode.
Please note: In the legacy pull mode, the transported data is not encrypted.
If you created a "Windows agent controller" rule previously in on one of
2.1.0b versions, you will have to create two new rules, Setup -> Agents ->
Windows, Linux, Solaris, AIX -> Agent rules -> Windows agent controller troubleshooting
and Setup -> Agents -> Windows, Linux, Solaris, AIX -> Agent rules -> Agent controller
to get the same behavior.
------------------------------------<diff>-------------------------------------------
Title: cmk-agent-ctl: Agent controller can be disabled on Linux
Class: feature
Compatible: incomp
Component: agents
Date: 1652429684
Edition: cee
Knowledge: undoc
Level: 1
State: unknown
- Version: 2.1.0
+ Version: 2.1.0b9
? ++
It was possible to disable agent controller in agent bakery for Windows.
Now, it's also possible for the Linux distributions.
Disabling the agent controller is not advised unless you experience
problems with it. In this case, the agent will work in legacy pull mode.
Please note: In the legacy pull mode, the transported data is not encrypted.
If you created a "Windows agent controller" rule previously in on one of
2.1.0b versions, you will have to create two new rules, Setup -> Agents ->
Windows, Linux, Solaris, AIX -> Agent rules -> Windows agent controller troubleshooting
and Setup -> Agents -> Windows, Linux, Solaris, AIX -> Agent rules -> Agent controller
to get the same behavior.
Werk 14101 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Add InfluxDB exporter
Class: feature
Compatible: compat
Component: wato
Date: 1650970100
Edition: cee
Knowledge: undoc
Level: 2
Version: 2.1.0b7
With Checkmk 2.1 we introduce the new option to configure InfluxDB connections.
With this option you are able to send metrics directly from Checkmk to the
REST-API of InfluxDB.
More information on how to configure the connection can be found here:
https://docs.checkmk.com/master/en/metrics_exporter.html
Please note:
The integration is only compatible with InfluxDB 2.0 or later.
If you're using InfluxDB <= 1.8 you need to use the option "Send metrics to
Graphite" as described in the Checkmk docs.
------------------------------------<diff>-------------------------------------------
Title: Add InfluxDB exporter
Class: feature
Compatible: compat
Component: wato
Date: 1650970100
Edition: cee
Knowledge: undoc
Level: 2
- Version: 2.1.0b1
? ^
+ Version: 2.1.0b7
? ^
With Checkmk 2.1 we introduce the new option to configure InfluxDB connections.
With this option you are able to send metrics directly from Checkmk to the
REST-API of InfluxDB.
More information on how to configure the connection can be found here:
https://docs.checkmk.com/master/en/metrics_exporter.html
Please note:
The integration is only compatible with InfluxDB 2.0 or later.
If you're using InfluxDB <= 1.8 you need to use the option "Send metrics to
Graphite" as described in the Checkmk docs.
Werk 13900 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Update Pillow and Paramiko
Class: security
Compatible: compat
Component: core
Date: 1650872232
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.1.0b6
This updates paramiko to 2.3.10 and Pillow to 9.1.0. These new versions include fixes for these CVEs:
LI: CVE-2022-24302
LI: CVE-2022-22817
LI: CVE-2022-22816
LI: CVE-2022-22815
LI: CVE-2022-24303
------------------------------------<diff>-------------------------------------------
Title: Update Pillow and Paramiko
Class: security
Compatible: compat
Component: core
Date: 1650872232
Edition: cre
Knowledge: doc
Level: 1
State: unknown
- Version: 2.1.0b7
? ^
+ Version: 2.1.0b6
? ^
This updates paramiko to 2.3.10 and Pillow to 9.1.0. These new versions include fixes for these CVEs:
LI: CVE-2022-24302
LI: CVE-2022-22817
LI: CVE-2022-22816
LI: CVE-2022-22815
LI: CVE-2022-24303
Werk 16299 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Fix inconsistent interaction for graphs in dashboards
Class: fix
Compatible: compat
Component: multisite
Date: 1700147621
Edition: cre
Level: 1
Version: 2.1.0p37
The mouse interaction (zooming, scrolling etc.) for graphs in dashboards only worked sporadically
and at seemingly random points.
------------------------------------<diff>-------------------------------------------
Title: Fix inconsistent interaction for graphs in dashboards
Class: fix
Compatible: compat
Component: multisite
Date: 1700147621
Edition: cre
Level: 1
- Version: 2.1.0p38
? ^
+ Version: 2.1.0p37
? ^
The mouse interaction (zooming, scrolling etc.) for graphs in dashboards only worked sporadically
and at seemingly random points.
Werk 14111 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Dynamic host management: Fix MKAPIError
Class: fix
Compatible: compat
Component: wato
Date: 1652680704
Edition: cee
Knowledge: doc
Level: 1
Version: 2.1.0
If the global option "Connection to the Web API" was changed, the error
"MKAPIError: {"title": "You need to be authenticated to use the REST API.",
"status": 401}" occurred.
------------------------------------<diff>-------------------------------------------
Title: Dynamic host management: Fix MKAPIError
Class: fix
Compatible: compat
Component: wato
Date: 1652680704
Edition: cee
Knowledge: doc
Level: 1
- Version: 2.1.0b010
? ----
+ Version: 2.1.0
If the global option "Connection to the Web API" was changed, the error
"MKAPIError: {"title": "You need to be authenticated to use the REST API.",
"status": 401}" occurred.
Title: mssql_availability_groups: Parsing of section failed
Class: fix
Compatible: compat
Component: checks
Date: 1722418114
Edition: cre
Level: 1
Version: 2.2.0p32
Provided with invalid lines `parse_mssql_availability_groups()` would crash with an exception
```
IndexError: list index out of range
```
Resulting in `Parsing of section mssql_availability_groups` error message in UI.
This change makes `parse_mssql_availability_groups()` resilient to those lines by just
ignoring them.
Werk 16009 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: HW/SW Inventory: Show icon and tooltip if a data field is kept further on or is outdated
Class: fix
Compatible: compat
Component: multisite
Date: 1701336085
Edition: cre
Level: 1
Version: 2.2.0p16
------------------------------------<diff>-------------------------------------------
Title: HW/SW Inventory: Show icon and tooltip if a data field is kept further on or is outdated
Class: fix
Compatible: compat
Component: multisite
Date: 1701336085
Edition: cre
Level: 1
- Version: 2.2.0p17
? ^
+ Version: 2.2.0p16
? ^
-
Werk 16431 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: omd restore: Fix RuntimeError: Failed to determine site version
Class: fix
Compatible: compat
Component: omd
Date: 1718107423
Edition: cre
Level: 1
Version: 2.2.0p29
Due to a regression introduced by <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the
command `omd restore <NEW_SITE> <ARCHIVE_PATH>` could fail:
C+:
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/main.py", line 3522, in _restore_backup_from_tar
old_site.replacements(),
^^^^^^^^^^^^^^^^^^^^^^^
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/contexts.py", line 136, in replacements
raise RuntimeError("Failed to determine site version")
C-:
The failure only occured, if the user provided a site name, which differed from the original name,
and the original site did no longer exist. This crash also affected the `Migrate existing Site`
function of the appliance.
If you are affected by this crash, but are unable to update, then you can start be restoring the
site without a new name. The site can then be renamed with `omd mv`.
------------------------------------<diff>-------------------------------------------
Title: omd restore: Fix RuntimeError: Failed to determine site version
Class: fix
Compatible: compat
Component: omd
Date: 1718107423
Edition: cre
Level: 1
- Version: 2.2.0p32
? -
+ Version: 2.2.0p29
? +
Due to a regression introduced by <a href="https://checkmk.com/werk/16422">Werk #16422</a>, the
command `omd restore <NEW_SITE> <ARCHIVE_PATH>` could fail:
C+:
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/main.py", line 3522, in _restore_backup_from_tar
old_site.replacements(),
^^^^^^^^^^^^^^^^^^^^^^^
File "/omd/versions/2.3.0p6.cee/lib/python3/omdlib/contexts.py", line 136, in replacements
raise RuntimeError("Failed to determine site version")
C-:
The failure only occured, if the user provided a site name, which differed from the original name,
and the original site did no longer exist. This crash also affected the `Migrate existing Site`
function of the appliance.
If you are affected by this crash, but are unable to update, then you can start be restoring the
site without a new name. The site can then be renamed with `omd mv`.
Werk 16228 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Enable update as site user due incompatible python versions
Class: fix
Compatible: compat
Component: omd
Date: 1699525492
Edition: cre
Knowledge: doc
Level: 1
Version: 2.2.0p15
This werk is relevant for you in case you've been using <tt>omd -V {version} update</tt> as site user.
Due to the update of the Python version from 3.11.2 to 3.11.5 with 2.2.0p13, we needed to introduce a fix in order to avoid the following issue:
C+:
Traceback (most recent call last):
File "/omd/versions/2.2.0p13.cee/bin/omd", line 60, in <module>
import omdlib.main
File "/omd/versions/2.2.0p13.cee/lib/python3/omdlib/main.py", line 36, in <module>
import random
File "/omd/versions/2.2.0p13.cee/lib/python3.11/random.py", line 49, in <module>
from math import log as _log, exp as _exp, pi as _pi, e as _e, ceil as _ceil
ImportError: /omd/versions/2.2.0p13.cee/lib/python3.11/lib-dynload/math.cpython-311-x86_64-linux-gnu.so: undefined symbol: _PyModule_Add
C-:
However, this fix introduced another issue with the release of 2.2.0p13, that's why we had to withdraw 2.2.0p13 and release 2.2.0p14 which addressed both issues.
------------------------------------<diff>-------------------------------------------
Title: Enable update as site user due incompatible python versions
Class: fix
Compatible: compat
Component: omd
Date: 1699525492
Edition: cre
Knowledge: doc
Level: 1
- Version: 2.2.0p14
? ^
+ Version: 2.2.0p15
? ^
This werk is relevant for you in case you've been using <tt>omd -V {version} update</tt> as site user.
Due to the update of the Python version from 3.11.2 to 3.11.5 with 2.2.0p13, we needed to introduce a fix in order to avoid the following issue:
C+:
Traceback (most recent call last):
File "/omd/versions/2.2.0p13.cee/bin/omd", line 60, in <module>
import omdlib.main
File "/omd/versions/2.2.0p13.cee/lib/python3/omdlib/main.py", line 36, in <module>
import random
File "/omd/versions/2.2.0p13.cee/lib/python3.11/random.py", line 49, in <module>
from math import log as _log, exp as _exp, pi as _pi, e as _e, ceil as _ceil
ImportError: /omd/versions/2.2.0p13.cee/lib/python3.11/lib-dynload/math.cpython-311-x86_64-linux-gnu.so: undefined symbol: _PyModule_Add
C-:
However, this fix introduced another issue with the release of 2.2.0p13, that's why we had to withdraw 2.2.0p13 and release 2.2.0p14 which addressed both issues.
Werk 16453 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Fix failed expiration date check while license verification
Class: fix
Compatible: compat
Component: wato
Date: 1709130387
Edition: cce
Level: 1
Version: 2.2.0p26
If you encounter "[Error] Certificate is expired" on the licensing page please
run verification again.
------------------------------------<diff>-------------------------------------------
Title: Fix failed expiration date check while license verification
Class: fix
Compatible: compat
Component: wato
Date: 1709130387
Edition: cce
Level: 1
- Version: 2.2.0p23
? ^
+ Version: 2.2.0p26
? ^
If you encounter "[Error] Certificate is expired" on the licensing page please
run verification again.