[//]: # (werk v2)
# snmp: Fix error in SNMP context serialization
key | value
---------- | ---
date | 2024-06-28T10:44:57+00:00
version | 2.3.0p8
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Using SNMPv3 with contexts resulted in a CRIT Check_MK service and an error:
`[snmp] AttributeError("'tuple' object has no attribute 'section'")`.
[//]: # (werk v2)
# ICMP Echo Request (Ping): Off-by-one error in active check
key | value
---------- | ---
date | 2024-06-26T08:50:24+00:00
version | 2.3.0p8
class | fix
edition | cre
component | checks
level | 1
compatible | no
This fixes a regression in Checkmk version 2.3.
When using the setting _"Ping IP address identified by its index"_ of the plugin _ICMP Echo Request (Ping)_, the used address was off by one.
The fix is incompatible for users that have accounted for this error and changed their rule.
To avoid mistakes in the future, we've added a hint to the rule, and validate that the configured index is equal to or larger than 1.
[//]: # (werk v2)
# snmp: Fix error in SNMP context serialization
key | value
---------- | ---
date | 2024-06-28T10:44:57+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Using SNMPv3 with contexts resulted in a CRIT Check_MK service and an error:
`[snmp] AttributeError("'tuple' object has no attribute 'section'")`.
[//]: # (werk v2)
# ICMP Echo Request (Ping): Off-by-one error in active check
key | value
---------- | ---
date | 2024-06-26T08:50:24+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This fixes a regression in Checkmk version 2.3.
When using the setting _"Ping IP address identified by its index"_ of the plugin _ICMP Echo Request (Ping)_, the used address was off by one.
The fix is incompatible for users that have accounted for this error and changed their rule.
To avoid mistakes in the future, we've added a hint to the rule, and validate that the configured index is equal to or larger than 1.
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.