Checkmk werks level1 May 2021

checkmk-werks-lvl1@lists.checkmk.com

21 participants
112 discussions

Checkmk Werk 12834: Do not fail on not existing time periods in "Check period for passive Check_MK services"

by Lars Michelsen

ID: 12834 Title: Do not fail on not existing time periods in "Check period for passive Check_MK services" Component: Core & setup Level: 1 Class: Bug fix Version: 2.0.0p5 When time periods are configured in the ruleset "Check period for passive Check_MK services", this made the cmc fail on start. The normal behaviour of Checkmk is to create a warning message like "WARNING: The cmc_passive_check_period "ding" used by service "old;Check_MK Discovery" does not exist, falling back to 24x7." and continue. This is done for all other time period references, but did not work for this specific option. The fallback has now also been added to this options.

3 years, 3 months

Checkmk Werk 12814: agent_aws(<tt>aws_ebs_limits</tt>): do not request public snapshots from marketplace

by Ulrich Bschorer

ID: 12814 Title: agent_aws(<tt>aws_ebs_limits</tt>): do not request public snapshots from marketplace Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 In previous versions the check <tt>aws_ebs_limits</tt> reported a wrong snapshot number, because even snapshots from the AWS marketplace were requested. This werk fixes the check <tt>aws_ebs_limits</tt> by appling a filter to the snapshot request. Furthermore, this fix also decreases the runtime of the agent, since considerably less snapshots are requested. In order to be able to monitor snapshots the "create volume permissions" are required for the monitoring AWS account.

3 years, 3 months

Checkmk Werk 12790: kubernetes: label empty endpoint_info

by Benedikt Seidl

ID: 12790 Title: kubernetes: label empty endpoint_info Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 Before this werk endpoint hosts where only labeled if there was at least some information about the endpoint available. This is problematic as the host is created anyway even if there is no information available. In order to prevent the problem described in werk #12782 the host label <tt>cmk/kubernetes:yes</tt> has to be available, so we need to label the host even if there is no information available.

3 years, 3 months

Checkmk Werk 12788: Kubernetes: agent: handle pending pods

by Benedikt Seidl

ID: 12788 Title: Kubernetes: agent: handle pending pods Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 Before this werk, the kubernetes special agent could not handle pods that are pending. The error message was: <tt>TypeError: '<' not supported between instances of 'NoneType' and 'str'</tt> This should now be fixed.

3 years, 3 months

Checkmk Werk 12779: inventory: solaris_pkginfo: failed: '<' not supported between instances of 'str' and 'NoneType'

by Benedikt Seidl

ID: 12779 Title: inventory: solaris_pkginfo: failed: '<' not supported between instances of 'str' and 'NoneType' Component: HW/SW Inventory Level: 1 Class: Bug fix Version: 2.1.0i1 The solaris_pkginfo inventory plugin was not working and showed the following message: WARNING: solaris_pkginfo: failed: '<' not supported between instances of 'str' and 'NoneType' This should now be fixed.

3 years, 3 months

Checkmk Werk 10246: omd backup: Made it more robust against rrdcached communication issues

by Ronny Bruska

ID: 10246 Title: omd backup: Made it more robust against rrdcached communication issues Component: Site Management Level: 1 Class: Bug fix Version: 2.1.0i1 The "omd backup" could be terminated during backup by issues of the rrdcached. The backup communicates with the rrdcached to pause updates to the RRD files to ensure the files are consistent during backup. In case the rrdcached is not answering as expected or a connection is not possible the backup should continue with the backup instead of failing.

3 years, 3 months

Checkmk Werk 12833: Fix logout of active user sessions when using multiple sessions

by Lars Michelsen

ID: 12833 Title: Fix logout of active user sessions when using multiple sessions Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0i1 Previous Checkmk 2.0 releases could logout an active login sessions of a user when the same user was used from multiple clients (e.g. different browsers, GUI, API, or nagstamon). This was caused by an invalid session cleanup mechanism. Background: With Checkmk 2.0 a new login sessions tracking was introduced. This session tracking allows up to 20 active login sessions for a single user. Once the 21st login session is opened, a cleanup mechanism is triggered which cleans up a) all sessions except the newest 20 sessions and b) all sessions which were inactive for 7 days. Instead of keeping the newest sessions, the it was keeping the oldest sessions which lead to the active sessions being logged out in the moment the cleanup was triggered.

3 years, 3 months

Checkmk Werk 12799: Raw Edition: Allow round brackets in service descriptions

by Lukas Lengler

ID: 12799 Title: Raw Edition: Allow round brackets in service descriptions Component: Core & setup Level: 1 Class: Bug fix Version: 2.1.0i1 The Checkmk Raw Edition now allows service descriptions to use round brackets. Previously this was inconsistent with the Checkmk Enterprise Editions and has now been consolidated. Services which were often affected by this issue were the logfiles monitored on Windows systems. When a path contains round brackets, the service description was not named as expected. Illegal characters for Nagios: `;~!$%^&*|\'"<>?,= Illegal character for CMC: \t

3 years, 3 months

Checkmk Werk 12893: qnap_disks: Warn if SMART status is not "GOOD"

by External contributor

ID: 12893 Title: qnap_disks: Warn if SMART status is not "GOOD" Component: Checks & agents Level: 1 Class: Bug fix Version: 2.1.0i1 The check returns {CRIT} in case of an error state reported by the device, and go to {WARN} if the SMART status is missing. Additionally the plugin will now go to {WARN} if the SMART status is not "GOOD".

3 years, 3 months

Checkmk Werk 12785: Fix "A negative value is not valid." in "Problem notification" Main Dashboard

by Benedikt Seidl

ID: 12785 Title: Fix "A negative value is not valid." in "Problem notification" Main Dashboard Component: Setup Level: 1 Class: Bug fix Version: 2.1.0i1 Chromium based browsers showed an error message in the developer tools: <tt>Error: <rect> attribute width: A negative value is not valid.</tt> This error was provoked by a broken windowing function in the python implementation and is now fixed. Furthermore the calculation of the windowing function was adapted: Before the first and last Bar was not a full sized window based on the current time. Now all time windows have the same duration.

3 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2021