pollers peers disconnection not working inactive
- Pollers or peers not connected/ in an inactive state.
- Different OP5 versions within the cluster.
- SSH keys not propagated within the cluster.
- Corrupted nagios.conf file.
ist diagnose can quickly diagnose most aspects of the above-mentioned errors.
- Try a
- Run this command on all devices, and make sure that all devices are running the same version:
cat /etc/op5-monitor-releaseIt should give output such as this:
- If there are differences, please rectify the situation by getting all devices on the same version.
- Afterward, check in the
/var/log/securefile, and see if there are any errors pertaining to SSH. If there is, run these commands on the server having the issue. This will need to run for each additional server in the cluster. An example:
mon sshkey push <hostname1>This pushes all SSH keys over to the other servers in the cluster. OP5 uses passwordless SSH connections for some communications, so we need to make sure all the SSH keys are moved everywhere.
asmonitor mon sshkey push <hostname1>
mon sshkey push <hostname2>
asmonitor mon sshkey push <hostname2>
- If you have a corrupted or damaged naemon config, (which is located at
/opt/monitor/etc/naemon.cfg), you can simply copy the nagios.conf file from one of the other servers in the cluster, then run
If the issue persists
- Please contact our Client Services team via the chat service box available on any of our websites or via email to firstname.lastname@example.org
- Make sure you provide to us:
-Any troubleshooting step already verified from the ones described in this article.