Werk #18751: Livestatus proxy no longer connects to disabled site connections
| Component | Livestatus proxy | ||||||
| Title | Livestatus proxy no longer connects to disabled site connections | ||||||
| Date | Jun 2, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
Previously, when you temporarily disabled a site connection in distributed
monitoring (the Disable in status GUI option of a connection), the Livestatus
proxy daemon (liveproxyd) on the central site kept a process running for that
site. That process continuously tried to (re)connect to the - often
unreachable - remote site, spamming var/log/liveproxyd.log with messages like:
Failed to create channel to (...): [Errno 111] Connection refused
and
Could not send heartbeat for 10 secs - no free channel
On setups with several disabled connections this wasted noticeable CPU time and memory, in extreme cases filling up the central site's RAM. The processes also came back after a restart of the site.
This has been fixed. Disabled site connections are now excluded from the Livestatus proxy configuration, so the proxy no longer spawns a process or attempts to connect to them. Re-enabling the connection restores the proxy connection as before.
This only affects status data, which a disabled connection does not provide anyway. Configuration replication to the remote site is handled separately and is not affected.
The Livestatus proxy configuration is regenerated when site connections are saved. For connections that are already disabled when you upgrade, re-save the site connection once (or toggle the Disable in status GUI option) to apply the new behavior and remove the lingering proxy process.