I am not able to reproduce it.
Update from 2.2.0p23cre tp 2.3.0b3.cre or 2.2.0p24cre to 2.3.0b3.cre with one host registered via TLS works out of the box. No errors.
Can you tell if there are any local custom extensions or if this existing 2.2.0p23.cre was upgraded/downgraded ever to/from cee?
I think it is possible that this error is triggered if you have an mkp installed that also has parts that are only cee usable.
Like deployment rules for agent plugins or so.
I just disabled all plugins to be sure, same error.
OMD[home]:~$ mkp list
Name Version Title Author Req. Version Until Version Files State
----------------------- --------------- ---------------------------- ------------------------------------------------ ------------ ------------- ----- --------
fail2ban 1.9.1 Monitor fail2ban jail status Jens Kuehnel 2.0.0 None 7 Disabled
snmp_uptime 20220306.v0.0.1 SNMP Uptime Th.L. (thl-cmk[at]outlook[dot]com) 2021.09.20 None 1 Disabled
active_check_traceroute 0.0.2-20230607 Check Traceroute (extended) Th.L. (thl-cmk[at]outlook[dot]com) 2.1.0b1 None 4 Disabled
checkmk_update 0.1.1-20230519 Checkmk Update Th.L. (thl-cmk[at]outlook[dot]com) 2.0.0b1 None 3 Disabled
sslcertificates 8.7.3 SSL-Certificates Robert Sander <r.sander@heinlein-support.de> 2.0.0 None 6 Disabled
qemu 2.0.2 Qemu / KVM Kuhn & Rueß GmbH 2.0.0 None 4 Disabled
access_logs 1.2.1 HTTP Access Logs Notausstieg0309 <Notausstieg0309@googlemail.com> 2.0.0 None 8 Disabled
Don’t think there is anything else that specific about my installation. Never had CEE, always CRE. Is there a way to get more verbosity/debug for the update script?
That worked. Removing the different cee directories worked.
With that being said, it’s not the first time I’m having issues updating because of MKPs. Do you think the updating process could be a little bit more resilient to this in the future?
I do have a new issue starting the site however, will need to investigate further later today.
Starting nagios.../omd/sites/home/bin/nagios: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
Might be a missing dependancy somewhere or just permissions.
With that being said, it’s not the first time I’m having issues updating because of MKPs. Do you think the updating process could be a little bit more resilient to this in the future?
The libperl error is a typical problem with wrong package for your distribution.
Also if OpenSuse should be binary compatible, i would not use such a setup for any tests.
I don’t understand what you are saying here. It’s the exact same OS, except for the fact that SLES requires a paid registration that comes with support.
With the release of SLES 15 SP3 we now have 100% binary compatibility with openSUSE Leap 15.3 (our developer platform). That means that you can smoothly move workloads from development to production environments that run SLE 15 SP3 – and back again – with assured application compatibility.
Thank you, very appreciated. I will happily test again with my broken plugins on 2.3.0b4. I noticed it does not only crash during the update process but also cause the same errors after the update if the packages are reinstalled/reenabled.
All in all it’s never too easy to update to a major or minor version (but that’s expected with betas). Patches are easy. But I got a lot of other problems and overcame most. I see some of them are already fixed on GitHub (such as the postfix plugin). Others I’m not sure if normal (for example SNMP uptimes had to be deleted and rediscovered to work for me, I see the plugin has been modified). Also got some other issues which I reported to the feedback email. I haven’t been able to make the new http plugin work but it looks promising, looking forward to make it work.
From our experience, custom extensions (via MKPs from the exchange, GitHub etc.) are the main reason for issues in the update process.
We have added many developer APIs in Checkmk 2.3, so that developers of such extensions can built their extensions on these APIs and users can then benefit from much higher stability during major updates as well.
We will also start cleaning up the exchange sooner or later as many plug-ins there are broken and not maintained anymore.
