So today I upgraded our distributed environment from CME 1.6.0p22 to CME 2.0.0p3.
Worked like a charm, expected nothing less.
BUT: Now the replication from master to slaves does not replicate the ~/local structure anymore.
Before it worked on all connected sites. And the settings are still correct, I verified that.
There are no errors shown in the UI and the configuration synchronization itself works.
The permissions in the filesystem look about right, too.
Does anyone have a similar issue or an idea what could be causing this behavior?
I got the idea that after changes are applied, local was synced to the other slaves. Have you checked the sync with new file and with (new test) checkmk site? To verify that it is in your site or in the CheckMK version.
Ist es möglich, dass das auch die Enterprise Edition betrifft?
Nach dem Upgrade von 1.6.0p22 auf 2.0.0p1 hatten wir das Problem, dass nach der Aktivierung von Changes oft alle Files unter “local” auf den Slave-Instanzen gelöscht und nicht erneut gesynct wurden - nach dem Aktivieren eines weiteren Changes, wurden die Files dann wieder korrekt gesynct. Wir haben daraufhin temporär den Sync in den Settings für unsere Slave-Sites deaktiviert. Getestet haben wir allerdings nur mit der 2.0.0p1, aktuell sind wird schon auf der 2.0.0p3.
Also bei in der CME mir ist das Problem persistent, egal wie oft ich Ă„nderungen aktiviere.
Blöderweise wird auf dem Satelliten tatsächlich ~/local komplett geleert, sodass ich auch nicht manuell etwas hinlegen kann.
@keylane_sbaas: Yes I modified some files but to no avail.
I can understand how difficult it is with no clear message in logging. If you want to can increase the logging level to maximum of debug logging. Maybe that will give you a message in logging.
So you did create second slave site and tried/check if the replication does work from your master? I was not sure from the answer if you did.
Last resort that I can think is, create CheckMK and OMD backup. Create clean new site and restore you backup and check if the problem persist.
I re-enabled it today and tested it several times. The problem still exists in 2.0.0p3, but it happens only in about 1 out of 4 cases. Sometimes the files in the “local” folder just disappeared on the slave site.
We definitely didn’t have the problem before version 2.0.
Our problem still exists in version 2.0.0p7 CEE. We recently set up another slave site that keeps losing all files in /local from time to time after config activations.