Skip to main content
Solved

Centreon is not running.

  • 5 July 2024
  • 7 replies
  • 53 views

Hello everyone,I am stuck with my centreon which despite several installations still does not want to start. When I export my configuration, I have no errors but it still remains stopped. So I don't have anything display-wise.I don't really know what to do anymore, because I updated it, restarted it, reinstalled it.If anyone knows what I should be looking for, because the logs don't tell me anything either, I'm interested.

Thanks

 

7 replies

Userlevel 6
Badge +20

Hi @louarn can you check is gorgoned process is alive:

systemctl status gorgoned

 

Badge +6

Hello,

Here is the output:

● gorgoned.service - Centreon Gorgone
   Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2024-07-18 20:25:58 CEST; 3h 5min ago
 Main PID: 1717946 (perl)
    Tasks: 48 (limit: 23238)
   Memory: 865.5M
   CGroup: /system.slice/gorgoned.service
           ├─1717946 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=>
           ├─1717957 gorgone-action
           ├─1717958 gorgone-httpserver
           ├─1717959 gorgone-proxy
           ├─1717960 gorgone-proxy
           ├─1717961 gorgone-proxy
           ├─1717962 gorgone-proxy
           ├─1717963 gorgone-proxy
           ├─1717964 gorgone-engine
           ├─1717965 gorgone-autodiscovery
           ├─1717967 gorgone-legacycmd
           ├─1717970 gorgone-cron
           ├─1717973 gorgone-nodes
           ├─1717976 gorgone-dbcleaner
           ├─1717977 gorgone-statistics
           └─1717978 gorgone-audit

Jul 18 20:25:58 centreon-central systemd[1]: Started Centreon Gorgone.
Jul 18 21:24:19 centreon-central sudo[1720772]: centreon-gorgone : PWD=/ ; USER=root ; COMMAND=/usr/sbin/service centengine reload
 

 

I don't really know what's changed because I've updated the server from version 2.8 to 24.

Poller is down and the database now has a problem. But I don’t see where …

Nothing in logs …

 

And I'm not talking about vmware errors …

CHECK_VMWARE_API CRITICAL - Server version unavailable at 'https://myserver:443/sdk/vimService.wsdl' at /usr/local/lib64/perl5/VMware/VICommon.pm line 705.

 

It’s a few complicated ...

Userlevel 6
Badge +20

Hi @louarn if you update from 2.8 did you perform move from centcore to gorgoned?

https://docs.centreon.com/docs/22.10/monitoring/monitoring-servers/communications/#change-communication-from-ssh-to-zmq

Badge +6

Hello,

No I didn’t do it.

My central is my poller too.

Userlevel 6
Badge +20

Since you move from Centreon Web 2.8, please check also this procedure : https://docs.centreon.com/docs/22.10/upgrade/upgrade-from-3-4/

Badge +6

I did all of that when I upgraded my centreon.

 

I think it’s dead .. Because for example, i can ping a server, but it doesn’t work in centreon.

Badge +6

New error … 

 

[root@centreon-central centreon_storage]# tail -F /var/log/centreon-gorgone/gorgoned.log | grep ERROR
2024-07-19 11:26:36 - ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - configuration missing
2024-07-19 11:27:36 - ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - configuration missing
2024-07-19 11:28:36 - ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - configuration missing
 

I don’t have any licence. Can I remove it ?

 

Do I need a central server separate from a collector? The central server could very well be the one running the probes, couldn't it?

Reply