[//]: # (werk v2)
# time_periods: Fix timeperiod iCalendar (ics) import
key | value
---------- | ---
date | 2024-04-17T09:19:29+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
This Werk solves a problem with importing events that take more than
one day. Before this Werk, only the first day of the event was
imported. Now all days involved are imported.
[//]: # (werk v2)
# mk_postgres.py: Add 'PG_BINARY_PATH' to Bakery Rule
key | value
---------- | ---
date | 2024-04-16T15:15:06+00:00
version | 2.4.0b1
class | feature
edition | cee
component | agents
level | 1
compatible | yes
[Werk #15619](https://checkmk.com/werk/15619) added support for reading `PG_BINARY_PATH` from
`postgres.cfg`. This Werk allows setting this value with the agent bakery.
[//]: # (werk v2)
# Inventory: Add Windows support for Hardware > System > Uuid
key | value
---------- | ---
date | 2024-04-16T13:09:47+00:00
version | 2.4.0b1
class | feature
edition | cre
component | inv
level | 1
compatible | yes
This element is already available for Linux, now the windows agent also supports
reading this value.
You have to update `mk_inventory.vbs` on the monitored host, to provide the
necessary data.
[//]: # (werk v2)
# postgres_stat_database_size: Don't discover 'access_to_shared_objects'
key | value
---------- | ---
date | 2024-04-16T07:10:21+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
Checkmk discovered Services like "PostgreSQL DB MAIN/access_to_shared_objects
Size" but the Services only showed "Database size not available" and a WARN
status.
Those Services are no longer discovered.
Werk 16606 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# agent_netapp_ontap: handle shelves without elements
key | value
---------- | ---
date | 2024-04-10T12:26:35+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The agent did not handle the cases where shelves had no fans, temperature sensors or PSUs.
This led to crashes during the agent execution.
With this werk we now correctly handle these scenarios and the corresponding services are not discovered if no items are found.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# agent_netapp_ontap: handle shelves without elements
key | value
---------- | ---
date | 2024-04-10T12:26:35+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The agent did not handle the cases where shelves had no fans, temperature sensors or PSUs.
This led to crashes during the agent execution.
- With this werk we know correctly handle these scenarios and the corresponding services are not discovered if no items are found.
? -
+ With this werk we now correctly handle these scenarios and the corresponding services are not discovered if no items are found.
[//]: # (werk v2)
# Just show an error message if redis is not reachable
key | value
---------- | ---
date | 2024-04-17T06:14:37+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The mega menu search produced a crash report if redis was not reachable.
Now only an error message is shown.
[//]: # (werk v2)
# agent_netapp_ontap: handle shelves without elements
key | value
---------- | ---
date | 2024-04-10T12:26:35+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The agent did not handle the cases where shelves had no fans, temperature sensors or PSUs.
This led to crashes during the agent execution.
With this werk we know correctly handle these scenarios and the corresponding services are not discovered if no items are found.
[//]: # (werk v2)
# check_httpv2: Lookup password containing whitespace
key | value
---------- | ---
date | 2024-04-16T13:05:49+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously, the active check "HTTP web service" failed to parse the site's
password store when there was at least one stored password containing whitespaces.
This was observable when configuring "Authentication" with a password from password store,
and resulted in a *CRIT* state and an error message like
```
error: invalid value 'http_pass' for '--auth-pw-pwstore <AUTH_PW_PWSTORE>': Can't parse password store: Unexpected format.
```
in the service's summary.