We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Werk #8780: mknotifyd: fix race condition in distributed setups

ComponentNotifications
Titlemknotifyd: fix race condition in distributed setups
Date2019-07-08 14:39:16
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version1.6.0b4,1.7.0i1
LevelProminent Change
ClassBug Fix
CompatibilityCompatible - no manual interaction needed

In a distributed setup a slave site may try to deliver notifications locally during an activate changes even though the slave site should forward notifications to the master site.

This effect appears when the option "Notification Spooling" is set to "Asynchronous local delivery by notification spooler" in the global settings and to "Forward to remote site by notification spooler" in the "Site specific global settings" of the slave site.

This werk fixes this issue by locking the Checkmk configuration when a configuration snapshot is installed on the remote site. This way the "cmk --notify" command and the mknotifyd cannot use a partially installed Checkmk configuration.

As a workaround the "Notification Spooling" can be set to "Forward to remote site by notification spooler" in the global settings and to "Asynchronous local delivery by Notification spooler" in the "Site specific global settings" of the slave site.