Werk #22636: automation-helper: omd start waits until the helper can serve requests
| Component | Site management | ||
| Title | automation-helper: omd start waits until the helper can serve requests | ||
| Date | Oct 20, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
omd start and omd restart used to report the automation-helper service
as started before it could serve requests. The daemon only answers requests
once its workers have started and read the configuration files. Automations
issued in that window, for example by services started after the automation
helper, had to wait for it or failed because the helper was not reachable.
Starting the automation-helper service now waits until the helper answers
requests. As a consequence, starting or restarting a site takes longer by the
time the helper needs to read the configuration files. The same applies to
installing, enabling or disabling extension packages (MKPs), since these
restart the automation helper to pick up new plug-ins.
If the automation helper does not become ready within 300 seconds, or exits
during start-up, the service is reported as failed. If the helper is already
running, omd start reports it as running without waiting.