Remove older versions of checkMK -- what is the best way to do this?

General
,
1

Hi All,

What is the best way to remove older versions of checkMK on the same server?
We are currently running on version 2.2 and would like to remove at least v1.6.
Via Search I saw in another post that someone said it was possible to just delete the directory of the older version.
An IT colleague suggested using yum erase to remove the install package.

Which of these would be the better choice ?

Best regards,
Jacky

2

When you install Checkmk via package manager you also remove the software via package manager.
It’s that easy.

3

Hi Robert,

Thanx for replying.

I presume you mean this [ 3. Now uninstall all unused Checkmk versions. In the following command, the --purge parameter ensures that old configuration files are also erased. ] on this page: Linux upgrade on the Checkmk server (which I just found after some additional seaches)
when you refer to “package manager” & not to yum erase?

Best regards,
Jacky

4

you can use “omd cleanup” , with this all unused checkmk versions are automatically uninstalled

1 Like
5

Hi Andre,

Thanx for replying. I found the omd cleanup documentation you are referring to here: Site administration with omd

Thanx for the suggestion, it seems much simpler than the purge command I came across before. :slight_smile:

Best regards,
Jacky

6

Mmm … after reading this thread:

I’m not sure whether omd cleanup is the way to go now … as it’s not clear to me whether the issues experienced by the different replyers to the thread has been resolved in the meantime.

Does anyone know this for sure?

Best regards,
Jacky

7

Im using this command all the time and the problem was fixed two years ago

1 Like
8

yum is the package manager on RedHat based distributions.

9

Hello,
We also use yum remove/erase to delete old versions. We have checkmk installed on Red hat Linux.

Regards

10

Hi Robert,

Thanx for clarifying what you meant with “package manager”. :+1:

I have used the yum erase option on 1 of the older versions and that does indeed work. :smiley:

Best regards,
Jacky

11

Hi Christian,

Thanx for confirming that yum erase is definitely a viable way to go. :smiley:

Best regards,
Jacky

12

Hi Andre,

Thanx for the clarification about the fixed/not fixed status of the omd cleanup command. :+1:
I’ve not tried using it yet, but plan to test it on one of the remaining older versions. :smiley:

Best regards,
Jacky

1 Like
13

FYI, this is how it looked on our Server:

# omd cleanup
1.6.0p10.cee         Could not determine package. Keeping this version.
1.6.0p12.cee         Could not determine package. Keeping this version.
1.6.0p14.cee         Could not determine package. Keeping this version.
1.6.0p16.cee         Could not determine package. Keeping this version.
1.6.0p18.cee         Could not determine package. Keeping this version.
1.6.0p19.cee         Could not determine package. Keeping this version.
1.6.0p20.cee         Could not determine package. Keeping this version.
1.6.0p22.cee         Could not determine package. Keeping this version.
2.0.0p21.cee         Could not determine package. Keeping this version.
2.1.0p12.cee         Uninstalling
2.1.0p13.cee         Uninstalling
2.1.0p14.cee         Uninstalling
2.1.0p15.cee         Uninstalling
2.1.0p16.cee         Uninstalling
2.1.0p17.cee         Uninstalling
2.1.0p18.cee         Uninstalling
2.1.0p19.cee         Uninstalling
2.1.0p21.cee         Uninstalling
2.1.0p22.cee         Uninstalling
2.1.0p25.cee         Uninstalling
2.1.0p26.cee         Uninstalling
2.1.0p28.cee         Uninstalling
2.1.0p30.cee         Uninstalling
2.1.0p33.cee         Uninstalling
2.1.0p34.cee         Uninstalling
2.1.0p36.cee         Uninstalling
2.1.0p37.cee         Uninstalling
2.1.0p38.cee         Uninstalling
2.1.0p39.cee         Uninstalling
2.1.0p40.cee         Keeping this version, since it is the default.
2.2.0p9.cee          Uninstalling