| Info |
|---|
This article explains how to troubleshoot a pending activation error while working with a remote site. |
| Status |
|---|
| colour | Green |
|---|
| title | LAST TESTED ON CHECKMK 2.3.0P1 |
|---|
|
| Panel |
|---|
| borderColor | black |
|---|
| bgColor | #f8f8f8 |
|---|
| title | Table of Contents |
|---|
|
|
Problem
During the activation of changes from master the central site for a remote site, we faced an issue. This will hapen happen if WATO is enabled on the remote site and if you have pending changes there.
| Info |
|---|
 Image Removed
|
On the slave:
In the 'replication_changes_slave.mk' you will find the pending change.
...
Image Added
| Code Block |
|---|
|
Failed: Garbled automation reponse
Internal automation error: There are 1 pending changes that would get lost. The most recent are: Modified host p19central-vcenter-agent.txt.
Traceback (most recent call last):
File "/omd/sites/remote/lib/python/cmk/gui/wato/pages/automation.py".line 186, in execute_automation _command
html.write(repr(automation.execute(automation.get_request()))File ":/omd/sites/remote/lib/python/cmk/gui/watolib/sites.py":. line 717, in get
request self._verify_remote_site_config(site_id) File "/omd/sites/remote/lib/python/cmk/gui/watolib/automation_commands.pyquot:, line 63, in
verify_remote_site_config raise MKGeneralException(message) MKGeneralException: There are 1 pending changes that would get lost. The most recent are:
Modified host p19central-vcenter-agent.txt |
On the remote:
On the remote site, the pending change is stored in the ~/var/check_mk/wato/replication_changes_remote.mk file.
| Code Block |
|---|
|
OMD[ slaveremote]:~/var/check_mk/wato$ ll
total 36
drwxrwx--- 2 slave slave 4096 Dec 11 2 remote remote 4096 Dec 11 10:07 activation/
drwxrwxr-x 2 slave slave 4096 Dec 11 2 remote remote 4096 Dec 11 13:24 auth/
-rw-rw---- 1 slave slave 35 Dec 10 1 remote remote 35 Dec 10 14:14 automation_secret.mk
-rw-rw---- 1 slave slave 9 Dec 10 1 remote remote 9 Dec 10 14:12 last_bake.mk
drwxrwxr-x 2 slave slave 4096 Dec 10 2 remote remote 4096 Dec 10 14:12 log/
drwxrwx--- 2 slave slave 4096 Dec 10 2 remote remote 4096 Dec 10 14:12 php-api/
-rw-rw---- 1 slave slave 301 Dec 11 1 remote remote 301 Dec 11 13:24 replication_changes_ slaveremote.mk
-rw-rw---- 1 slave slave 130 Dec 11 1 remote remote 130 Dec 11 12:00 replication_status_ slaveremote.mk
drwxrwxr-x 3 slave slave 4096 Dec 11 3 remote remote 4096 Dec 11 12:00 snapshots/ |
| Code Block |
|---|
| language | bash |
|---|
| theme | RDark |
|---|
| title | ~/var/check_mk/wato |
|---|
|
OMD[slaveremote]:~/var/check_mk/wato$ cat replication_status_slaveremote.mk
{'current_activation': None, 'last_activation': 'f9607439-2303-412c-a188-f4e0f54702ae', 'times': {'restart': 1.6235217094421388}}
OMD[slaveremote]:~/var/check_mk/wato$ cat replication_changes_slaveremote.mk
{'need_restart': True, 'need_sync': True, 'user_id': u'cmkadmin', 'time': 1607689496.047742, 'domains': ['check_mk'], 'text': u'Modified host p19masterp19central-vcenter-agent.txt.', 'object': ('CREHost', 'p19masterp19central-vcenter-agent.txt'), 'id': 'cc91dcc8-bcc6-46fa-a264-9bdc5b041720', 'action_name': 'edit-host'} |
Solution
In order to activate changes successfully from master central to slaveremote, you need to delete both replication-Files on the slaveremote:
| Code Block |
|---|
|
OMD[slaveremote]:~/var/check_mk/wato$ rm replication_* |
| Note |
|---|
To avoid this kind of issue, you should disable WATO on the slave remote and push the configuration only from mastercentral. |
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | KB |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ( "distributed_monitoring" , "wato" , "pending_changes" , "troubleshooting" ) and type = "page" and space = "KB" |
|---|
| labels | wato pending_changes distributed_monitoring |
|---|
|
...