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.
Code Block | ||||
---|---|---|---|---|
| ||||
# One of these error messages might apply to you: Error running automation call restart (exit code 1)., error: An error occurred: Other restart currently in progress. Aborting. orInternal automation Theerror: siteError isrunning currentlyautomation lockedcall byrestart another(exit 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 |
...
code 1), error: An error occurred: Other restart currently in progress. Aborting. |
...
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 reboot of the your Checkmk servers 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 tmp/check_mk/wato/activation/ OMD[mysite]:~$ llls -lah total 0 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 try to activate the changes again:
Code Block language bash theme RDark drwxrwx--- 3 mysite mysite 920 Jan 3 18:34 e55a7651-40ce-40da-b11f-880d0778481f/
Code Block language bash theme RDark OMD[mysite]:~$ rm -R e55a7651-40ce-40da-b11f-880d0778481f/
...