Werk #19681: omd: Livestatus TCP daemon is now fully managed by omd
| Component | Livestatus | ||
| Title | omd: Livestatus TCP daemon is now fully managed by omd | ||
| Date | Apr 22, 2026 | ||
| Level | Trivial Change | ||
| Class | Bug Fix | ||
| Compatibility | Incompatible - Manual interaction might be required | ||
| Checkmk versions & editions |
|
The livestatus TCP daemon configuration is now fully managed by omd. The
configuration file etc/mk-livestatus/xinetd.conf has been removed from the omd
skeleton and is no longer deployed when creating a new site. The active
configuration is now written to etc/xinetd.d/livestatusv1 and is managed
exclusively by omd.
As a result, omd diff no longer incorrectly reports changes to
etc/mk-livestatus/xinetd.conf on a fresh site.
Manual modifications to the livestatus TCP daemon configuration outside of
omd config are no longer possible. Use omd config to adjust the livestatus
behaviour instead.
To cover previously manual configuration options, omd config has been extended
with the following new parameters:
LIVESTATUS_INSTANCES: Maximum number of server instances that can be started by xinetd.LIVESTATUS_PER_SOURCE: Maximum number of simultaneous connections allowed from a single source IP.
For details on these parameters see man 5 xinetd.conf.
Incompatible change: If your site has local modifications to
etc/mk-livestatus/xinetd.conf, an update warning will be shown prompting you
to migrate those changes to omd config manually before the old file is
replaced.