...
Status | ||||
---|---|---|---|---|
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
You may face ones of these problems while activating changes. The exact error message might look different, but this article might still apply.
One of these error messages might apply to you:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
Got invalid data: Internal automation error: Error running automation call restart (exit code 1), error: An error occurred: Other restart currently in progress. Aborting Traceback (most recent call last): File "/omd/sites/mysite/lib/python3/cmk/gui/wato/pages/automation.py", line 231, in _execute_automation_command response.set_data(repr(automation.execute(automation.get_request()))) File "/omd/sites/mysite/lib/python3/cmk/gui/wato/pages/activate_changes.py", line 1034, in execute return activate_changes.execute_activate_changes( File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/activate_changes.py", line 2128. in execute_activate_changes warnings - get_config_domain(domain_request name)().activate(domain_request.settings) File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/config_domains.py", line 76, in activate return ("restart": restart, "reload": reload,)[ File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/check_mk_automations.py*. line 275, in restart automation_serialized("restart", args=hosts_to_update) File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/check_mk_automations.py", line 53. in automation_serialized cmdline, serialized_result check_mk_local_automation_serialized( File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/automations.py". line 148. Internal automation errorin check_mk_local_automation_serialized raise local_automation_failure( cmk.gui.watolib.automations.MKAutomationException: Error running automation call restart (exit code 1), error: An error occurred: Other restart currently in progress. Aborting. , Aborting |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
The site is currently locked by another activation process.
Please try again later. |
Verification
- Log into your central Checkmk site as an administrative user and navigate to Background jobs.
- Check the section titles Activate Changes Scheduler for running jobs, which are older than a few minutes.
- Take note of the UUID at the end of the job name (activate-changes-scheduler-263383ff-b58b-4a8e-ba77-c6e1ff2d3b94).
...
As you verified in the section above, there are lingering files within the central site's ~/tmp/check_mk/wato/activation/ directory.
- A reboot of your Checkmk servers server's operating system will clear out these files and should allow you to activate changes again.
...
Login to your central site as the site user
Code Block language bash theme RDark root@linux:~# omd su mysite
.Check to see if you have old directories within $OMD_ROOT/tmp/check_mk/wato/activation/
Code Block language bash theme RDark OMD[mysite]:~$ ls -lah $OMD_ROOT/tmp/check_mk/wato/activation/ total 42 drwxrwx--- 3 mysite mysite 100 Jul 4 00:42 6ecd4860-611e-4a4c-912f-74a6f1123e99/ drwxrwx--- 3 mysite mysite 100 Jul 4 00:42 bec06bbc-1d35-4668-a421-151828b8500d/ drwxrwx--- 3 mysite mysite 920 Jul 3 18:34 263383ff-b58b-4a8e-ba77-c6e1ff2d3b94/
It looks like there is one old directory that couldn't be deleted. The files here are deleted every minute by default.
.Remove the lingering directory:
Code Block language bash theme RDark OMD[mysite]:~$ rm -r $OMD_ROOT/tmp/check_mk/wato/activation/263383ff-b58b-4a8e-ba77-c6e1ff2d3b94/
.There will be a corresponding background job in $OMD_ROOT/var/check_mk/background_jobs/, which can be cleaned up as well:
Code Block language bash theme RDark OMD[mysite]:~$ ls -lah $OMD_ROOT/var/check_mk/background_jobs/ total 42 drwx------ 2 hydemysite hydemysite 4.0K Jul 4 00:42 activate-changes-scheduler-0897307d-d177-4b6e-a500-1263a5ec3299/ drwx------ 2 hydemysite hydemysite 4.0K Jul 4 00:42 activate-changes-scheduler-1ba662c2-374a-4bce-9b6a-59329e9f11a5/ drwx------ 2 hydemysite hydemysite 4.0K Jul 3 18:34 activate-changes-scheduler-263383ff-b58b-4a8e-ba77-c6e1ff2d3b94/ OMD[mysite]:~$ rm -R $OMD_ROOT/var/check_mk/background_jobs/activate-changes-scheduler-263383ff-b58b-4a8e-ba77-c6e1ff2d3b94/
.- Now go back to the UI and try to activate changes.
...