[//]: # (werk v2)
# Rittal temperature check regression
key | value
---------- | ---
date | 2024-06-14T11:21:23+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
You're affected if you're using rittal temperature checks under 2.3.0.
This regression exists since 2.3.0b1 and creates the following crash:
```
File "/omd/sites/YOURSITE/lib/python3/cmk/plugins/lib/temperature.py", line 319, in check_temperature
raise ValueError (Cannot compute trend. Either specify both variables 'unique_name' and 'value_store' or none.)
```
Title: cisco_temperature: Handle Invalid Device Readings
Class: fix
Compatible: compat
Component: checks
Date: 1718280849
Edition: cre
Level: 1
Version: 2.2.0p28
Cisco SNMP devices may report temperatures of "inf" or "-inf". According to
CISCO-ENTITY-SENSOR-MIB, these values are not valid.
Previously, Checkmk would treat non-finite temperatures as valid. This invalid
data would be written to <code>tmp/check_mk/counters/</code>, which then caused the
<code>Check_MK</code> service to become UNKNOWN. Furthermore, the services on the host
would become stale. With this Werk, the problematic values not persisted. Only
the affected service state will be UNKNOWN.
If you are affected, you can delete the corrupted counter file in
<code>tmp/check_mk/counters/<host name></code>. To fix the readings reported by your
device, please directly contact Cisco.
Title: Restart scheduler after setting "use the status of a service"
Class: fix
Compatible: compat
Component: core
Date: 1718288461
Edition: cee
Level: 1
Version: 2.2.0p28
This fixes the case where the default check scheduler would not restart after
the user temporarily set "use the status of service" as the "host check
command". The corresponding log entry was "refuse to schedule invalid jobhost
... at 1970-0101 ...".
Title: mkeventd: Forward to remote Event Console or Syslog server if configured
Class: fix
Compatible: compat
Component: notifications
Date: 1718284259
Edition: cre
Level: 1
Version: 2.2.0p28
The notification method "Forward notification to Event Console" offers the
option to forward messages to a remote Event Console or Syslog server.
In earlier versions the messages were only forwarded if the local Event Console
(mkeventd) was not running.
This has been fixed.
Title: Allow upload of Checkmk 2.3 compliant MKPs
Class: fix
Compatible: compat
Component: checks
Date: 1718184355
Edition: cre
Level: 1
Version: 2.2.0p28
Users where unable to upload MKPs containing files that are only relevant for Checkmk 2.3.
However, it should be possible to upload such MKPs in preperation for an upgrade.
[//]: # (werk v2)
# Rittal temperature check regression
key | value
---------- | ---
date | 2024-06-14T11:21:23+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
You're affected if you're using rittal temperature checks under 2.3.0.
This regression exists since 2.3.0b1 and creates the following crash:
```
File "/omd/sites/YOURSITE/lib/python3/cmk/plugins/lib/temperature.py", line 319, in check_temperature
raise ValueError (Cannot compute trend. Either specify both variables 'unique_name' and 'value_store' or none.)
```
[//]: # (werk v2)
# cisco_temperature: Handle Invalid Device Readings
key | value
---------- | ---
date | 2024-06-13T12:14:09+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Cisco SNMP devices may report temperatures of "inf" or "-inf". According to
CISCO-ENTITY-SENSOR-MIB, these values are not valid.
Previously, Checkmk would treat non-finite temperatures as valid. This invalid
data would be written to `tmp/check_mk/counters/`, which then caused the
`Check_MK` service to become UNKNOWN. Furthermore, the services on the host
would become stale. With this Werk, the problematic values not persisted. Only
the affected service state will be UNKNOWN.
If you are affected, you can delete the corrupted counter file in
`tmp/check_mk/counters/<host name>`. To fix the readings reported by your
device, please directly contact Cisco.