Solved

can't migrate 2.8 centos7 databases to debian11 VM

zach
Badge +3

i want to migrate from Centreon 2.8 on centoOS7 to Centreon 23.10 on Debian 11.
While the whole installation, and webinstall went well, following that documentation , as soon as i try to transfer my databases, as indicated i get the following error on the login page of my server :


Error while searching for the widgets version of the Centreon platform
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'centreon.provider_configuration' doesn't exist
Error while searching authentication tokens

Not only that, but i can’t log back with the credentials used on the old server, neither the one i was using before dumping my databases.

I checked both /etc/centreon/conf/pm and /etc/centreon/centreon.conf.php, on both servers and they were using the same credentials on both.

During the webinstall i entered the corresponding credentials for the admin profile.
If you also need it, i’m running both on VMWare.
I actually rolled back the new server on a snapshot who’s at the correctly ( or seemingly) configured webinstall, just before the databases dump.

But don’t worry, i can perfectly recreate it. ( which is kind of the elephant in the room).

If any of you have any clue, let me know, it’s been weeks i’m fighting with this.

icon

Best answer by zach 2 May 2024, 08:43

View original

12 replies

Laurent
Rank
Userlevel 6
Badge +18

Hi @zach , you must be in Centreon 2.8.32 on you old server before to start migration.

Then when you install your new Centreon central, finish web wizard installation with previous credentials used on your 2.8 server and reinstall “centreon-web” package to have possibility to execute update wizard.

import your dump and access to the web interface of the new server, you must have the update wizard to update your DB.

zach
Badge +3

Hi @zach , you must be in Centreon 2.8.32 on you old server before to start migration.

Then when you install your new Centreon central, finish web wizard installation with previous credentials used on your 2.8 server and reinstall “centreon-web” package to have possibility to execute update wizard.

import your dump and access to the web interface of the new server, you must have the update wizard to update your DB.

i’m on centreon 2.8.28. it’s a production server, so, i don’t really want to stop it, or take the risk to break it down.

I may want to create a copy of the server, but can’t for now.

thanks for your answer thought, i’ll use it whenever i could create a copy.

zach
Badge +3

Hi @zach , you must be in Centreon 2.8.32 on you old server before to start migration.

Then when you install your new Centreon central, finish web wizard installation with previous credentials used on your 2.8 server and reinstall “centreon-web” package to have possibility to execute update wizard.

import your dump and access to the web interface of the new server, you must have the update wizard to update your DB.

Well, @Laurent , it appears that from the yum.centreon.com page, the latest version is 21.10.

And, on packages.centreon.com i can browse freely all the packages, but that would mean installing them one by one, with the corresponding version of each.

The docs.centreon.com don’t seem to handle this type of process anywhere.

Lastly, i have on the old centreon doc something that could help me, but, once again, the archives are incomplete.

I hope that i just don’t know how and where to browse, but the only solution that could work, is what i suggested above, installing packages one by one. And it’s such a tidious process i’m not sure i want to go through it.

If any of you happen to know an old mirror or archive, or even an unofficial one, i’ll gladly take the link.

Laurent
Rank
Userlevel 6
Badge +18

you should have the possibility to start with 2.8.28

You need to follow this procedure: https://docs.centreon.com/docs/migrate/migrate-from-el-to-el/

 

zach
Badge +3

you should have the possibility to start with 2.8.28

You need to follow this procedure: https://docs.centreon.com/docs/migrate/migrate-from-el-to-el/

 

i’ll try it this morning, thanks.

zach
Badge +3

althought it sound and look like it could solve my problem, i currently don’t have any other centos VM handy. And considering that, i woudnl’t be able to install 2.8.32 still. Since no archives are left.
 

While i’m waiting for my VM to be set ( i’m not the one in charge of the VM, sadly ) I tried this : https://docs.centreon.com/docs/22.04/upgrade/upgrade-from-3-4/

 

I’m stuck at the update of centreon\* and php-pecl-gnupg.

it seemed like just updating provoked dependency conflict, so instead i removed all centreon packages, and reinstalled all. When it indicated me that the packages have been updated but couldn’t be installed is installed them manually:

 

yum install centreon\* php-pecl-gnupg

 

And now, i’m left with something else. It seems like the packages are in conflict, because they try to install on the same files :

Transaction check error:
  file /usr/lib/systemd/system/cbd.service conflicts between attempted installs    of centreon-collect-22.04.5-1.el7.x86_64 and centreon-broker-cbd-22.04.6-1.el7.x   86_64
  file /var/log/centreon-engine/centengine.debug conflicts between attempted ins   talls of centreon-collect-22.04.5-1.el7.x86_64 and centreon-engine-daemon-22.04.   6-1.el7.x86_64
  file /var/log/centreon-engine/centengine.log conflicts between attempted insta   lls of centreon-collect-22.04.5-1.el7.x86_64 and centreon-engine-daemon-22.04.6-   1.el7.x86_64
  file /var/log/centreon-engine/retention.dat conflicts between attempted instal   ls of centreon-collect-22.04.5-1.el7.x86_64 and centreon-engine-daemon-22.04.6-1   .el7.x86_64
  file /var/log/centreon-engine/status.dat conflicts between attempted installs    of centreon-collect-22.04.5-1.el7.x86_64 and centreon-engine-daemon-22.04.6-1.el   7.x86_64

 

Note that they always try to install the 22.04 version, so, i feel like i’m close to have a solution, that may only stand on a house of cards, but still, a solution.

 


 

zach
Badge +3

rolled back my VM. still following the same procedure.

i’m still stucked at the same point, after updating centreon and php80.

gorgoned isn’t installed.

Tried to install gorgoned via yum install gorgoned.

No package gorgoned available.

I consider this migration, now impossible, for as much as i know. I won’t lock the topic so if anyone happen to find a solution.

zach
Badge +3

false alert. Just logged back on my web interface and updated to 2.8.32.

seems like i could finally follow up with what @Laurent suggested earlier.

zach
Badge +3

Hi @zach , you must be in Centreon 2.8.32 on you old server before to start migration.

Then when you install your new Centreon central, finish web wizard installation with previous credentials used on your 2.8 server and reinstall “centreon-web” package to have possibility to execute update wizard.

import your dump and access to the web interface of the new server, you must have the update wizard to update your DB.

by the way @Laurent , if you could re-explain it more clearly and specifically, i’ll be thankful, since there’s bits i didn’t understand.
Should i reinstall the centreon-web package on the old or new server ?

zach
Badge +3

the centreon.provider-configuration table is still missing on the ol ( 2.8.32) version. I don’t know how it’ll turn out with the dump. I’ll make a snapshot first.

Laurent
Rank
Userlevel 6
Badge +18

Hi @zach on the new Centreon central server, after finishing to install it, including install wizard, please reinstall centreon-web package (dnf reinstall centreon-web), to reinstall files on this server that will allow to perform upgrade wizard after importing your dump on the new DBMS.

zach
Badge +3

okay, prolem solved. Let’s recap.

For anyone who want to follow the same path, here’s what i did and here’s how i made it work.

First, get yourself a Debian 11 device (i recommend a virtual machine so you can make snapshots and rollbacks.

You’ll need to follow this procedure , whichin itself don’t contain that much tricky things. It’s straightforward, just be sure to follow step by step.

If you’re using a proxy, just be sure that it’s correctly configurated in the wget file, and enter the proxy parameters on the command whenever you’re using curl (configuring the file didn’t worked for me, for curl ) ==> curl -x <http://yourproxy> <http://your.file/you/want/to.download>

Second, as @Laurent mentionned, if your version is as old as 2.8.28, like for me, you’ll need to follow this procedure for upgrading your old server to 2.8.32.  personnally i stopped just before the “additional actions” .

I don’t really know how my problem solved themselves at this point, but all i can tell is follow the procedure, step by step, and at the end, refresh your old server.

 

Finally, the databases migration :

you’ll need to follow this final procedure for migration. 

BUt first, as @Laurent precised apfter the installation of the new centreon server, deinstall and reinstall the centreon-web packages. if you want, you could also refresh the new server webpage, to see it in progress.

 

Hi @zach on the new Centreon central server, after finishing to install it, including install wizard, please reinstall centreon-web package (dnf reinstall centreon-web), to reinstall files on this server that will allow to perform upgrade wizard after importing your dump on the new DBMS.

 

If you did like me, and decided to dump before reinstalling the centreon-web, there might be a problem with the webserver upgrading from 2.8.32 to 23.10, specifically at the 20.10.12 upgrade. 

 

the file is located at /usr/share/centreon/www/install/php/Update-20.10.12.php . The error i got was that the file couldn’t delete the columns contact_platform_data_sending.
I tried modifying the rights of the centreon user in my databases, so it could delete the column.
I didn’t worked.

what worked for me, is that after trying bits and bops, i decided to do it manually. I first opened the file, commented the line trying to delete the specific columns, then, went into the database and deleted the column myself.

After this, i refreshed my new server, and it all went well.

And please, for the sake of everyone sanity, whenever you’re doing such an update/upgrade/migration use the same credentials which were used before. Or at least, note down the ones who works.

 

I hope this was informative enough, if anyone have any other questions regarding this process i followed, i’ll be glad to answer.

Reply


Terms & ConditionsCookie settings