| Info |
|---|
| Error: An error occurred: Other restart currently in progress. Aborting. or The site is currently locked by another activation process. Please try again later. There are different error messages, to which this article may apply. Read the Problem section, to learn which exact error messages are relevant. |
| Status | ||||
|---|---|---|---|---|
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Problem
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. orTraceback (most Therecent sitecall islast): currently locked by another activation process. Please try again later. |
Solution A (recommended)
Check the entries within the site's web.log, you may see entries like below:
...
| language | bash |
|---|---|
| theme | RDark |
| title | ~/var/log/web.log |
...
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. in 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 |
| 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).
If you see one or more of the aforementioned jobs, move forward with this article.
Solution A (recommended)
As you verified in the section above, there are lingering files within the central site's ~/tmp/check_mk/wato/activation/ directory.
- A restart of the reboot of your Checkmk server's operating system will clear out these files and should allow you to activate changes again.
Solution B
If for whatever reason you cannot or do not want to restart reboot the server, you can delete the files manually on the command line. We recommend this only be done by experienced users.
Login to your central site as your the site user
Code Block language bash theme RDark root@linux:~# omd su - mysite
.Check to see if you have old directories within ~within $OMD_ROOT/tmp/check_mk/wato/activation/
Code Block language bash theme RDark OMD[mysite]:~$ cd ls -lah $OMD_ROOT/tmp/check_mk/wato/activation/ OMD[mysite]:~$ ll total 042 drwxrwx--- 3 mysite mysite 100 JanJul 4 1100:1242 6ecd4860-611e-4a4c-912f-74a6f1123e99/ drwxrwx--- 3 mysite mysite 100 JanJul 4 1100:1242 bec06bbc-1d35-4668-a421-151828b8500d/ drwxrwx--- 3 mysite mysite 920 JanJul 3 18:34 e55a7651263383ff-40ceb58b-40da4a8e-b11fba77-880d0778481fc6e1ff2d3b94/
It looks like there is one old directory that couldn't be deleted. The files here should be are deleted after one every minute by default.
.Remove the lingering directory and activate the changes again:
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 drwxrwxOMD[mysite]:~$ ls -lah $OMD_ROOT/var/check_mk/background_jobs/ total 42 drwx------ 2 mysite mysite 4.0K Jul 4 00:42 activate-changes-scheduler-0897307d-d177-4b6e-a500-1263a5ec3299/ drwx------ 2 mysite mysite 4.0K Jul 4 00:42 activate-changes-scheduler-1ba662c2-374a-4bce-9b6a-59329e9f11a5/ drwx------ 3 2 mysite mysite 9204.0K JanJul 3 18:34 e55a7651-40ce-40da-b11f-880d0778481f/
Code Block language bash theme RDark activate-changes-scheduler-263383ff-b58b-4a8e-ba77-c6e1ff2d3b94/ OMD[mysite]:~$ rm -R e55a7651-40ce-40da-b11f-880d0778481f/$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.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...