ID: 5025
Title: Make communication with smartping helpers more robust
Component: Core & setup
Level: 1
Class: Bug fix
Version: 1.5.0i1
When the communication between the Micro Core and the smartping helpers
(icmpsender/icmpreceiver) fails, we restart the latter, but we forgot to
flush an internal buffer. In some cases this could lead to more
communication problems later. This has been fixed.
ID: 5080
Title: mssql_blocked_sessions: Put details about session ID, blocking ID, wait data and type into longoutput
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.5.0i1
Previously above details were displayed in service details
which causes overcrowding. Now a summary about which session
IDs are blocked by how much blocking IDs is shown and etails
can be found in the long output of the service.
ID: 5051
Title: Fixed backup/restore of encrypted backups
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i1
It was not possible to perform encrypted backups since version 1.4.0b5. An error
message "NotImplementedError("Use module Crypto.Cipher.PKCS1_OAEP instead“)" was
displayed in the log when trying to create such a backup.
Workaround: Disable encrypted backups and perform unencrypted ones.
Encrypted backups created with previous versions need to be restored with 1.4.0b4
or older.
ID: 5024
Title: Fixed parsing of some host-related monitoring history entries.
Component: Livestatus
Level: 1
Class: Bug fix
Version: 1.5.0i1
Some log lines in the monitoring history were classified incorrectly,
leading to possibly wrong results in e.g. availibility calculations. This
has been fixed.
The affected kind of lines were:
INITIAL HOST STATE
CURRENT HOST STATE
HOST ALERT
ID: 4987
Title: oracle_instance: Removed uptime from inventory plugin in sense of werk #4485
Component: HW/SW Inventory
Level: 1
Class: Bug fix
Version: 1.5.0i1
ID: 4854
Title: WATO Web-API: The liveproxyd configuration was not correctly updated when a site got configured
Component: WATO
Level: 1
Class: Bug fix
Version: 1.5.0i1
This caused strange side effects, whereas a site was correctly configured in the
distributed monitoring page, but always considered <i>dead</i> from the liveproxyd's perspective.