Skip to main content

Troubleshooting CMA

Host checks​

Check that the service is running​

  1. Execute the following command:

    systemctl status centagent

  2. If the service is not running, start it.

    systemctl restart centagent

Check that the agent log file does not contain any errors​

Depending on the path configured for your log file, check for any errors:

grep error /var/log/centreon-monitoring-agent/centagent.log

No lines should be returned.

Poller checks​

Check that the server is listening and that packets are arriving​

  1. Port number 4317 must be open (inbound) on the poller.

  2. Execute the following command:

    netstat -na | grep 4317

    This command must return results, showing that the server is listening (ESTABLISHED).

  3. Execute the following command:

    tcpdump -i any port 4317

    This command must return results, showing that packets are arriving from the agent.

Enable the OpenTelemetry logs​

  1. Edit the monitoring engine's configuration file:

    /etc/centreon-engine/centengine.cfg

  2. Add the following line:

    log_level_otl=trace

    The different log levels are: trace, debug, info, warning, error, critical, disabled.

  3. Restart the monitoring engine.

Check that the engine log file does not contain any errors​

Execute the following command:

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

No CMA related lines should be returned.

Checks in Centreon​

The host and its configured services must return a status and metrics.

Location of poller and agent logs​

  • Poller logs: /var/log/centreon-engine/centengine.log

  • Agent logs:

    • Linux: by default, /var/log/centreon-monitoring-agent/centagent.log (this log location can be configured in /etc/centreon-monitoring-agent/centagent.json)
    • Windows: the location is the one you specified when installing the agent (by default, in the Windows Event Viewer).