Skip to main content
Sticky

Centreon Monitoring Agent - Troubleshooting

  • November 5, 2024
  • 9 replies
  • 774 views

fmattes
Centreonian
Forum|alt.badge.img+10

“The Agent is not working properly !”

If you encounter errors using Centreon Monitoring Agent, please check the dedicated documentation

 

 

 

9 replies

Forum|alt.badge.img+11
  • Builder *
  • August 13, 2025

Hello,

For check engine logs on poller which logs must config in trace mode for CMA Troubleshooting ?

how reload the agent ? on the poller or on the host ?

 

In my case I receive the packets on port 4317 as demonstrated by tcpdump on the poller but the services remain pending.

 

the command “netstat -nap | grep 4317” seems to show that port 4317 is not listening on the poller.

 

thanks


fmattes
Centreonian
Forum|alt.badge.img+10
  • Author
  • Centreonian
  • August 14, 2025

Hi,

Engine logs on Poller are 

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

If port 4317 is not listening, can you check that : 

  • you are using the last version of collect (24.10.10), centreon (24.10.10) & agent (24.10.7)
  • The broker directive is created in Configuration > Poller > Engine configuration 
    • /usr/lib64/centreon-engine/libopentelemetry.so /etc/centreon-engine/otl_server.json

  • Give a try with no encryption (test mode) on both Poller & Agent

 

Thanks


Forum|alt.badge.img+11
  • Builder *
  • August 14, 2025

Dear ​@fmattes ,

Tthank you for your reply.

I can confirm that I am up to date (as of yesterday) on the central and on the poller and on the monitored Windows host.

centreon-central-24.10.10-1.el8.noarch

centreon-web-24.10.10-1.el8.noarch

centreon-engine-24.10.10-1.el8.x86_64

centreon-monitoring-agent-24.10.7.exe

 

I installed the packs, added the commands in the connector. Created an agent without TLS and associated it with the correct poller.

(and associated my host with the adequoite template with the 2 macros SYSTEMLANGUAGE = fr and CENTREONAGENTPLUGINS = C:/Program Files/Centreon/Plugins)

The poller has the json file "/etc/centreon-engine/otl_server.json"

{
"otel_server": {
"host": "0.0.0.0",
"port": 4317,
"encryption": false,
"public_cert": "",
"private_key": "",
"ca_certificate": ""
},
"centreon_agent": {
"check_interval": 60,
"export_period": 60
},
"tokens": []
}

selinux is in permissive mode

the firewall is reloaded after allowing port 4317/tcp

but the port is still not listening on the poller.

the tcpdump shows that I am receiving the 4317 streams

my centreon services are pending

The Windows Server logs of the host show that the connection is refused.

 

[2025-08-13 19:05:15.586] [error] [bireactor.cc:191] 0x20af5e0ddd0 peer:172.31.0.81:4317 client::OnDone(failed to connect to all addresses; last error: UNAVAILABLE: ipv4:172.31.0.81:4317: WSAGetOverlappedResult: Connection refused (Unable to retrieve error string -- 10061)) 

 

Thanks you


fmattes
Centreonian
Forum|alt.badge.img+10
  • Author
  • Centreonian
  • August 14, 2025

Thanks for these details. 

Did you check the following ? 

  • The broker directive is created in Configuration > Poller > Engine configuration 
    • /usr/lib64/centreon-engine/libopentelemetry.so /etc/centreon-engine/otl_server.json


Forum|alt.badge.img+11
  • Builder *
  • August 14, 2025

Dear ​@fmattes ,

I need to add this broker module directive here ?

usr/lib64/centreon-engine/libopentelemetry.so /etc/centreon-engine/otl_server.json

 

Thanks


fmattes
Centreonian
Forum|alt.badge.img+10
  • Author
  • Centreonian
  • August 14, 2025

Dear ​@fmattes ,

I need to add this broker module directive here ?

usr/lib64/centreon-engine/libopentelemetry.so /etc/centreon-engine/otl_server.json

 

Thanks

Yes, please.

It should already be here, i create an issue about this.


Forum|alt.badge.img+11
  • Builder *
  • August 15, 2025

Dear ​@fmattes ,

I confirm after adding the broker module directive everything works now, my passive CMA services receive data from the host.

Thanks and best regards


fmattes
Centreonian
Forum|alt.badge.img+10
  • Author
  • Centreonian
  • August 18, 2025

Dear ​@fmattes ,

I confirm after adding the broker module directive everything works now, my passive CMA services receive data from the host.

Thanks and best regards

Hi,

In order to work on this behavior, could you give me more detail about your context ? 

  • was the Agent configuration (in UI) already created before upgrade to 24.10.10 ?
  • if yes, was the Agent working before this upgrade ? 
  • or is it a fresh Agent configration in 24.10.10 ?

The directive is created, if not existing, once you create an Agent configuration.

We tested it on 24.10.10 and it is working.

Thanks


Forum|alt.badge.img+11
  • Builder *
  • August 18, 2025

Dear ​@fmattes ,

My current instance of Centreon dates from approximately 21.10.

I did not create the Agent configuration myself in UI, it seems to me that it was already created automatically before upgrading to 24.10.10.

But I've never used CMA before so I don't know in detail when this agent appeared.

Best regards