Skip to main content

Hi,

since I have updated my server from SL7/Centreon 19 to RH8/Centreon 24 , if I change the IP of a host, the update doesn’t apply when I export the conf as usual. The check continue with the old IP.

Then, I need to go to the server shell and restart the centreon service to make it work.

Any idea ? Did I miss something during the update process ?

Regards,

JF

Hello

do you have any warning during the export of the configuration in the poller page?

if so, please paste them here

 


Hi,

No any warning or error during export :

 

Préparation de l'environnement... OK
Génération des fichiers... OK
Déplacement des fichiers... OK
Redémarrage de l'ordonnanceur... OK
- ] Central
Configuration mechanism used: legacy
Reading main configuration file '/var/cache/centreon/config/engine/1/centengine.DEBUG'.
Reading resource file '/var/cache/centreon/config/engine/1/resource.cfg'
Checking global event handlers...
Checking obsessive compulsive processor commands...

Checked 26 commands.
Checked 2 connectors.
Checked 11 contacts.
Checked 0 host dependencies.
Checked 0 host escalations.
Checked 13 host groups.
Checked 228 hosts.
Checked 0 service dependencies.
Checked 0 service escalations.
Checked 5 service groups.
Checked 2624 services.
Checked 2 time periods.
Total Warnings: 0
Total Errors: 0

hmm, you are not the only one with that issue, there is another post

Need to reload/restart centengine after export configuration | Community (centreon.com)

unfortunately I don’t know where are the logs for that pushing process

clearly the file are generated and then pushed in the correct folder, but you don’t get the “reload” or “restart” command

 

could try to

tail -f /var/log/centreon-engine/centengine.log

and from the UI, just do the export configuration with “reload” 

when I do that on my central I get these 2 lines and the modification are applied.

 

also, just to be sure “ ll /etc/centreon-engine/ ”

and check if the files have been modified with the timestamp of when you pushed, and that the files have permissions like these

 

 

there may be other issues like Gorgoned not having the correct whitelist commands to reload the service, but I have no idea how to check/debug that, what is your gorgoned log saying ? (/var/log/centreon-gorgoned/)


Hi,
Nothing happens in /var/log/centreon-engine/centengine.log during the export and reload of the config.

But the date of the .cfg files is updated.

 

Thanks,

JF


hello

at this point, the only thing I can tell is that the “reload/restart” command is not sent, my guess is as good as yours, i would blame gorgoned somehow but I don’t know how to debug it.

since installing/upgrading have you rebooted the central server, or restarted the gorgoned and cbd services?

if you didn’t, just try a quick reboot or ‘systemctl restart gorgoned cbd centreon centengine” (be sure that they are also enabled, maybe the gorgoned services is not running

(or just reboot and verify the services are running with systemctl status)

 

next you would need a centreonian or someone else.

 


Thanks for you help.

The only thing I found for now is this in gorgoned.log :

2024-09-25 15:56:56 - DEBUG - legacycmd] Processing file '/var/lib/centreon/centcore//1727272613.4132-externalcommand.cmd_read'
2024-09-25 15:56:56 - INFO - legacycmd] Handling command 'RELOAD', Target: '1'
2024-09-25 15:56:56 - DEBUG - legacycmd] internal message: COMMAND] fe4e60ce0ab94cd07d80f62e0d40860ce66d5ceb08d03c76da73f69c2ff479d6695f1d967c3b06bd1b2a7fd8707c64f8dc3575e1e484334153e9873c62acacbd] 1] {"content"::{"command":"sudo service centengine reload","metadata":{"centcore_proxy":1,"centcore_cmd":"RELOAD"}}],"logging":0}
2024-09-25 15:56:56 - DEBUG - core] Message received internal - COMMAND] fe4e60ce0ab94cd07d80f62e0d40860ce66d5ceb08d03c76da73f69c2ff479d6695f1d967c3b06bd1b2a7fd8707c64f8dc3575e1e484334153e9873c62acacbd] 1] {"content"::{"command":"sudo service centengine reload","metadata":{"centcore_proxy":1,"centcore_cmd":"RELOAD"}}],"logging":0}
2024-09-25 15:56:56 - DEBUG - legacycmd] Event: ACK] ] {"code":1,"data":{"error":"unknown_action","message":"action 'COMMAND' is unknown"}}


Same issue here, i just migrate a 24.04.6 Debian 11 to Debian 12.

Under Debian 11 no issue, with the new Debian 12 installation, conf was not changed after configuration and export poller. There is no error. Same files than Debian 11, i checked again and again permissions without find anything …

There is just this issue, Centreon works fine otherwise.


SOLVED :

40-gorgoned.yaml was missing in /etc/centreon-gorgone/config.d

Take your gorgone conf with web interface on poller copy/paste to the file


Reply