[//]: # (werk v2)
# Dashboards and graph collections: Fix "There is no graph template with the id 'commit_charge'"
key | value
---------- | ---
date | 2024-10-31T08:08:54+00:00
version | 2.3.0p20
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The error message mentioned above was raised by certain combined graphs in dashboards and graph
collections. Furthermore, this werk also fixes certain empty template graphs in dashboards and
graph collections.
[//]: # (werk v2)
# oracle_performance: character string buffer too small
key | value
---------- | ---
date | 2024-10-30T13:41:07+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
In the past it was possible to see `PL/SQL: numeric or value error: character
string buffer too small` if a PDB name was longer than 11 characters. No memory
performance was available in this case.
This limit was now lifted, it's now possible to use the full length of 128
characters for PDB names. This is the limit for PDB names defined by oracle.
Title: Crash in during HW/SW inventory on Windows
Class: fix
Compatible: compat
Component: checks
Date: 1728416670
Edition: cre
Level: 1
Version: 2.2.0p36
This fixes a crash in case software package names contained a pipe character (<code>|</code>).
Affected users need to redeploy the Checkmk agent.
Werk 17196 was deleted. The following Werk is no longer relevant.
Title: Crash in during HW/SW inventory on Windows
Class: fix
Compatible: compat
Component: checks
Date: 1728416670
Edition: cre
Level: 1
Version: 2.2.0p36
This fixes a crash in case software package names contained a pipe character (<code>|</code>).
Affected users need to redeploy the Checkmk agent.
[//]: # (werk v2)
# Catch invalid "Explicit hosts" condition on save instead of crashing
key | value
---------- | ---
date | 2024-10-28T11:23:18+00:00
version | 2.3.0p20
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When invalid host names were passed into the "Explicit hosts" condition
while creating or editing a rule, Checkmk would crash with the message
`Internal error: Invalid hostaddress: '{explicit hosts condition}'.
With this werk, the form will warn you that you have entered an invalid
*Explicit hosts* condition. This allows you to fix the error without
losing the rest of the entered inputs.
[//]: # (werk v2)
# Crash in during HW/SW inventory on Windows
key | value
---------- | ---
date | 2024-10-08T19:44:30+00:00
version | 2.3.0p20
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a crash in case software package names contained a pipe character (`|`).
Affected users need to redeploy the Checkmk agent.
Werk 17196 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# Crash in during HW/SW inventory on Windows
key | value
---------- | ---
date | 2024-10-08T19:44:30+00:00
version | 2.3.0p20
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a crash in case software package names contained a pipe character (`|`).
Affected users need to redeploy the Checkmk agent.
[//]: # (werk v2)
# if64: Use Uptime instead of Check Time
key | value
---------- | ---
date | 2024-09-23T08:36:11+00:00
version | 2.3.0p20
class | fix
edition | cre
component | checks
level | 2
compatible | yes
The check plugin `if64` monitors network interfaces via SNMP.
The plugin reports a number of rates, e.g. `Input octets` and `Output packets`.
In the past, these rates were computed by using the time the check function is being run.
However, the SNMP output is always older, and the check time does not accurately reflect the age of the counters inside the SNMP output.
These inaccuracies were especially noticeable for clustered services.
With this Werk, the rates are based on `sysUpTime`, i.e., the time since the network management portion of the system was last re-initialized.
If the system is re-intialized, or `sysUpTime` overflows, no rates are reported, but the state remains OK.
The check will report 'time anomaly detected'.
[//]: # (werk v2)
# Catch invalid "Explicit hosts" condition on save instead of crashing
key | value
---------- | ---
date | 2024-10-28T11:23:18+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When invalid host names were passed into the "Explicit hosts" condition
while creating or editing a rule, Checkmk would crash with the message
`Internal error: Invalid hostaddress: '{explicit hosts condition}'.
With this werk, the form will warn you that you have entered an invalid
*Explicit hosts* condition. This allows you to fix the error without
losing the rest of the entered inputs.
[//]: # (werk v2)
# Crash in during HW/SW inventory on Windows
key | value
---------- | ---
date | 2024-10-08T19:44:30+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a crash in case software package names contained a pipe character (`|`).
Affected users need to redeploy the Checkmk agent.