O.K. it’s maybe a simple problem for expeerts but i am getting crazy with this.
I want to update my installation (only one site) from 1.5x to 1.6x. The problem is that 1.6 is not supported on Debian 7 (current server). So i can not upate it to 1.6x before the backup.
If i try to restore the 1.5x backup to a new Ubuntu 20.04 machine with 1.6x installed i get an error to install the 1.5 at first. The problem is that 1.5 is not supported on this system.
I hoped that i could at least copy all the hosts to the new system but i do not know how without a backup.
I found a “werk” about this issue but no sollution?
Is there any help available?
Hallo,
why not update debian 7 to 8 to 9 to 10 step by step to get an actual system.
Ralf
@rprengel i am trying this but the result is:
Es wurden 1.132 MB in 4 min 18 s geholt (4.386 kB/s).
apache2-bin:amd64 conflicts with apache2.2-bin:amd64
apache2-bin:amd64 conflicts with apache2.2-common:amd64
Lese Changelogs… Fertig
apt-listchanges: Sende E-Mail an root: apt-listchanges: Neuigkeiten für omd
Extrahiere Vorlagen aus Paketen: 100%
Vorkonfiguration der Pakete …
(Lese Datenbank … 372120 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von check-mk-raw-1.2.6p10 …
Stopping all OMD monitoring sites using omd version 1.2.6p10.cre:
Entfernen von check-mk-raw-1.2.8p17 …
Stopping all OMD monitoring sites using omd version 1.2.8p17.cre:
Entfernen von check-mk-raw-1.2.8p4 …
Stopping all OMD monitoring sites using omd version 1.2.8p4.cre:
Entfernen von check-mk-raw-1.4.0p26 …
Stopping all OMD monitoring sites using omd version 1.4.0p26.cre:
Entfernen von check-mk-raw-1.4.0p9 …
Stopping all OMD monitoring sites using omd version 1.4.0p9.cre:
Entfernen von check-mk-raw-1.5.0p13 …
Site cl is still using this version!
dpkg: Fehler beim Bearbeiten von check-mk-raw-1.5.0p13 (–remove):
Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
Trigger für man-db werden verarbeitet …
Fehler traten auf beim Bearbeiten von:
check-mk-raw-1.5.0p13
E: Sub-process /usr/bin/dpkg returned an error code (1)
There seems to be a problem with omd allthough this version is supported on Debian 7 and 8.
I’m afraid you have the worst possible combination: old Debian too old for new cmk, new Ubuntu too new for old cmk.
I think you need to manually install (using dpkg --install ...deb) the same version (check-mk-raw-1.5.0p13) but using the package for the matching Debian release. This would be check-mk-raw-1.5.0p13_0.jessie_amd64.deb. Probably followed by apt-get -f install to fix the dependencies. Do this after an modifiying the sources.list and after running apt-get update && apt-get upgrade but before running apt-get dist-upgrade.
If you can’t find the ...p13...deb for download, then first update to the latest 1.5 patch (p24) while still on Debian 7 – I would recommend this anyway: to first update to the latest 1.5 patch release before then upgrading to 1.6.
…addon - it seems to me that with the dist-upgrade the old 1.5.0p13 shall be removed. This is not possible as it is in use. so now i will try to remove omd - i do have a backup, do the dist-upgrade and than reinstall 1.5.0p13 to debian 8…
Right, dist-upgrade wants to remove it. But you should be able to “update” it to the jessie package first (keeping the version number the same).
i used
omd -f rm site
to remove the site.
dist-upgrade is now running. if i still have a stable system after that i will re-install 1.5.0p13 for Jessie, restore my backup, upgrade to 1.5.0p24 ant than to 1.6.0p15.
And if this worked fine i will make a fresh backup. This should be restorable to ubuntu 20.04.
…
so, as far as i can see now, the main problem was simply that 1.5.0p13 on “Wheezy” had to be uninstalled before dist-upgrade to “Jessie”.
The way how to do the update for check_mk is:
Backup the site with release 1.5.0p13 (omd backup …)
Remove the site from Wheezy (omd -f rm ‘sitename’)
Do the dist-upgrade and after that check dependencies (apt-get -f install)
Remove old packages (apt-get autoremove)
Install 1.5.0p13 for Jessie (dpkg -i check-mk-raw-1.5.0p13_0.jessie_amd64.deb)
Restore the site from the backup (omd restore …)
Install 1.5.0p24 for Jessie (dpkg -i check-mk-raw-1.5.0p24_0.jessie_amd64.deb)
Login to your site (su - sitename’)
omd stop - omd update - omd version - omd start
do the same for check-mk-raw-1.6.0p15_0.jessie_amd64.deb
If this worked also, the last step is to get a fresh backup for 1.6.0p15 that i can restore to the new ubuntu 20.04 system…
Thank god it’s friday …
Good to hear it works for you. But as I said, you do not necessarily have to uninstall the package. In fact, one could probably just update it along with the rest of the system, if only it was available to apt in a repository. Since it isn’t, it has to be “upgraded” manually (from wheezy to jessie version but keeping the cmk version the same), at the right step in the distribution upgrade.
Been there, done that on many systems. No backup/delete/restore required.
(Of course, having a working backup is always a good thing 
)
You can avoid removing the installed site by stopping the site and remove the “version” link in the site directory (so remove /omd/sites//version). After this you can remove the checkmk package, do the debian upgrade and install the same checkmk version on the new distribution. Add the “version” link back to the site (do not forget the trailing / ) and you should be fine.
1 Like
@uwoehler’s way is also my preferred doing for distribution upgrades.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.