Werk #14469: Notification spooler: Fix possible ConnectionRefusedError after update to 2.0
| Component | Notifications | ||
| Title | Notification spooler: Fix possible ConnectionRefusedError after update to 2.0 | ||
| Date | Aug 15, 2022 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
If the notification spooler configuration was made via "Distributed monitoring" - "Site specific global configuration" for central sites in versions before 2.0, the start of the mknotifyd daemon could fail with an error like "ConnectionRefusedError: [Errno 111] Connection refused".