Werk #2407: WATO master/slave replication: fixed problem where the configuration from the master site was not activate on slave site
| Component | Setup | ||||||||||||||||||
| Title | WATO master/slave replication: fixed problem where the configuration from the master site was not activate on slave site | ||||||||||||||||||
| Date | Jul 17, 2015 | ||||||||||||||||||
| Level | Prominent Change | ||||||||||||||||||
| Class | Bug Fix | ||||||||||||||||||
| Compatibility | Compatible - no manual interaction needed | ||||||||||||||||||
| Checkmk versions & editions |
|
Changes made on a distributed WATO slave site could delay a configuration update attempt from the master.
Detailed information: Any changes on a slave site which lead to a pending log entry triggered the cmcrushd. The cmcrushd creates a configuration for the microcore, which takes precendence over creating the configuration anew. When a snapshot got pushed from the master site, the slave site thought that there is already a precompiled configuration available and used the cmcrushd configuration.
This problem is automatically resolved on the following configuration push from the master, because the cmcrushd configuration is only used once.