Title: Hanging background jobs/frozen site
Class: fix
Compatible: compat
Component: multisite
Date: 1719405900
Edition: cee
Level: 1
Version: 2.2.0p28
Background jobs could previously hang without ever finishing under the wrong conditions. This could lead to the entire site freezing if the job had acquired crucial file locks (i.e. a lock on licensing files).
This is usually accompanied by the error
C+:
Bad file descriptor
C-:
in the logs.
Title: Fix regex error when using global flags when matching multiple expressions
Class: fix
Compatible: compat
Component: wato
Date: 1718966795
Edition: cre
Level: 1
Version: 2.2.0p28
There are a few places where we concatenate multiple regular expressions
to save performance. This concatenation broke when expressions using
global flags such as "(?i)cpu" were concatenated. With this werk, we are
converting these global flags to local ones for that specific expression
which restores the expected behavior of the expression, fixing various
crashes that would occur for example when updating or activating
changes.
[//]: # (werk v2)
# Add option to change the maximum response size for livestatus
key | value
---------- | ---
date | 2024-06-26T11:51:44+00:00
version | 2.3.0p8
class | feature
edition | cee
component | core
level | 1
compatible | yes
We add a new option in WATO under General > Global settings > Monitoring core to
set the maximum livestatus response time for CMC.
Note, however, that setting this value too high may result in out-of-memory
errors or timeout on the livestatus sockets. Use with care.
[//]: # (werk v2)
# Fix regex error when using global flags when matching multiple expressions
key | value
---------- | ---
date | 2024-06-21T10:46:35+00:00
version | 2.3.0p8
class | fix
edition | cre
component | wato
level | 1
compatible | yes
There are a few places where we concatenate multiple regular expressions
to save performance. This concatenation broke when expressions using
global flags such as "(?i)cpu" were concatenated. With this werk, we are
converting these global flags to local ones for that specific expression
which restores the expected behavior of the expression, fixing various
crashes that would occur for example when updating or activating
changes.
[//]: # (werk v2)
# HW/SW Inventory: 'Show internal tree paths' is now available in history view
key | value
---------- | ---
date | 2024-06-26T14:22:31+00:00
version | 2.4.0b1
class | feature
edition | cre
component | multisite
level | 1
compatible | yes
[//]: # (werk v2)
# Add option to change the maximum response size for livestatus
key | value
---------- | ---
date | 2024-06-26T11:51:44+00:00
version | 2.4.0b1
class | feature
edition | cee
component | core
level | 1
compatible | yes
We add a new option in WATO under General > Global settings > Monitoring core to
set the maximum livestatus response time for CMC.
Note, however, that setting this value too high may result in out-of-memory
errors or timeout on the livestatus sockets. Use with care.
[//]: # (werk v2)
# Fix regex error when using global flags when matching multiple expressions
key | value
---------- | ---
date | 2024-06-21T10:46:35+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
There are a few places where we concatenate multiple regular expressions
to save performance. This concatenation broke when expressions using
global flags such as "(?i)cpu" were concatenated. With this werk, we are
converting these global flags to local ones for that specific expression
which restores the expected behavior of the expression, fixing various
crashes that would occur for example when updating or activating
changes.
Title: Graphs with legend in dashboards: Avoid crash if dashlet is too short to contain graph
Class: fix
Compatible: compat
Component: multisite
Date: 1719486107
Edition: cre
Level: 1
Version: 2.2.0p28
Graph dashlets with activated legend crashed if the dashlet was too short to contain the graph. As
of this werk, the UI instead displays a helpful error message in such cases, hinting the user at
either increasing the dashlet height or disabling the legend.
[//]: # (werk v2)
# Graphs with legend in dashboards: Avoid crash if dashlet is too short to contain graph
key | value
---------- | ---
date | 2024-06-27T11:01:47+00:00
version | 2.3.0p8
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
Graph dashlets with activated legend crashed if the dashlet was too short to contain the graph. As
of this werk, the UI instead displays a helpful error message in such cases, hinting the user at
either increasing the dashlet height or disabling the legend.
[//]: # (werk v2)
# Enable several host actions no matter the tree depth of existing hosts
key | value
---------- | ---
date | 2024-06-24T11:19:49+00:00
version | 2.3.0p8
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
This Werk fixes the previous [Werk #16638](https://checkmk.com/werk/16638).
For host actions "Run bulk service discovery", "Rename multiple hosts" and "Detect network parent hosts" only hosts in the current folder and in the first level subfolders were taken into account.
This is fixed to the expected recursive behavior: If a host exists in the current folder or any of its subfolders - no matter their tree depth - the host actions are enabled.