Hello

following the guide I managed to connect a host to the poller using the method “poller connect to the agent” (with some issue on another post, but it worked)

however I tried the other method wich is “agent connect to poller”, and I tried to do the config allowing both method

mode agent->poller

{
   "otel_server":{
      "host":"0.0.0.0",
      "port":4317
   },
   "max_length_grpc_log":0,
   "centreon_agent":{
      "check_interval":60,
      "export_period":10
   }
}

mixed agent<->poller

{
   "otel_server":{
      "host":"0.0.0.0",
      "port":4317
   },
   "max_length_grpc_log":0,
   "centreon_agent":{
      "check_interval":60,
      "export_period":15,
      "reverse_connections":n
         {
            "host":"192.168.10.10",
            "port":4317
         }
      ]
   }
}

in both case after restarting centengine there is nothing listening on 0.0.0.0 on the linux poller

but there something listening on localhost ipv6 :::4317

tcp6       0      0 :::4317                 :::*                    LISTEN      984        202352     9016/centengine
 

if I input the real ipv4 instead of 0.0.0.0 in the config file, the tcp port 4317 appears on the ipv4 and there is no ipv6 listening.

the CMA connected correctly when I put that ip in the poller.

I will personnaly only use the mode “poller connects to the agent” as this is the mode I will need to use, all my pollers are in DMZ and we “poll” the data from the client hosts, they can’t talk to us. I tried this mode to test if there were differences, but encounterd this proble.

on an additionnal note, I made this centreon setup on a basic alma9 OS, this has the firewall activated by default, and the centreon installer script did all things needed for the web service to work correctly, so this command needs to be included as well somewhere :

firewall-cmd --permanent --zone=public --add-port=4317/tcp

otherwise the agent can’t connect to the poller. (probably something else on other distrib but for Alma it’s that command.)