Checkmk werks level1 January 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
231 discussions

[2.3.0] Checkmk Werk 16147 created: Abort CMC on irrecoverable filesystem errors

by Checkmk werks level 1

[//]: # (werk v2) # Abort CMC on irrecoverable filesystem errors key | value ---------- | --- date | 2024-01-03T15:27:33+00:00 version | 2.3.0b1 class | fix edition | cee component | cmc level | 1 compatible | yes The errors * too many files open (EMFILE) * too many files open in system (ENFILE) * no buffer space (ENOBUFS) * not enough memory (ENOMEM) now exit the core. Correct monitoring cannot be guaranteed when the server is in this state.

8 months, 1 week

[2.3.0] Checkmk Werk 16194 created: Licensing: Allow UI to be used in trial and free state when CMC is not running

by Checkmk werks level 1

[//]: # (werk v2) # Licensing: Allow UI to be used in trial and free state when CMC is not running key | value ---------- | --- date | 2024-01-08T12:25:13+00:00 version | 2.3.0b1 class | fix edition | cce component | wato level | 1 compatible | yes When using a CCE in the trial phase or in the free license state, the UI was mostly unusable when the CMC was not running (with the pages showing the error "Cannot connect to 'unix:/omd/sites/monitoring_eval/tmp/run/live'....") Since the CMC is prohibited from starting if too many services are being monitored in the free license state, this meant that in order to get out of the free state, the license could only be applied via REST-API. This has now been fixed.

8 months, 1 week

[2.3.0] Checkmk Werk 16012 created: Event Console: Fix events on central site if these events are dedicated for remote sites

by Checkmk werks level 1

Title: Event Console: Fix events on central site if these events are dedicated for remote sites Class: fix Compatible: compat Component: ec Date: 1702905058 Edition: cre Level: 1 Version: 2.3.0b1

8 months, 1 week

[2.3.0] Checkmk Werk 16164 adapted: veeam_cdp_jobs: Handle last sync time from the future

by Checkmk werks level 1

Werk 16164 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # veeam_cdp_jobs: Handle last sync time from the future key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2023-12-29T08:24:59+00:00 level | 1 class | fix component | checks edition | cre Previously, the veeam_cdp_jobs would crash when receiving last sync time from the future with a message: ``` raise ValueError("Cannot render negative timespan") ``` Now, the affected service will be in state WARN and report the following message: ``` "The timestamp of the file is in the future. Please investigate your host times" ``` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # veeam_cdp_jobs: Handle last sync time from the future key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2023-12-29T08:24:59+00:00 level | 1 class | fix component | checks edition | cre Previously, the veeam_cdp_jobs would crash when receiving last sync time from the future with a message: ``` raise ValueError("Cannot render negative timespan") ``` - Now, the time since the last job run will be 0 for such cases. + Now, the affected service will be in state WARN and report the following message: + ``` + "The timestamp of the file is in the future. Please investigate your host times" + ```

8 months, 1 week

[2.1.0] Checkmk Werk 16274 adapted: Unusable services for "HPE Proliant Servers: Raid Status"

by Checkmk werks level 1

Werk 16274 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Unusable services for "HPE Proliant Servers: Raid Status" Class: fix Compatible: incomp Component: checks Date: 1702636533 Edition: cre Level: 1 Version: 2.1.0p38 This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affecs you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send <tt>"\x00"</tt> (the null-byte) as their name (OID .1.3.6.1.4.1.232.3.2.3.1.1.14). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. We now replace all null-bytes with <tt>"\\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitring history by running C+: sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* C-: ------------------------------------<diff>------------------------------------------- Title: Unusable services for "HPE Proliant Servers: Raid Status" Class: fix Compatible: incomp Component: checks Date: 1702636533 Edition: cre Level: 1 Version: 2.1.0p38 This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affecs you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send <tt>"\x00"</tt> (the null-byte) as their name (OID .1.3.6.1.4.1.232.3.2.3.1.1.14). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. - We now replace all null-bytes with <tt>"\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). + We now replace all null-bytes with <tt>"\\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). ? + As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitring history by running C+: sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* C-:

8 months, 2 weeks

[2.2.0] Checkmk Werk 16274 adapted: Unusable services for "HPE Proliant Servers: Raid Status"

by Checkmk werks level 1

Werk 16274 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Unusable services for "HPE Proliant Servers: Raid Status" Class: fix Compatible: incomp Component: checks Date: 1702636533 Edition: cre Level: 1 Version: 2.2.0p18 This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affecs you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send <tt>"\x00"</tt> (the null-byte) as their name (OID .1.3.6.1.4.1.232.3.2.3.1.1.14). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. We now replace all null-bytes with <tt>"\\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitring history by running C+: sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* C-: ------------------------------------<diff>------------------------------------------- Title: Unusable services for "HPE Proliant Servers: Raid Status" Class: fix Compatible: incomp Component: checks Date: 1702636533 Edition: cre Level: 1 Version: 2.2.0p18 This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affecs you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send <tt>"\x00"</tt> (the null-byte) as their name (OID .1.3.6.1.4.1.232.3.2.3.1.1.14). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. - We now replace all null-bytes with <tt>"\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). + We now replace all null-bytes with <tt>"\\x00"</tt> (the literal containing the four characters backslash, 'x', 'zero', 'zero'). ? + As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitring history by running C+: sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* C-:

8 months, 2 weeks

[2.3.0] Checkmk Werk 16168 created: fortiauthenticator_auth_fail: Detect new FortiAuthenticator devices

by Checkmk werks level 1

[//]: # (werk v2) # fortiauthenticator_auth_fail: Detect new FortiAuthenticator devices key | value ---------- | --- date | 2024-01-05T13:30:46+00:00 version | 2.3.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Additional FortiAuthenticator devices with SysObjectID starting with ".1.3.6.1.4.1.12356.113" are now detected.

8 months, 2 weeks

[2.3.0] Checkmk Werk 16274 adapted: Unusable services for "HPE Proliant Servers: Raid Status"

by Checkmk werks level 1

Werk 16274 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Unusable services for "HPE Proliant Servers: Raid Status" key | value --- | --- compatible | no version | 2.3.0b1 date | 2023-12-15T10:35:33+00:00 level | 1 class | fix component | checks edition | cre This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero'). As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitoring history by running ``` sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* ``` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Unusable services for "HPE Proliant Servers: Raid Status" key | value --- | --- compatible | no version | 2.3.0b1 date | 2023-12-15T10:35:33+00:00 level | 1 class | fix component | checks edition | cre This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. - We observed some devices to send `""` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`). + We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`). ? ++++ Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. - We now replace all null-bytes with `"\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero'). + We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero'). ? + As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitoring history by running ``` - sed -i 's||\x00|' var/check_mk/core/history var/check_mk/core/archive/* ? - + sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* ? ++++++ ```

8 months, 2 weeks

[2.1.0] Checkmk Werk 16307 created: Validate empty settings for "Maximum long output size"

by Checkmk werks level 1

Title: Validate empty settings for "Maximum long output size" Class: fix Compatible: compat Component: wato Date: 1692626179 Edition: cre Knowledge: undoc Level: 1 Version: 2.1.0p38 It was possible to unset the settings for the global option "Maximum long output size" leading to an error on activating of changes.

8 months, 2 weeks

[2.1.0] Checkmk Werk 16306 created: Fix PDF export of host- and servicegroup views

by Checkmk werks level 1

Title: Fix PDF export of host- and servicegroup views Class: fix Compatible: compat Component: reporting Date: 1704188131 Edition: cee Level: 1 Version: 2.1.0p38 If you exported a view with host- or servicegroup context, an error like "Error while rendering element type" was shown because of missing context information.

8 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 January 2024