Unable to update within 2.2.0p version

My single site raw cre install of 2.2.0p7 is not allowing me to upgrade to latest version 2.2.0p17.
It says:
Site ict uses version 2.1.0p9.cre which is not installed.
Please reinstall that version and retry this command.

But everywhere else ( like in omd itself and in the web gui) it claims and says it is already on 2.2.0p7 ?

Here are some steps with info of what it reports.

omd versions
2.1.0p9.cre
2.2.0p7.cre (default)

omd sites
SITE VERSION COMMENTS
ict 2.2.0p7.cre default version

omd su ict
Last login: Sun Dec 24 17:28:56 UTC 2023 on pts/0

omd version
OMD - Open Monitoring Distribution Version 2.2.0p7.cre

omd update
Saving temporary filesystem contents…OK
Unmounting temporary filesystem…OK
Site ict uses version 2.1.0p9.cre which is not installed.
Please reinstall that version and retry this command.

ls -l /omd/versions/
total 0
drwxr-xr-x. 3 root root 17 Apr 24 2023 2.1.0p9.cre/
drwxr-xr-x. 8 root root 81 Jul 25 07:46 2.2.0p7.cre/
lrwxrwxrwx. 1 root root 11 Aug 1 12:31 default → 2.2.0p7.cre/

ls -l /omd/versions/2.1.0p9.cre/
total 0
drwxr-xr-x. 3 root root 20 Apr 24 2023 lib/

ls -l /omd/versions/2.1.0p9.cre/lib/
total 0
drwxr-xr-x. 3 root root 21 Nov 23 2021 apache/

ls -l /omd/versions/2.2.0p7.cre/
total 16
drwxr-xr-x. 3 root root 4096 Aug 1 12:30 bin/
drwxr-xr-x. 6 root root 119 Aug 1 12:30 include/
drwxr-xr-x. 14 root root 4096 Aug 1 12:31 lib/
drwxr-xr-x. 3 root root 17 Feb 21 2022 local/
drwxr-xr-x. 11 root root 127 Feb 21 2022 share/
drwxr-xr-x. 6 root root 105 Aug 1 12:31 skel/

Do I need to get the two no longer available files from checkmk feedback@checkmk.com to somehow recover from this?

check-mk-raw-2.1.0p9.cre.tar.gz
check-mk-raw-2.1.0p9-el8-38.x86_64.rpm

Any feedback or info how to solve this?
Do I need to somehow get the old rhel 8 rpm for 2.1.0p9 and install it? or unpack some of it’s contents to somewhere on disk?
Surely I am not the first and there are some docs on how to go about solving this?

It is a little bit strange that you have such a folder for apache as a leftover from an older version.
The only thing what you can look at, is inside the “~/etc/” folder in your site if there is somewhere a file with “2.1.0p9”.
I think the last upgrade from 2.1.0p9 to 2.2.0p7 was not without error messages.

Hey Andreas,
Thanks I think you pointed me in the right direction. I found the following entries when doing a
ls -ltrR etc

./init.d:
total 76
-rwxr-xr-x. 1 ict ict 2944 Jun  6  2018 gearman_worker*
-rwxr-xr-x. 1 ict ict 2298 Jun  6  2018 nagflux*
-rwxr-x---. 1 ict ict 4462 Jul 11  2018 npcd*
-rwxr-x---. 1 ict ict 2864 Oct  8  2018 rrdcached*
-rwxr-x---. 1 ict ict 8189 Oct  8  2018 nagios*
-rwxrwx---. 1 ict ict 3985 Oct  8  2018 mkeventd*
-rwxr-x---. 1 ict ict 1183 Oct  8  2018 crontab*
-rwxr-x---. 1 ict ict 4798 Oct  8  2018 apache*
-rwxr-xr-x. 1 ict ict 2970 Apr  9  2020 pnp_gearman_worker.orig*
-rw-rw----. 1 ict ict 3022 Aug 12  2022 pnp_gearman_worker-2.1.0p9.cre
-rw-rw----. 1 ict ict 3040 Aug 12  2022 pnp_gearman_worker-2.0.0p27.cre
-rwxr-x---. 1 ict ict 1579 Aug 12  2022 redis*
-rwxr-x---. 1 ict ict 1983 Aug 12  2022 xinetd*
-rwxr-x---. 1 ict ict 2203 Aug 12  2022 stunnel*
-rwxr-x---. 1 ict ict 3047 Nov 14  2022 pnp_gearman_worker*
-rwxrwx---. 1 ict ict 3402 Aug  1 09:29 agent-receiver*
lrwxrwxrwx. 1 ict ict    6 Aug  1 09:30 core -> nagios*

How do I handle these 3 lines?

-rwxr-xr-x. 1 ict ict 2970 Apr  9  2020 pnp_gearman_worker.orig*
-rw-rw----. 1 ict ict 3022 Aug 12  2022 pnp_gearman_worker-2.1.0p9.cre
-rw-rw----. 1 ict ict 3040 Aug 12  2022 pnp_gearman_worker-2.0.0p27.cre

Thanks for any pointers or help with this.

Oh this looks like a very old instance that was migrated from Consols OMD version to CheckMK OMD.
Important are not these files with the endings you mentioned. More important are the files with “2.1.0p9” in the content.

Yes, it is quite an old install indeed.

So how do I deal or fix the issue?

the omd cmd line and the web gui both say I am on version 2.2.0p7 cre.

but when trying to do the omd upgrade from 2.2.0p7 to latest 2.2.0p17 it tells me it is missing 2.1.0p9 in order to do an upgrade.

So I seem stuck as that old version cannot be downloaded anymore and Check_MK feedback who are listed as the email to ask for older downloads do not respond ( tried twice so far)

Is there a file I can remove or a symlink I need to point to somewhere else? How do I go about fixing this? BTW FYI the ONLY file under etc that has 2.1.0p9.cre in it is

etc/init.d/pnp_gearman_worker-2.1.0p9.cre

I also spotted two other file collections when searching for files ending in .orig under etc on that site …

./mk-livestatus:
total 28
-rw-r--r--. 1 ict ict 1389 Jul 24  2019 xinetd.conf.orig
-rw-r--r--. 1 ict ict 1416 Apr  7  2020 xinetd.conf-1.6.0p11.cre
-rw-r--r--. 1 ict ict 1412 Apr  7  2020 xinetd.conf-1.5.0p19.cre
./init.d:
total 76
...
-rwxr-xr-x. 1 ict ict 2970 Apr  9  2020 pnp_gearman_worker.orig*
-rw-rw----. 1 ict ict 3022 Aug 12  2022 pnp_gearman_worker-2.1.0p9.cre
-rw-rw----. 1 ict ict 3040 Aug 12  2022 pnp_gearman_worker-2.0.0p27.cre
...
./omd:
total 28
-rw-rw-rw-. 1 ict ict 131 Apr 24  2023 allocated_ports.orig
-rw-r--r--. 1 ict ict  89 May  4  2023 allocated_ports-2.1.0p27.cre
-rw-r--r--. 1 ict ict  81 May  4  2023 allocated_ports-2.1.0p16.cre

But I assume since the omd upgrade only complains about 2.1.0p9 then the only file I have to somehow deal with is:

etc/init.d/pnp_gearman_worker-2.1.0p9.cre

Any pointers to documentation or a how to resolving this issue?

Thank you so much for your work on this.

This is a very rare situation with a site that old.
Honestly, I would consider a clean rebuild.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.