ID: 8613
Title: Fix exception when signing agent and a host once had an agent but now don't
Component: Agent Bakery
Level: 2
Class: Bug Fix
Version: 1.4.0i1
ID: 8571
Title: Guard against mixing up check results from different hosts.
Component: The Check_MK Micro Core
Level: 2
Class: Bug Fix
Version: 1.4.0i1
ID: 8572
Title: Made scheduling of check helpers more robust
Component: The Check_MK Micro Core
Level: 2
Class: Bug Fix
Version: 1.4.0i1
Under very rare circumstances the monitoring core miscounted the number of
idle helpers, leading to an endless loop with 100% CPU load.
ID: 8555
Title: Enable local asynchronous notification delivery using mknotifyd by default
Component: Notifications
Level: 2
Class: New Feature
Version: 1.4.0i2
The notification deamon can be used for local asynchronous delivery and is informing you
about failed notification delivery since werk #8330 and is increasing the performance of
notifications in case the delivery of notifications takes time.
So the default delivery mechanism has been changed to use the local asynchronous delivery
in the Enterprise Edition.
ID: 8557
Title: Alert handling: Fixed repeating error "OSError: [Errno 9] Bad file descriptor"
Component: The Check_MK Micro Core
Level: 2
Class: Bug Fix
Version: 1.4.0i2
This error occured when a helper was terminated or not really started and persisted
until the alert helper was restarted (e.g. with cmk -R) and prevented othr event handlers
from working correctly.
ID: 8634
Title: Fixed broken config when configuring "Parameters for linux_remote" ruleset
Component: Alert Handlers
Level: 2
Class: Bug Fix
Version: 1.4.0i2
This fixes this error after configuring a rule for this ruleset when executing
Check_MK commands:
Cannot read in configuration file /omd/sites/heute/etc/check_mk/conf.d/wato/rules.mk: name 'alert_handler_parameters' is not defined
ID: 8638
Title: Fixed broken notifications when Check_MK notification spooler not enabled (regression since 1.4.0i2)
Component: Notifications
Level: 3
Class: Bug Fix
Version: 1.4.0i3
When updating an existing site to 1.4.0i2 or 1.4.0i2p2 while not having the "Check_MK notification spooler"
enabled via "omd config", the notification system stopped sending notifications.
The background is that the default notification mechanism had been changed from direct delivery to
asynchronous delivery. And this was done even when the notification spooler, which is responsible for
delivering the asynchronous notification, was disabled.
The notifications are not lost, they have simply not been processed. In case you are affected,
there should exist one file for each notification that has been created but was not delivered
below <tt>var/check_mk/notify/spool/</tt>.
To fix this issue just install the new version. After the update all notification will be sent out.
In case you want to supress the stuck notifications, you can go to the directory mentioned above and
remove the <tt>.mk</tt> files in this directory before starting the site again.
To make it work for you with the existing versions, you can execute "omd config" and go to
"Distributed Monitoring > MKNOTIFYD" and enable this option. After starting the site again,
all your notifications will be processed and are sent to the users.
ID: 8637
Title: Check_MK Notification Spooler is now always enabled
Component: Notifications
Level: 2
Class: New Feature
Version: 1.4.0i2
The notification spooller will be enabled on all sites and can not be
disabled anymore via "omd config".