I am unable to update my site beyond 1.6.0p24. Attempts to update to ANY of the flavors of 2.0.0px ends with the update process stuck.
It appears to be the same issue in this thread…
https://forum.checkmk.com/t/omd-update-to-2-0-0p2cre-stuck-during-cmk-update-config/24172
Is there any way to increase the verbosity of the logs? I looked at /omd/sites/mysite/var/log/update.log However, the text is the same that is presented on the screen during the update attempt (no further details)
Creating temporary filesystem /omd/sites/wmur/tmp…OK
Executing update-pre-hooks script “02_cmk-update-config”…
-| Initializing application…
-| Loading GUI plugins… [<- This is where it freezes. During the “frozen state” the python3 process is pegged on 100% cpu load]
Aborted.
If I crtl+c after the update process is stuck and get the ‘Aborted’ response. The site is updates to 2.0.0px. But, all service checks of any device with the agent installed is broken. No further checks. Only host-alive ICMP ping checks are working.
I have a close of my primary Check_MK server running as a VM. So, I have the ability to easily rollback to a snapshot. I’ve tried all flavors of 2.0.0px. I’ve even tried taking a backup of the running server on 1.6.0p24 and restoring it to a brand new Ubuntu 20.04 install and a clean install of 1.6.0p24. Same results.
Is there any to increase the debug level of the logs to see what is hanging during the update process?
Can I manually perform each step of the update process, in the hopes of catching the culprit?
I have >150 hosts with >1400 services. I really don’t want to re-enter all of these manually….