Checkmk werks level2 June 2014

checkmk-werks-lvl2@lists.checkmk.com

4 participants
22 discussions

Check_MK Werk 0973: Renaming of hosts via WATO

by Mathias Kettner

ID: 0973 Title: Renaming of hosts via WATO Component: WATO Level: 2 Class: New Feature Version: 1.2.5i3 WATO has now a new function Rename Host. You will find a button with that name in the Properties of a host. It allows a renaming of an existing host. Before you can use that feature you need to have all changes activated, so nothing is pending. Renaming a host is a complex precedure that will not only rename the host in WATO, but also in: <ul> <li>all rules from Host & Service Parameters</li> <li>cluster's node definitions</li> <li>a host's parent definitions</li> <li>Business Intelligence rules</li> <li>notification rules (both rule based and flexible notifications)</li> <li>internal Check_MK data like caches and performance counters</li> <li>auto-disovered services of the host</li> <li>logfile information of logwatch plugin</li> <li>stored SNMP walks</li> <li>RR databases with performance data</li> <li>RRD updates in journal of RRD Cache</li> <li>spool files of PNP4Nagios</li> <li>NagVis maps</li> <li>monitoring history entries (events and availability)</li> <li>the current monitoring state (including ackowledgements and downtimes)</li> </ul> Please note that renaming of a host involves a temporary stop of the monitoring core. This is neccessary in order to avoid situation where the old and the new name of a host is being used at the same time.

8 years, 9 months

Check_MK Werk 1035: Do not fail on errors in *.mk files anymore - except in interactive mode

by Mathias Kettner

ID: 1035 Title: Do not fail on errors in *.mk files anymore - except in interactive mode Component: Core & Setup Level: 2 Class: Bug Fix Version: 1.2.5i5 If a syntax error in <tt>main.mk</tt> or other <tt>*.mk</tt> files occurs, Check_MK used to abort any operation. This is nasty when for example a new variable that has been introduced in a new version is not known in an older version of Check_MK and thus after a version downgrade the configuration cannot be activated any more. The behaviour has now changed so that in case of such an error Check_MK will only abort in interactive mode, i.e. if the standard output is a terminal. That means that WATO will always try to activate Changes. You can force the old behaviour by adding the new option <tt>--interactive</tt>.

10 years, 2 months

Check_MK Werk 1034: Always provide also 64 bit version of Windows agent

by Mathias Kettner

ID: 1034 Title: Always provide also 64 bit version of Windows agent Component: Checks & Agents Level: 2 Class: New Feature Version: 1.2.5i5

10 years, 2 months

Check_MK Werk 0946: hw/sw inventory: fixed display bug for byte fields with the value 0

by Andreas Boesl

ID: 0946 Title: hw/sw inventory: fixed display bug for byte fields with the value 0 Component: HW/SW-Inventory Level: 2 Class: Bug Fix Version: 1.2.5i5 There was an exception for fields represented in bytes when the value was set to 0.

10 years, 2 months

Check_MK Werk 1013: Sort host names naturally, e.g. foobar11 comes after foobar2

by Mathias Kettner

ID: 1013 Title: Sort host names naturally, e.g. foobar11 comes after foobar2 Component: Multisite Level: 2 Class: New Feature Version: 1.2.5i5 Hostnames are now sorted naturally. That means that sequences of numbers are being interpreted as numbers. This also works for host names that have the form of an IPv4 address, e.g. <tt>10.1.1.5</tt> is now correctly sorted before <tt>10.1.1.11</tt> and <tt>srv17_3</tt> comes before <tt>src17_108</tt>. This new sorting is implemented in the status GUI and also in WATO.

10 years, 2 months

Check_MK Werk 0945: Sidebar snapin "Problem hosts": Now excludes hosts and services in downtime

by Andreas Boesl

ID: 0945 Title: Sidebar snapin "Problem hosts": Now excludes hosts and services in downtime Component: Multisite Level: 2 Class: Bug Fix Version: 1.2.5i5

10 years, 2 months

Check_MK Werk 1012: Fix quoting of \ in custom checks with nagios core

by Mathias Kettner

ID: 1012 Title: Fix quoting of \ in custom checks with nagios core Component: Core & Setup Level: 2 Class: Incompatible Change Version: 1.2.5i5 When you are using Nagios as montitoring core then backslashes contained in <tt>custom_checks</tt> (Classical active and passive Nagios checks) would be interpreted by Nagios. That way single backslashes would usually vanish und you would have to duplicate them. The Check_MK Micro Core never interpreted these backslashes so it was transparent for the user. This fix changes the behaviour of Check_MK in a way that also with the Nagios core you need only one backslash. Backslashes are transparent now. NOTE: If you have custom checks that contain backslashes (for example as part of names or passwords) then you need to remove duplicate backslashes after this update!

10 years, 2 months

Check_MK Werk 0944: oracle_tablespaces: fixed calculation of space left and number of remaining increments

by Andreas Boesl

ID: 0944 Title: oracle_tablespaces: fixed calculation of space left and number of remaining increments Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.5i5 The remaining increments and space left was not correctly calculated when the remaining memory space was not a multiple of the increment size. For example: C+: Tablespace 900 MB used 100 MB free space for autoincrement 200 MB increment size C-: The previous version calculated 900 MB as maximum size, because the increment size was greater than the remaining autoincrement space. This was wrong. The last increment also uses the remaining space, even if the remaining size is smaller than the increment size. As a result, this fix actually increases the amount of available free space, so it should not have any negative side effects for already configured limits.

10 years, 2 months

Check_MK Werk 0943: if.include: fixed incorrect traffic percentage values in the check output of if checks

by Andreas Boesl

ID: 0943 Title: if.include: fixed incorrect traffic percentage values in the check output of if checks Component: Checks & Agents Level: 2 Class: Bug Fix Version: 1.2.5i5 There was a display bug in the traffic percentages. The value was off by factor 8. This bug didn't cause wrong check results or performance data values, just a visual glitch.

10 years, 2 months

Check_MK Werk 0984: Fix code injection for logged in users via automation url

by Lars Michelsen

ID: 0984 Title: Fix code injection for logged in users via automation url Component: WATO Level: 2 Class: Incompatible Change Version: 1.2.5i4 This fixes CVSS 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C. The description: The check_mk applications uses insecure API calls, which allow an attacker to execute arbitrary code on the server by issuing just a single URL. The reason for this is the usage of the insecure "pickle" API call. Apparently this was modified as a security means from a former version, which used "eval"-like structures with untrusted input data. Anyhow, as the python API documentation clearly state, "pickle" should be considered unsafe as well, see: <tt>https://docs.python.org/2/library/pickle.html</tt>. The fix replaces <tt>pickle<tt> with a module called <tt>ast</tt>. Unfortunately this module is not available on Centos/RedHat 5.X and Debian 5. On these systems WATO still uses <tt>pickle</tt>, even with this fix. Note: This change makes the current Check_MK versions incompatible to older versions. In a mixed environment with old and new Check_MK versions or with old and newer Python versions you have to force WATO to use the old unsafe method by setting <tt>wato_legacy_eval = True<tt> in <tt>multisite.mk</tt>. This can also be done with the new global WATO setting Use unsafe legacy encoding for distributed WATO.

10 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2 June 2014