Gorgone configuration file : Error when connecting to the Gorgone server

Hello everyone I had deployed a machine as a poller and connected it to centreon, then later i exported it to a different network and wanted to attach it to a different centreon server, however the command “/usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1’ was run succesfully and I could see the poller in the list when I went to add it, however when It came to the gorgoned file I click to copy the contents and I see the error above, I’m unsure what I’m supposed to do, I deleted the old gorgoned file and restarted the service on both the central and the poller, and redeployed the poller and added it again, still same issue, I’m unsure what I should do, I also deleted the log files and the key files:

rm -rf /var/lib/centreon-gorgone/.keys
rm -rf /var/log/centreon-gorgone/*

Page 1 / 1

@Thibault @Laurent Would you have any idea?thanks :c

Hi @xorya you said:

I click to copy the contents and I see the error above

which error?

@Laurent this “Gorgone configuration file : Error when connecting to the Gorgone server” i really cant seem to connect to the gorgone and see the config file at all, i removed the old config of the previous poller made it as if the machine is new and i still see the same error, cant generate the config file at all

@Laurent I see this in the log file for gorgoned “

proot@poller1 osadmin]# cat /var/log/centreon-gorgone/gorgoned.log

2025-05-07 11:07:38 ERROR - no such table: gorgone_information

2025-05-07 11:07:39 - ERROR no such table: gorgone_information

2025-05-07 11:07:39 ERROR no such table: gorgone_identity

2025-05-07 11:07:40 ERROR no such table: gorgone_identity

proot@poller1 osadmin]#”

Can you check on your central that gorgoned process is strted with httpserver module:

# systemctl status gorgoned| grep httpserver
             ├─1145859 gorgone-httpserver

@Laurent and on the central server i see this error in config file “

2025-05-13 14:44:47 ERROR Rautodiscovery] -class- host discovery cannot get host discovery jobs request error rcode: '500'] 0message: 'The license of th

e autodiscovery module is not valid']

2025-05-13 14:45:47 ERROR Rautodiscovery] -class- host discovery cannot get host discovery jobs - request error rcode: '500'] 0message: 'The license of th

e autodiscovery module is not valid']

2025-05-13 14:46:47 ERROR Rautodiscovery] -class- host discovery cannot get host discovery jobs request error rcode: '500'] 0message: 'The license of th

e autodiscovery module is not valid']

2025-05-13 14:47:47 ERROR Rautodiscovery] -class- host discovery

cannot get host discovery jobs request error rcode: '500'] 0message: 'The license of th

e autodiscovery module is not valid']

47e

full gorgoned modules on a central server:

# systemctl status gorgoned
● gorgoned.service - Centreon Gorgone
     Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; preset: disabled)
     Active: active (running) since Wed 2025-04-23 13:00:10 CEST; 2 weeks 6 days ago
   Main PID: 1145422 (perl)
      Tasks: 75 (limit: 50413)
     Memory: 271.6M
        CPU: 1h 32min 1.005s
     CGroup: /system.slice/gorgoned.service
             ├─1145422 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error
             ├─1145859 gorgone-httpserver
             ├─1145860 gorgone-dbcleaner
             ├─1145861 gorgone-cron
             ├─1145862 gorgone-anomalydetection
             ├─1145864 gorgone-engine
             ├─1145868 gorgone-statistics
             ├─1145873 gorgone-mbi-etlworkers
             ├─1145882 gorgone-mbi-etlworkers
             ├─1145884 gorgone-mbi-etlworkers
             ├─1145892 gorgone-mbi-etlworkers
             ├─1145907 gorgone-mbi-etlworkers
             ├─1145918 gorgone-mbi-etlworkers
             ├─1145932 gorgone-mbi-etlworkers
             ├─1145950 gorgone-mbi-etlworkers
             ├─1145961 gorgone-nodes
             ├─1145984 gorgone-mbietl
             ├─1145997 gorgone-legacycmd
             ├─1146008 gorgone-action
             ├─1146021 gorgone-proxy
             ├─1146042 gorgone-proxy
             ├─1146071 gorgone-proxy
             ├─1146090 gorgone-proxy
             ├─1146120 gorgone-proxy
             └─1146142 gorgone-autodiscovery

@Laurent this command “# systemctl status gorgoned| grep httpserver” returns nothing on the central server however status alone shows “

proot@centreon centreon-gorgone]# systemctl status gorgoned.service

gorgoned.service Centreon Gorgone

Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; preset: disabled)

Active: active (running) since Tue 2025-05-06 16:06:20 CEST; 6 days ago

Main PID: 1862068 (perl)

Tasks: 27 (limit: 48703)

Memory: 98.9M

CPU: 3min 41.629s

CGroup:

/system.slice/gorgoned.service

1862068 /usr/bin/perl/usr/bin/gorgoned ig=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=e>

1862071 gorgone-autodiscovery

1862072 gorgone-statistics

-1862073 gorgone-dbcleaner

1862074 gorgone-nodes

-1862075 gorgon-legacycmd

-1862076 gorgone-cron

1862077 gorgone-engine

-1862078 gorgon-audit

Notice: journal has been rotated since unit was started, output may be incomplete.

Can you try to copy in a code block, click on “...” and select code.

@Laurent I dont have all that you have and I have zero clue how to fix it

In /etc/centreon-gorgone/config.d/40-gorgoned.yaml file can you move to true the following block:

  modules:
    - name: httpserver
      package: "gorgone::modules::core::httpserver::hooks"
      enable: true
      address: "0.0.0.0"
      port: "8085"
      ssl: false
      auth:
        enabled: false
      allowed_hosts:
        enabled: true
        subnets:
          - 127.0.0.1/32

and configure subnets

@Laurent

I believe it’s already enabled no?

@Laurent I added the subnet too and restarted the service but i dont see any difference in the status result

@Laurent this centreon was configured in a different ip address aka installed it with a different ip, maybe its cus i changed the ip something didnt go right in the database or idk?

Can you enable debug in /var/sysconfig/gorgoned by changing ERROR to DEBUG and restart gorgoned process then check logs

@Laurent this is what im seeing in the logs now

Maybe i need to change the ip somewhere from the localhost one to the actual ip of centreon? idk

@Laurent COULD it also be related to thi? i dont know

@Laurent It says mariadb is not found, maybe that’s the issue, although i did install it, somethings wrong with my server

@Laurent I redid everything and still get same issue, i see nothing running on port 5556 I think that’s the problem cus even when I try to nc or telnet connect to the poller with ip and port 5556 i get connection timeout, any idea what to do?

is the conf file for centreon supposed to look like this “

name: gorgoned-Central
description: Configuration for remote server Central
gorgone:
  gorgonecore:
    privkey: "/var/lib/centreon-gorgone/.keys/rsakey.priv.pem"
    pubkey: "/var/lib/centreon-gorgone/.keys/rsakey.pub.pem"
    id: 1
  modules:
    - name: httpserver
      package: "gorgone::modules::core::httpserver::hooks"
      enable: true
      address: "0.0.0.0"
      port: "8085"
      ssl: false
      auth:
        enabled: false
      allowed_hosts:
        enabled: true
        subnets:
          - 127.0.0.1/32
    - name: action
      package: "gorgone::modules::core::action::hooks"
      enable: true
      command_timeout: 30
      whitelist_cmds: true
      allowed_cmds:
        - ^sudo\s+(/bin/)?systemctl\s+(reload|restart)\s+(centengine|centreontrapd|cbd)\s*$
        - ^(sudo\s+)?(/usr/bin/)?service\s+(centengine|centreontrapd|cbd|cbd-sql)\s+(reload|restart)\s*$
        - ^/usr/sbin/centenginestats\s+-c\s+/etc/centreon-engine/centengine\.cfg\s*$
        - ^cat\s+/var/lib/centreon-engine/ea-zA-Z0-9\-]+-stats\.json\s*$
        - ^/usr/lib/centreon/plugins/.*$
        - ^/bin/perl /usr/share/centreon/bin/anomaly_detection --seasonality >> /var/log/centreon/anomaly_detection\.log 2>&1\s*$
        - ^/usr/bin/php -q /usr/share/centreon/cron/centreon-helios\.php >> /var/log/centreon-helios\.log 2>&1\s*$
        - ^centreon
        - ^mkdir
        - ^/usr/share/centreon/www/modules/centreon-autodiscovery-server/script/run_save_discovered_host
        - ^/usr/share/centreon/bin/centreon -u \"centreon-gorgone\" -p \S+ -w -o CentreonWorker -a processQueue$
    - name: cron
      package: "gorgone::modules::core::cron::hooks"
      enable: true
      cron: !include cron.d/*.yaml
    - name: nodes
      package: "gorgone::modules::centreon::nodes::hooks"
      enable: true
    - name: proxy
      package: "gorgone::modules::core::proxy::hooks"
      enable: true
    - name: legacycmd
      package: "gorgone::modules::centreon::legacycmd::hooks"
      enable: true
      cmd_dir: "/var/lib/centreon/centcore/"
      cmd_file: "/var/lib/centreon/centcore.cmd"
      cache_dir: "/var/cache/centreon"
      cache_dir_trap: "/etc/snmp/centreon_traps"
      remote_dir: "/var/cache/centreon/config/remote-data/"
    - name: engine
      package: "gorgone::modules::centreon::engine::hooks"
      enable: true
      command_file: "/var/lib/centreon-engine/rw/centengine.cmd"
    - name: statistics
      package: "gorgone::modules::centreon::statistics::hooks"
      enable: true
      broker_cache_dir: "/var/cache/centreon/broker-stats/"
      cron:
        - id: broker_stats
          timespec: "*/5 * * * *"
          action: BROKERSTATS
          parameters:
            timeout: 10
        - id: engine_stats
          timespec: "*/5 * * * *"
          action: ENGINESTATS
          parameters:
            timeout: 10

because I literally have no clue why it wont work, I cant see port 5556 running at all

Reply

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded