Here is a summary of known issues, encoutered during the tests of Centreon Monitoring Agent, in Beta phasis.
| Issue | Status | Workaround | Target |
|---|---|---|---|
| Listening is not working if IPv4 AND IPv6 are activated on server (Poller or Host) | In development | Disable IPv6 or use s::] as listening IP address | 24.10.3 |
| “Poller initiated connection” mode is not set up properly by installer | Ready for release | in the registry key : HKEY_LOCAL_MACHINE\SOFTWARE\Centreon\CentreonMonitoringAgent Create a new DWORD value : reverse_connection with value 0 for mode “agent send to the poller”, or 1 for “poller initiated connecion” ( = agent listen on the tcp port 4317) | 24.10.2 |
|
|
Troubleshooting
“The Agent is not working properly !”
If you applied the workarounds described above, and the Agent is still in errors, please check the following :
- Ensure you followed the deployment procedure, without missing any step
- Make sure you can reach the Poller from the Host, on the configured port (default : 4317)
- Check is the Poller is listening on the right port
netstat -nap | grep 4317-
Check if there are incomming packets on this port. It must be
tcpdump -i any port 4317- Check if the hostname is strictly the same in the Centreon Host ?
- For Windows Host, on Host template, check the SYSTEMLANGUAGE macro, according to the Windows host language (fr or en)
- Check engine logs on Poller, in trace mode
tail -100 /var/log/centreon-engine/centengine.log- Reload engine
- Reload the agent
- Make sure you have the last version of dedicated connectors, which include default passive mode (needed)