Errors while migrate Centreon in Centos to Debian 12.

hello

what versions (centreon and centos) were installed on the old platform and what centreon version did you install on the new platform?

Hello

You should try to upgrade platform A before migrating to B and try to have the same version (on the latest release) on both sides.

CentOS Linux release 7.9.2009 (Core)//Centreon 22.04.24 on the old

Debian 12//Latest version of centreon in the new.

 

Thank you very much.

Yes, I'll try. The problem is that since it's such an old CenOS, the mirrors don't download new things, and I have them in "Vault." I don't know if I can update Centron to the latest version.

Thank you very much.

Añado el log de error.

ass":null,"function":null},"request_infos":{"url":null,"http_method":null,"server":null,"referrer":null}},"exception":null,"custom":null}}
[2025-03-20T09:14:47+0100] [ERROR] [Core\Security\ProviderConfiguration\Application\UseCase\FindProviderConfigurations\FindProviderConfigurations:76]: Some properties doesn't match the json schema :[authentication_conditions] The property authentication_conditions is required [] The property trusted_client_addresses is not defined and the definition does not allow additional properties [] The property blacklist_client_addresses is not defined and the definition does not allow additional properties [] The property contact_group_id is not defined and the definition does not allow additional properties [] The property claim_name is not defined and the definition does not allow additional properties  {"trace":"#0 /usr/share/centreon/src/Core/Security/ProviderConfiguration/Infrastructure/Repository/DbReadConfigurationRepository.php(206): Centreon\\Infrastructure\\Repository\\AbstractRepositoryDRB->validateJsonRecord()\n#1 /usr/share/centreon/src/Core/Security/ProviderConfiguration/Infrastructure/Repository/DbReadConfigurationRepository.php(98): Core\\Security\\ProviderConfiguration\\Infrastructure\\Repository\\DbReadConfigurationRepository->loadCustomConfigurationFromConfiguration()\n#2 /usr/share/centreon/src/Core/Security/ProviderConfiguration/Infrastructure/Repository/DbReadConfigurationRepository.php(134): Core\\Security\\ProviderConfiguration\\Infrastructure\\Repository\\DbReadConfigurationRepository->getConfigurationByType()\n#3 /usr/share/centreon/src/Core/Security/ProviderConfiguration/Application/UseCase/FindProviderConfigurations/FindProviderConfigurations.php(54): Core\\Security\\ProviderConfiguration\\Infrastructure\\Repository\\DbReadConfigurationRepository->findConfigurations()\n#4 /usr/share/centreon/src/Core/Security/ProviderConfiguration/Infrastructure/Api/FindProviderConfigurations/FindProviderConfigurationsController.php(44): Core\\Security\\ProviderConfiguration\\Application\\UseCase\\FindProviderConfigurations\\FindProviderConfigurations->__invoke()\n#5 /usr/share/centreon/vendor/symfony/http-kernel/HttpKernel.php(181): Core\\Security\\ProviderConfiguration\\Infrastructure\\Api\\FindProviderConfigurations\\FindProviderConfigurationsController->__invoke()\n#6 /usr/share/centreon/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\\Component\\HttpKernel\\HttpKernel->handleRaw()\n#7 /usr/share/centreon/vendor/symfony/http-kernel/Kernel.php(197): Symfony\\Component\\HttpKernel\\HttpKernel->handle()\n#8 /usr/share/centreon/api/index.php(47): Symfony\\Component\\HttpKernel\\Kernel->handle()\n#9 {main}"}
^\Abandona
 

I've more or less managed to do it by following the process, thank you so much!I just need to fix the poller, since for some reason it's giving me an error, and I'm a bit lost.

 I've more or less managed to do it by following the process, thank you so much!I just need to fix the poller, since for some reason it's giving me an error, and I'm a bit lost.

that yellow timestamp means the engine of the poller (centengine) is not correctly sending data to the broker on the central (service cbd)

as it is on the same machine, and not a remote poller, the issue may lie in the confg, have you regenerated and pushed the config on the local poller (central) and restarted the services (centengine, cbd, gorgoned) as it is required after an update

(also be sure to not have any warning when you generate the config in the “export configuruation” button, there may be some files issue to fix)

if that doesn’t fix, then there are some logs to parse to identify what is broken, 

I get this log of centengine.log 
2025-03-21T08:44:37.746+01:00] [tcp] [error] [17046] TCP: Connection refused to localhost:5669
[2025-03-21T08:44:37.746+01:00] [processing] [error] [17046] failover: global error: failover: 'central-module-master-output' cannot connect endpoint.
Maybe this is causing the problem.

When i restart via web, I’dont get any errors, and all the related services are enabled and running. No warnings or errors.
 

tcp 5669 is the listening port for “cbd”, the broker process, it is configured here

in the “central-broker-master”

be sure it is this port

also be sure the cbd service is running and that port is listening on 0.0.0.0:5669, and that you don’t have a local firewall that could prevent you to connect locally

try to disable any firewall and selinux temporarily, to see if can come from one of this thing, no idea what is running by default on debian12 

tcp 5669 is the listening port for “cbd”, the broker process, it is configured here

 

in the “central-broker-master”

be sure it is this port

 

also be sure the cbd service is running and that port is listening on 0.0.0.0:5669, and that you don’t have a local firewall that could prevent you to connect locally

try to disable any firewall and selinux temporarily, to see if can come from one of this thing, no idea what is running by default on debian12 

Thank you very much for your response. I checked it and it was correct. (Local Poller 127.0.0.1)Finally, what was giving me problems was that my old server was connected to Grafana, and when I migrated, everything was misconfigured, and I was having problems with the poller. Several other errors with various plugins were also causing problems. The only thing left to fix is ​​that the widgets I had applied to the custom views are giving me a 500 error and not displaying.

Solved!