CMK version: 2.4.0p9
OS version: Debian 13
When will the version for Debian 13 Trixie be available?
The issues seem to be related to dependencies with libpango1.0-0, libperl5.36, and libldap-2.5
CMK version: 2.4.0p9
OS version: Debian 13
When will the version for Debian 13 Trixie be available?
The issues seem to be related to dependencies with libpango1.0-0, libperl5.36, and libldap-2.5
There are issues with the CXX ABI (GCC changed to 14). So, it will probably take until p11 or p12.
We are working on it.
Ok, thanks.
Will it then be possible to restore a backup from a previous version?
Or do we need to install Checkmk in a Docker container and restore from there before performing the upgrades?
A restore always needs the same Checkmk version (down to the patch level) as the backup was created with. So, running in a virtual machine or a Docker container for restore might be the best solution.
I will discuss with dev/PM whether it makes sense to run the same configuration migration scripts as used by the updater after restoring a backup in future Checkmk versions.
Thanks.
For now, I solved it by installing Checkmk in a Proxmox container.
And I’m considering keeping it there.
Could you please update Release notes - for Checkmk 2.4.0p9 to reflect that Debian 13 (Trixie) is currently NOT supported - other than stated there?
Hi @hesa - thank you very much for the hint. This got wrong when we centralized some internal variables to set the versions automatically. There referring to the major version again beginning with tonight’s build.
I have updated my monitoring machine to trixie without consulting the checkmk documentation, and it works for the most part. However, all graphs are broken, by which I mean the display is as if checkmk does not collect the data anymore (for example, I monitor the temperature of two machines, and while the current temp is displayed and updated, the graph is empty).
So if you upgrade “by accident” like me, it is not the end of the world, but still I would not advise it.
btw I am using the raw edition.
Damn. Same here. Assumption being the mother of all f ups…
p12 still not working with debian 13. Just so people know…
2.4.0p12 Is out, but still no support for the current Debian stable release.
I just installed and set up Debian 13, but now I realize there is no support for it yet. Is there an approximate time frame for when 13 will be supported? It’s not that easy to install 12…
Ubuntu 24.10, RHEL 10 and Debian 13 require CXXABI_1.3.15 which is supported from gcc 14.1.0, see ABI Policy and Guidelines
gcc14 support has been now added in our development branch (master). Now we have to port this to our stable branches and test to ensure it doesn’t break stuff.
Thank you very much for your reply. Could I already install this version on Debian 13? And later switch to the stable branch?
gcc 14.2 has been in Debian Testing since August 2024. And Debian isn’t known for being cutting edge is it?
I wouldn’t do so for productive environments. Sorry.
Switching from master to stable will likely not work. The configurations are likely not compatible.
Fair enough. Every major distro update comes with a lot of changes to packaging.
We do then all required changes in one haul, so that we can do system testing quite close to it, and gcc was just the last one remaining (and the most challenging).
That’s why we just highlighted that this was the last one blocking it. Guess that didn’t come across as intended.
Friendly reminder.
2.4.0p14 Is out, but still no support for the current Debian stable release.
I just looked in the internal tickets. 2.4.0p16 or p17 is more likely.
Martins explanation is still valid. Lots of work involved.
Can you give an ETA here when p16/17 will be released?
I would not want to give any false promises here, so I cannot give any specific estimates.
But I hope to be able to provide more information at the end of the week.