Skip to main content

Hi,

I’m upgrading from Centreon 22 on Centos 7 to the latest version on Debian 12. I made a fresh install of Centreon and I used the Import/export module to import back all the data. Everything seems fine but I can’t start the colletor. When I export the configuration, everything is green and OK but it doesn’t start. Do any of you had this problem happen before? 

 

Here are screenshots: https://imgur.com/a/chJhkU1

 

Thanks a lot, 

Your poller don’t seem to be started in the first place, even if the configuration is properly exported.

Can you check this FAQ regarding poller issues ? My poller is down | Community


Your poller don’t seem to be started in the first place, even if the configuration is properly exported.

Can you check this FAQ regarding poller issues ? My poller is down | Community

Hi, thanks for your reply! I just followed the entire page you mentioned, every service is running as expected. Here is the status of the last two commands, everything looks fine to me:

 

root@centreon-2025:~# tail /var/log/centreon-broker/central-broker-master.log
[2025-09-18T14:01:44.574+02:00] [core] [info] multiplexing: 'central-broker-master-unified-sql' starts with 0 in queue and the queue file is disable
[2025-09-18T14:01:44.575+02:00] [core] [info] multiplexing: 'centreon-broker-master-rrd' starts with 0 in queue and the queue file is disable
[2025-09-18T14:01:44.576+02:00] [core] [info] multiplexing: engine started
[2025-09-18T14:01:44.578+02:00] [core] [info] Poller 'Central' with id 1 connected
[2025-09-18T14:01:47.512+02:00] [core] [info] Available connections cleaning: Operation canceled
[2025-09-18T14:01:47.513+02:00] [core] [info] Poller '' with id 0 connected
[2025-09-18T14:01:47.513+02:00] [core] [info] New incoming connection 'central-broker-master-input-2'
[2025-09-18T14:01:47.514+02:00] [core] [info] multiplexing: 'central-broker-master-input-2' starts with 0 in queue and the queue file is disable
[2025-09-18T14:02:06.881+02:00] [core] [info] main: configuration update requested
[2025-09-18T14:02:06.882+02:00] [core] [info] multiplexing: engine started

 

and :

 

root@centreon-2025:~# grep -i cbmod.so /var/log/centreon-engine/centengine.log
[1758180863] [25376] Event broker module '/usr/lib64/nagios/cbmod.so' initialized successfully
[2025-09-18T09:34:23.385+02:00] [events] [info] [25376] Event broker module '/usr/lib64/nagios/cbmod.so' initialized successfully
[1758180866] [25376] Event broker module '/usr/lib64/nagios/cbmod.so' deinitialized successfully
[2025-09-18T09:34:26.282+02:00] [events] [info] [25376] Event broker module '/usr/lib64/nagios/cbmod.so' deinitialized successfully
[1758180870] [25470] Event broker module '/usr/lib64/nagios/cbmod.so' initialized successfully
[2025-09-18T09:34:30.391+02:00] [events] [info] [25470] Event broker module '/usr/lib64/nagios/cbmod.so' initialized successfully


Hi ​@tch 

Can you try to export in Restart mode and then check the uptime of the centengine service?

systemctl status centengine

If the uptime doesn’t match the export timing, it means there is something wrong with Gorgone 

You can try to restart it with this command

systemctl restart gorgoned

And retry an export

Then check the gorgone logs
/var/log/centreon-gorgone/gorgoned.log

 

Hope it helps