+4
I’ve imported centreon and centreon_storage from my RHEL7 server to a new RHEL8 server configured with Centreon 21.04.
problems
- the GUI does not display any HOSTS or SERVICES = “0” but my poller is running
- if I export the poller (Move/Restart/Post), The Console displays the progress at 0%.
Any ideas where I should look to fix this?
Jacques
Best answer by gespada
View originalHello
You just use a new server with a new OS RHEL8 and you install a 21.04 with the dump of the older platform only ?
You don't do any change on your Pollers (OS, Centreon Version) pollers are on 21.04.x supported by your 21.04.x you installed on your Central (https://docs.centreon.com/docs/21.04/releases/centreon-core/#21042-1) ?
You use Gorgone for the connection between your Central and your Poller(s) or SSH ?
Maybe, you just do redeploy your gorgone configuration because you change the Central ? (a new thumbprint with the new central)
When you solved the communication problem, i think you do upgrade your platform to a supported version https://docs.centreon.com/docs/releases/lifecycle/#maintenance-table-for-centreon-versions
Greg,
+4
Good day,
I keep getting the following error with my installation of Centreon 21.04. Any idea what needs to be done?
Currently installing database and generating cache... please do not interrupt this process.
| Step | Status |
|---|---|
| Setting up configuration file | OK |
| Configuration database | createTables.sql Line 21:Cannot execute query : /*!40101 SET character_set_client = @saved_cs_client */; |
I don't understand your last post versus the first.
For the first have you follow this guidelines : https://docs.centreon.com/docs/21.04/migrate/migrate-from-20-x/#upgrade-centreon
Most particulary the last indication with the replacement of IP adresse ?
Could you share some logs of gorgone /var/log/centreon-gorgone on Central and Poller(s) and also /var/log/centreon-engine
+4
I followed the document guidelines and was able to move my Centreon 21.04 on RHEL 7 to Centreon 21.10 on RHEL. My problem now is with my poller and was wondering if you could provide me with more info on why
centengine stutus point to “/usr/sbin” and not “/usr/lib64/nagios/plugins” for check.
+4
My working Centreon 21.04 on RHEL 7 uses “/usr/lib64/nagios/plugins”. My plugins were moved to my new RHEL 8 server to “/usr/lib64/nagios/plugins”. I really do not want to use “/usr/sbin” to hold my plugins,
Hi,
The binary centengine path is /usr/sbin/ like you show on your screenshots.
You probably speak Ressources Macros
https://docs.centreon.com/fr/docs/21.10/monitoring/basic-objects/macros/#les-macros-de-ressources
https://docs.centreon.com/docs/21.10/monitoring/basic-objects/macros/#resource-macros
You associate a Ressource Macros to a path.
Regards,
Greg
+4
merci … ça aide beaucoup!
+4
Maintenant j’ai cette erreur
# /usr/lib64/nagios/plugins/check_nrpe
/usr/lib64/nagios/plugins/check_nrpe: error while loading shared libraries: libcrypto.so.10: cannot open shared object file: No such file or directory
Pourquoi?
Re,
Vous étiez sur qu'elle version de NRPE sur la RHEL 7.x ?
Peut être le NRPE (version 2.15) centreon-nrpe
En RHEL 8.x vous devez être obligatoirement en NRPE3 (version 4.0.3) centreon-nrpe3
Le plugin est peut être pas installé ou plutôt mal installé ?
+4
J’ai fait une mise à jour de NRPE qui règle mon problème de nrpe. J’ai aussi copié /etc/centreon/centreon-engine de mon RHEL 7 et fait une mise à jour de mon check_ping qui à réglé mon problème de “0” Service et Hosts.
Maintenant, tout est fonctionnel excepté pour mon “export” ou “reload” qui demeure à 0%.
Bonjour,
Comme vous avez copié le contenu de /etc/centreon/centreon-engine vous avez peut être un problème de droit, sur le(s) répertoire(s) si le blocage est sur la génération des fichiers.
Pouvez vous vérifier dans les logs /var/log/centreon* que vous n'avez pas des problèmes de droits/permissions ?
If you talk in english, maybe more people can help :)
+4
No Problem … Basically I managed to migrate my Centreon 21.04 RHEL7 to Centreon 21.10 RHEL8. My problem is with the “broker” which doesn’t “export”.
The copying of RHEL7:etc/centreon-engine solved “0” hosts and “services”. Now, I need to understand why the export doesn’t work but the “broker” updates if I reboot the server.
The following is a “tail” of my /var/log/centreon-engine/centreon-.log file which is completely normal.
I noticed that my /var/cache/centreon/config “broker” directory doesn’t update (see date)
Notice the “console” progress remains at “0”.
If you could help, that would be greatly appreciated.
Jacques
+4
I finally found the cause of my error with the “stalled” “Console 0% server problem”. The problem was with bad Hosts templates assigned to Window servers. Once I delete the templates and performed a “save” for each host, this enabled Centreon to export the config files at 100%.
Troubleshooting steps:
1- Did a duplicate of my poller and noticed that all “hosts” acquired a new “poller name” (ie. Central_1)
2- enabled and configured my new poller and disabled the original poller
3- changed the new poller name “Central_1” to “Central”
4- Selected the 1sr host and changed “Central_1” to “Central” and applied the “save” for the host
5- performed the “export” for the 1st host without any issues.
6- did the same for the 2nd, 3rd. etc,... hosts, and if the “export” didn’t work I disabled the host and retried the “export”. The disabled host would allow the “export” to work which made me look at the templates and noticed the “bad Hosts Templates”. I deleted the bad templates and reenabled the host and performed successfully the export.
======================================================
My next question is:
See /var/cache/centreon/config/engine/4/…
| Console | |
| Progress (100%) | |
| Preparing environment... OK Generating files... OK Moving files... OK Restarting engine... OK Executing command... OK | [ - ] Central Reading main configuration file '/var/cache/centreon/config/engine/4/centengine.DEBUG'. Reading resource file '/var/cache/centreon/config/engine/4/resource.cfg' |
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
