Werk #19233: mysql.local.cfg now takes effect on single-directory installations
| Component | Agent bakery | ||||||
| Title | mysql.local.cfg now takes effect on single-directory installations | ||||||
| Date | Nov 2, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Incompatible - Manual interaction might be required | ||||||
| Checkmk versions & editions |
|
On a host with the single-directory agent layout, the baked mysql.cfg
included mysql.local.cfg from the configuration directory of the classic
layout, by default /etc/check_mk. The MySQL agent plug-in creates
mysql.local.cfg in the configuration directory of the agent, which on these
hosts is <installation directory>/default/package/config. The include
therefore never named the file that the plug-in had created, and settings in
that file had no effect. Hosts with the classic agent layout were not affected.
Starting with this release, the include names the configuration directory of the host's layout. On hosts with the classic layout the path is unchanged, including a path set by the rule "Installation paths for agent files (Linux, Unix)".
The include is part of the baked mysql.cfg. Bake the agent packages again and
deploy them to your hosts. Until a host receives the new package, it keeps the
old include.
If you worked around the problem by placing mysql.local.cfg under
/etc/check_mk on a single-directory host, move the file to
<installation directory>/default/package/config before you deploy.