Werk #22326: EC: new replication slaves sync at once
| Component | Event Console | ||
| Title | EC: new replication slaves sync at once | ||
| Date | Oct 22, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
An Event Console replicating the events of a central Event Console didn't sync with it as long as it had no saved replication status, e.g. right after setting up the replication. Instead, it behaved like a stand-alone Event Console: It neither took over the events and rules of the central Event Console nor ignored incoming messages. This went on until its configuration was reloaded once more, e.g. by activating changes again. If you had set up the replication by activating changes, it then ignored incoming messages without syncing until it was restarted, see Werk #22330. Conversely, an Event Console which you had configured to no longer replicate the events of a central Event Console kept syncing with it until it was restarted, replacing its own events with those of the central Event Console. Even after a restart, it kept using the rule packs and actions of the central Event Console instead of its own ones.
Such Event Consoles now start or stop syncing right away, and an Event Console which no longer replicates the events of a central Event Console uses its own rule packs and actions again.
Likewise, an Event Console which you configure to replicate the events of another central Event Console than before now syncs completely with the new one right away, like a newly set up Event Console. Previously, it kept using the rule packs and actions of its previous central Event Console until the new one reloaded its configuration.
Flushing a replicating Event Console with etc/init.d/mkeventd flush now only
deletes its events and its history, keeping its replication as it is, no matter
whether the Event Console is running or not. Previously, it also deleted its
saved replication status and its saved copy of the rule packs and actions of the
central Event Console. When it reloaded its configuration afterwards, e.g. when
activating changes, or when it was started again, it could therefore use its own
rule packs and actions instead of those of the central Event Console, or end a
takeover and ignore incoming messages again.
Why this werk is incompatible
Flushing a replicating Event Console no longer makes it start over like a newly set up one, i.e. with a complete sync with the central Event Console. If you relied on that, e.g. in a script, the flushed Event Console now keeps its replication status, so it stays in takeover mode if it had taken over, and it keeps its saved copy of the rule packs and actions of the central Event Console.
To let a replicating Event Console start over like a newly set up one, flushing
it is no longer enough: Stop it, delete the files var/mkeventd/slave_status
and var/mkeventd/master_config and start it again.