Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 8156: New option for forcing a history logfile rotation based on its size

by Lars Michelsen

ID: 8156 Title: New option for forcing a history logfile rotation based on its size Component: cmc Level: 2 Class: New feature Version: 1.2.7i1 The Check_MK Micro Core now forces a rotation of the history logfile if its size exceeds a configure limit. This avoids too large logfiles in situations with a high logging volume. Large logfile make problems in certain Livestatus queries. The default is now to force a rotation at a size of 20 MB. You can configure this limit within the bounds of 10 KB and 1 GB.

7 years, 7 months

Check_MK Werk 8134: Avoiding falsely reported packet loss by PING service

by Lars Michelsen

ID: 8134 Title: Avoiding falsely reported packet loss by PING service Component: cmc Level: 2 Class: Bug fix Version: 1.2.7i1 The PING services, which is being created for hosts which are not monitored via SNMP or agent, sometimes reported packet loss of x% while the host check of the microcore reported that the host is reachable without problems. This issue was caused by the way the Micro Core icmpsender generated the ICMP packages. These packages seemed to confuse the check_icmp plugin which is executed by the PING service.

7 years, 7 months

Check_MK Werk 8153: Fix notification delay if delay is greater than 2147 seconds

by Lars Michelsen

ID: 8153 Title: Fix notification delay if delay is greater than 2147 seconds Component: cmc Level: 2 Class: Bug fix Version: 1.2.7i1 If you configured a notification delay of more than 2147 seconds (approx 35 minutes, precisely 2^31 micro seconds) then due to an internal range overflow the actual delay would be somewhere between -2147 and +2147 seconds. So in some cases the delay was just too short, in other it was negative and that way totally ineffective. This has been fixed.

7 years, 7 months

Check_MK Werk 8128: Fix filedescriptor leak in CMC due to new error handling of check helpers

by Lars Michelsen

ID: 8128 Title: Fix filedescriptor leak in CMC due to new error handling of check helpers Component: cmc Level: 2 Class: Bug fix Version: 1.2.7i1

7 years, 7 months

Check_MK Werk 8129: Create log entries for acknowledgements in monitoring log

by Lars Michelsen

ID: 8129 Title: Create log entries for acknowledgements in monitoring log Component: cmc Level: 2 Class: New feature Version: 1.2.7i1 When an acknowledgement is being created or removed or an acknowledgement ends because of a state change or expires then now an entry in made in the monitoring log. Example: F+:var/check_mk/core/history [1420818703] HOST ACKNOWLEDGE ALERT: xyserver12;STARTED;omdadmin;Some comment... F-: These entries are visiable via Multisite and via Livestatus. This only works with the CMC.

7 years, 7 months

Check_MK Werk 8125: Fix invalid number of Alert statistics view when exported as PDF

by Lars Michelsen

ID: 8125 Title: Fix invalid number of Alert statistics view when exported as PDF Component: Reporting & Availability Level: 2 Class: Bug fix Version: 1.2.7i1 The reason was that internally a limit on the number of raw lines from the log query was imposed. This has been fixed.

7 years, 7 months

Check_MK Werk 8126: Agent bakery creates now tarball AIX agent (still no plugins)

by Lars Michelsen

ID: 8126 Title: Agent bakery creates now tarball AIX agent (still no plugins) Component: agents Level: 2 Class: New feature Version: 1.2.7i1

7 years, 7 months

Check_MK Werk 8123: Fix broken layout of host/service detail pages, add host details to example report

by Lars Michelsen

ID: 8123 Title: Fix broken layout of host/service detail pages, add host details to example report Component: Reporting & Availability Level: 2 Class: New feature Version: 1.2.7i1

7 years, 7 months

Check_MK Werk 8124: Avoid configuration changes to be become active without activate changes

by Lars Michelsen

ID: 8124 Title: Avoid configuration changes to be become active without activate changes Component: config Level: 2 Class: Bug fix Version: 1.2.7i1 The Check_MK keepalive mode, which is used for the Check_MK helpers and for the RRD creation helper, now uses a new method for reading the configuration from <tt>main.mk</tt>, the other <tt>*.mk</tt> files and the <tt>autochecks</tt>. This new method has two advantages: <ul> <li>Changes done to <tt>*.mk</tt> files can no longer become active unless they are activated. This even holds for core or server restarts and for crashed check helpers</li> <li>Check helpers and RRD helper do not any longer need to restart themselves after a configuration change but simply reload the changed configuration. This has a muss smaller CPU footprint when activating changes.</li> <li>Autochecks files are now only read for the host that is currently being delt with. This makes the internal check table much smaller and speeds configuration reloads.</li> </ul> The gross result is that configuration changes are now really automic and also faster. H2:Implementation details Whenever you create the configuration for the core (options <tt>-B</tt>, <tt>-O</tt>, <tt>-R</tt> or <tt>-U</tt> or Activate Changes via WATO) then the complete configuration (the result from parsing <tt>main.mk</tt> and friends) is written to the file <tt>var/check_mk/core/config.mk</tt>. The core then triggers the check helpers for configuration reload. The helpers simply re-read that file and are immediately up-to-date. At the same time copies (hard links) of the autochecks files in <tt>var/check_mk/autochecks</tt> are being created in <tt>var/check_mk/core/autochecks</tt>. These files are used during the monitoring. Note: The Discovery check (formerly known as Inventory check) does not use the activated configuration but still that one that is modified via WATO. That way after doing a service discovery the discovery check will immediately be happy - without a core restart. This is just as it used to be.

7 years, 7 months

Check_MK Werk 8118: Smartping: Fixed "no buffer space available" error when having a lot of hosts configured

by Lars Michelsen

ID: 8118 Title: Smartping: Fixed "no buffer space available" error when having a lot of hosts configured Component: cmc Level: 2 Class: Bug fix Version: 1.2.7i1 We already changed the way smartping was operating some time ago, this solved the "no buffer space available" problem for many systems and increased the possible number of hosts to be pinged dramatically. This did not fix the problem for all systems. Some systems with maybe slower network cards or drivers still had the problem that the message "no buffer space available" appeared from time to time in the cmc.log. This occured when the cmc was asking for ping requests faster than the kernel / NIC could process them. The send queue of the single raw socket was filling up to the maximum and then resulting in this error message. The icmpsender now opens 8 sockets instead of 1 for sending the ICMP requests. Additionally the socktes now get a larger send buffer to make it less likely to fill up.

7 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2