Info |
---|
Error: An error occurred: Other restart currently in progress. Aborting 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
If you face this problem while activating changes:
Solution
Check the web.log, there should be something like this to be found alsoYou 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 | |||||||
---|---|---|---|---|---|---|---|
| 022-02-23 15:13:35,705 [30] [cmk.web.automations 7098] 'check_mk --automation restart' returned 'An error occurred: Other restart currently in progress. Aborting.
2022-02-23 15:13:35,705 [40] [cmk.web.automations 7098] Error running 'check_mk --automation restart' (exit code 1)
2022-02-23 15:13:35,706 [40] [cmk.web.site[<sitename>] 7098] error activating changes
| ||||||
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/watolib/activate_changeswato/pages/automation.py", line 1388231, in _doexecute_run configurationautomation_warningscommand = selfresponse._do_activate() set_data(repr(automation.execute(automation.get_request()))) File "/omd/sites/mysite/lib/python3/cmk/gui/watolibwato/pages/activate_changes.py", line 16511034, in _do_activate configuration_warnings = self._call execute return activate_changes.execute_activate_changes_automation() File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/activate_changes.py", line 1661,2128. in _callexecute_activate_changes_automation return execute_activate_changes(domains) warnings - get_config_domain(domain_request name)().activate(domain_request.settings) File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/activateconfig_changesdomains.py", line 179276, in execute_activate_changes warnings = domain_class().activate() 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/configcheck_mk_domainsautomations.py", line 60,53. in activate returnautomation_serialized cmdline, serialized_result check_mk_local_automation(config.wato_activation_method)_serialized( File "/omd/sites/mysite/lib/python3/cmk/gui/watolib/automations.py",. line 143,148. in check_mk_local_automation_serialized raise _local_automation_failure(command=command, cmk.gui.utilswatolib.exceptionsautomations.MKGeneralExceptionMKAutomationException: Error running automation call <tt>restart</tt>restart (exit code 1), error: <pre>AnAn error occurred: Other restart currently in progress, Aborting |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
The site is currently locked by another activation process. Aborting Please try again later. |
Log on via SSH and become site user. Then do (one step after another):
Stop the site
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 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 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 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]:~$
omd stop- Reload the config
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]:~$ cmk -O
.
Start the site againrm -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 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------ 2 mysite mysite 4.0K Jul 3 18:34 activate-changes-scheduler-263383ff-b58b-4a8e-ba77-c6e1ff2d3b94/ OMD[mysite]:~$ omd startrm -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.
.
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...