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