[Check_mk (english)] confused with OMD versions (and upgrade path)

Afternoon list,

Our original installation of check_mk was done via OMD downloaded from http://omdistro.org/ which has been fine, we have upgraded a couple of versions and now reside on 1.30.

This puts us on check_mk v 1.2.6p12, I would like to use 1.2.8 (or latest stable) and all the wonders that has but I believe the official advice is to not to manually upgrade check_mk and stick to omd update.

Sooo now I’m looking at the check_mk website, I can grab the latest raw deb file, however when I installed it on a test box to see what was going on omd version sez:

OMD - Open Monitoring Distribution Version 1.2.8p14.cre

And on my original server since the upgrade I get:

OMD - Open Monitoring Distribution Version 1.30

My first question is what is the deal with the different versions of OMD?

and my second question is what is the upgrade path for my original OMD server to 1.2.8p14-cre? Is it as simple as installing check-mk-raw-1.2.8p14_0.deb and then do a omd update to 1.2.8p14?

Cheers,

Will

As far as the OMD version discrepancy goes, I can’t really speak for that. I can confirm that the same thing happened to me when I upgraded to cmk 1.2.8 enterprise.

The upgrade path for me was as follows:

omd cp site test_site

omd upgrade test_site

Then I logged into the test_site and look for issues. A bulk inventory in WATO can bring out the problems.

su - test_site

cmk -U

Can also show some more specific errors.

Personally, I ran into some custom plugins that needed some code changes. After I figured out what those were, I circled back, backed up and upgraded my real site:

omd cp site site_bak

omd upgrade site

Then I just diff’d what I did in my test site. Once I was satisfied that my site worked as it should, I dropped the test site

omd rm test_site

~joe

···

On Dec 9, 2016 6:19 AM, “William” willay@gmail.com wrote:

Afternoon list,

Our original installation of check_mk was done via OMD downloaded from http://omdistro.org/ which has been fine, we have upgraded a couple of versions and now reside on 1.30.

This puts us on check_mk v 1.2.6p12, I would like to use 1.2.8 (or latest stable) and all the wonders that has but I believe the official advice is to not to manually upgrade check_mk and stick to omd update.

Sooo now I’m looking at the check_mk website, I can grab the latest raw deb file, however when I installed it on a test box to see what was going on omd version sez:

OMD - Open Monitoring Distribution Version 1.2.8p14.cre

And on my original server since the upgrade I get:

OMD - Open Monitoring Distribution Version 1.30

My first question is what is the deal with the different versions of OMD?

and my second question is what is the upgrade path for my original OMD server to 1.2.8p14-cre? Is it as simple as installing check-mk-raw-1.2.8p14_0.deb and then do a omd update to 1.2.8p14?

Cheers,

Will


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Hi William,

since the release cycle of OMDistro was veeery long, Matthias Kettner started releasing its own packages independent from the OMDistro team. There's one distribution release for every check_mk version, so you can always be up to date. Since the OMDistro and CRE distributions are independent, they are enumerated differently. CRE has the same release number as the Check_MK version it contains.

For the update, you can use the exact same commands and procedure as with OMDistro and, as you guessed, you can update from OMD 1.30 to the latest CRE in a single step. You will however have to pay attention to incompatible changes to the checks. You will have to re-inventorize these checks or modify certain rules. You can list the incompatible changes here: http://mathias-kettner.de/check_mk_werks.php

Beginning in 1.2.8, Check_mk also shows those changes in the upper left hand corner.

HTH,
Dominik

http://www.wieland-electric.com/de/aktuelles/messen-und-termine

Wieland Electric GmbH
Sitz: Brennerstrasse 10-14, D-96052 Bamberg
Geschaeftsfuehrer: Dr. Oliver Eitrich, Dr. Ulrich Schaarschmidt
Registergericht: AG Bamberg HRB 105

Der Inhalt dieser Mail enthaelt moeglicherweise vertrauliche Informationen und ist ausschliesslich fuer den bezeichneten Adressaten bestimmt.
Wenn Sie nicht der richtige Adressat sind, teilen Sie dem Absender bitte den Erhalt der Mail mit und loeschen Sie die Mail.

The content of this mail may contain confidential information and is intended solely for the designated addressee.
If you are not the intended addressee, then please inform the sender the receipt of this mail and delete the E-Mail.

···

Von: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de] Im Auftrag von William
Gesendet: Freitag, 9. Dezember 2016 13:05
An: checkmk-en@lists.mathias-kettner.de
Betreff: [Check_mk (english)] confused with OMD versions (and upgrade path)

Afternoon list,

Our original installation of check_mk was done via OMD downloaded from http://omdistro.org/ which has been fine, we have upgraded a couple of versions and now reside on 1.30.

This puts us on check_mk v 1.2.6p12, I would like to use 1.2.8 (or latest stable) and all the wonders that has but I believe the official advice is to not to manually upgrade check_mk and stick to omd update.

Sooo now I'm looking at the check_mk website, I can grab the latest raw deb file, however when I installed it on a test box to see what was going on omd version sez:

OMD - Open Monitoring Distribution Version 1.2.8p14.cre

And on my original server since the upgrade I get:

OMD - Open Monitoring Distribution Version 1.30

My first question is what is the deal with the different versions of OMD?

and my second question is what is the upgrade path for my original OMD server to 1.2.8p14-cre? Is it as simple as installing check-mk-raw-1.2.8p14_0.deb and then do a omd update to 1.2.8p14?

Cheers,

Will

Thank you for the information.

After a quick test on a cloned VM I went for it, here are the steps I remember for anyone else having issues:

snapshot vm

turned off everything in master control

su - sitename

omd stop

as root:

wget latest file (http://mathias-kettner.com/check_mk_download_version.php?HTML=yes&version=1.2.8p14&edition=cre)

apt-get update

apt-get install gdebi

gdebi

su - sitename

omd update

select update, merge files

omd start

cmk -I (wasnt sure about this step but heyho)

fixed all the broken things via wato

turn notifications back on

···

On 9 December 2016 at 13:07, Eismann Dominik Dominik.Eismann@wieland-electric.com wrote:

Hi William,

since the release cycle of OMDistro was veeery long, Matthias Kettner started releasing its own packages independent from the OMDistro team. There’s one distribution release for every check_mk version, so you can always be up to date. Since the OMDistro and CRE distributions are independent, they are enumerated differently. CRE has the same release number as the Check_MK version it contains.

For the update, you can use the exact same commands and procedure as with OMDistro and, as you guessed, you can update from OMD 1.30 to the latest CRE in a single step. You will however have to pay attention to incompatible changes to the checks. You will have to re-inventorize these checks or modify certain rules. You can list the incompatible changes here: http://mathias-kettner.de/check_mk_werks.php

Beginning in 1.2.8, Check_mk also shows those changes in the upper left hand corner.

HTH,

Dominik

http://www.wieland-electric.com/de/aktuelles/messen-und-termine

Wieland Electric GmbH

Sitz: Brennerstrasse 10-14, D-96052 Bamberg

Geschaeftsfuehrer: Dr. Oliver Eitrich, Dr. Ulrich Schaarschmidt

Registergericht: AG Bamberg HRB 105

Der Inhalt dieser Mail enthaelt moeglicherweise vertrauliche Informationen und ist ausschliesslich fuer den bezeichneten Adressaten bestimmt.

Wenn Sie nicht der richtige Adressat sind, teilen Sie dem Absender bitte den Erhalt der Mail mit und loeschen Sie die Mail.

The content of this mail may contain confidential information and is intended solely for the designated addressee.

If you are not the intended addressee, then please inform the sender the receipt of this mail and delete the E-Mail.

Von: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de] Im Auftrag von William

Gesendet: Freitag, 9. Dezember 2016 13:05

An: checkmk-en@lists.mathias-kettner.de

Betreff: [Check_mk (english)] confused with OMD versions (and upgrade path)

Afternoon list,

Our original installation of check_mk was done via OMD downloaded from http://omdistro.org/ which has been fine, we have upgraded a couple of versions and now reside on 1.30.

This puts us on check_mk v 1.2.6p12, I would like to use 1.2.8 (or latest stable) and all the wonders that has but I believe the official advice is to not to manually upgrade check_mk and stick to omd update.

Sooo now I’m looking at the check_mk website, I can grab the latest raw deb file, however when I installed it on a test box to see what was going on omd version sez:

OMD - Open Monitoring Distribution Version 1.2.8p14.cre

And on my original server since the upgrade I get:

OMD - Open Monitoring Distribution Version 1.30

My first question is what is the deal with the different versions of OMD?

and my second question is what is the upgrade path for my original OMD server to 1.2.8p14-cre? Is it as simple as installing check-mk-raw-1.2.8p14_0.deb and then do a omd update to 1.2.8p14?

Cheers,

Will