A new mechanism has been introduced allowing certain tasks to be run as background processes.
Currently the following areas are included
- Host renaming
- Agent baking (Enterprise Edition)
- Report generation (Enterprise Edition)
Once a background job is triggered, an overview page provides additional information
regarding the progress. You can also stop and delete background jobs, if applicable.
Keep in mind that some jobs - in detail host renaming and agent baking - lock certain areas
in WATO to prevent further configurations as long the background process is running.
Each background has a working directory located in ~/var/check_mk/background_jobs with
a statusfile named jobstatus.mk. If the background job generates stdout data it will
be shown in the job details page. Job Exceptions are also shown in the details page and, in addition,
written to ~/var/log/web.log.
Keep in mind, old background jobs will be automatically removed after 30 days or if the maximum amount
of jobs for a job type has been reached. These limits are currently not configurable and hardcoded
- Reporting has a limit of 100
- Host renaming has a limit of 50
This cleanup routine is regularly called through a multisite cronjob.
To the list of all Werks