Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

[2.3.0] Checkmk Werk 16508 created: Make LDAP connection test errors more explicit

by Checkmk werks level 1

[//]: # (werk v2) # Make LDAP connection test errors more explicit key | value ---------- | --- compatible | yes version | 2.3.0b3 date | 2024-03-07T16:34:41+00:00 level | 1 class | feature component | wato edition | cre The LDAP connection test does not give enough information about which DN configured results in an error. This werk adds identifying information for the DN to the error message to make it easier to identify the problem.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16458 created: Cisco Meraki: Add new check plugin for power supplies

by Checkmk werks level 1

[//]: # (werk v2) # Cisco Meraki: Add new check plugin for power supplies key | value ---------- | --- date | 2024-03-13T15:51:47+00:00 version | 2.3.0b3 class | feature edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16459 created: Cisco Meraki: Levels for last reported time of devices is now configurable

by Checkmk werks level 1

[//]: # (werk v2) # Cisco Meraki: Levels for last reported time of devices is now configurable key | value ---------- | --- date | 2024-03-13T15:52:30+00:00 version | 2.3.0b3 class | feature edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16550 created: Linux remote alert handlers not running under non-root user

by Checkmk werks level 1

[//]: # (werk v2) # Linux remote alert handlers not running under non-root user key | value ---------- | --- date | 2024-03-12T09:14:38+00:00 version | 2.3.0b3 class | fix edition | cee component | agents level | 1 compatible | yes In the ruleset *Remote alert handlers (Linux)*, you have to specify a user under that the remote alert handler will be executed on agent side. This user is set to *root* by default, but it's possible to choose an arbitrary user. But, when choosing a non-root user, the alert handlers previously failed to execute, because the handler files got deployed with root-ownership and were not readable by others. To fix the problem, the ownership of the files now get changed to the specified user. Security note: In general, it's important that all internal files of the Checkmk agent have root ownership, as they might be read/executed by the Checkmk agent under root. However, this is not the case for remote alert handlers, as they always get executed under the specified user. As an additional security measure, the dispatcher on agent side checks the ownership of installed remote alert handlers, and refuses to execute non-root owned handlers when called via SSH with root rights.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16614 created: Ignore CAs with negative serial numbers

by Checkmk werks level 1

[//]: # (werk v2) # Ignore CAs with negative serial numbers key | value ---------- | --- date | 2024-03-11T10:43:27+00:00 version | 2.3.0b3 class | fix edition | cre component | core level | 1 compatible | no When Checkmk is configured to *Trust system wide configured CAs* the system CA store is traversed and the certificates are added to the trusted CAs. With RFC 5280 certificate serial numbers are required to be positive. Unfortunately there are CA certificates out from before this RFC and the might contain negative serial numbers. One we encountered several times while testing is: commonName = EC-ACC organizationalUnitName = Jerarquia Entitats de Certificacio Catalanes organizationalUnitName = Vegeu https://www.catcert.net/verarrel (c)03 organizationalUnitName = Serveis Publics de Certificacio organizationName = Agencia Catalana de Certificacio (NIF Q-0801176-I) countryName = ES Our underlying library we use for handling certificates announced to no longer support certificates with negative serial numbers in one of the next versions. Therefore we decided to ignore certificates with negative serial numbers so we can update this library during the lifetime of this Checkmk release without changing this behaviour. Since the mentioned `EC-ACC` certificate was encountered multiple times during testing and is not widely used the fact that this certificate was encountered and is ignored is NOT logged. If you use certificates issued by CA certificates with negative serial numbers you can add them manually to your list of trusted certificates via the UI. This might cause warnings appearing in console outputs and in logfiles and may stop to work in the future.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16486 created: Change default setting for usage to use community translated languages

by Checkmk werks level 1

[//]: # (werk v2) # Change default setting for usage to use community translated languages key | value ---------- | --- date | 2024-03-13T14:44:24+00:00 version | 2.3.0b3 class | feature edition | cre component | multisite level | 1 compatible | yes The default setting for "Enable community translated languages" was previously disabled. It is now enabled by default. The names of the community translated languages have also been changed.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16599 created: jolokia metrics: restores 'default product' behavior

by Checkmk werks level 1

[//]: # (werk v2) # jolokia metrics: restores 'default product' behavior key | value ---------- | --- date | 2024-03-11T13:50:14+00:00 version | 2.3.0b3 class | fix edition | cre component | checks level | 1 compatible | yes The check plugin no longer showed any metrics if a product was not specified in the ruleset configuration. This werk restores the original behaviour, using as a default product the one reported in the info section of the agent output.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16050 created: Change default OS dashboards "Linux hosts" and "Windows hosts"

by Checkmk werks level 1

[//]: # (werk v2) # Change default OS dashboards "Linux hosts" and "Windows hosts" key | value ---------- | --- date | 2024-03-12T07:58:50+00:00 version | 2.3.0b3 class | feature edition | cee component | multisite level | 1 compatible | yes We change the default dashboards "Linux hosts" and "Windows hosts" (Monitor > Overview) to a new layout and partly to new dashboard elements. This change shall improve user experience and provide the most relevant Linux/Windows host information on these boards.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16639 created: Ruleset API: Help text for SimpleLevels, Levels

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: Help text for SimpleLevels, Levels key | value ---------- | --- date | 2024-03-13T09:20:05+00:00 version | 2.3.0b3 class | fix edition | cre component | checks level | 1 compatible | yes Previously the help text configured for SimpleLevels and Levels was not shown in the UI, this is now fixed.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16410 created: omd update: Fix Aborting in Docker Container

by Checkmk werks level 1

[//]: # (werk v2) # omd update: Fix Aborting in Docker Container key | value ---------- | --- date | 2024-03-12T15:30:46+00:00 version | 2.3.0b3 class | fix edition | cre component | omd level | 1 compatible | yes This bug affects users of the 2.3.0 beta. In Werk #16408 a mechanism was introduced to restore a site after an aborted update. If this mechanism triggered inside a docker container, then the site may be in an inconsistent state. Any further update will show the following error. ``` FileNotFoundError: [Errno 2] No such file or directory: '/omd/versions/2.3.0b1.cee/share/omd/skel.permissions' ``` You can check whether you are affected by this issue by comparing the output of `omd update` and `cat "${OMD_ROOT}"/.version_meta/version`. If the versions do not match, then you are affected by this issue. This Werk fixes the update procedure. In case you are affected, you can delete `.version_meta` and upgrade to the version which is shown by `omd update`.

3 months, 3 weeks

← Newer
1
...
32
33
34
35
36
37
38
...
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024