I have a sensu-master on centos 6.5 with 2 nodes running the sensu-client both on centos 6.5.
I have the clients configured and they authenticate via rabbitmq and the transport is ok and the show up in Uchiwa no problem.
The issue I’m seeing right now is in the Uchiwa Dashboard I get the following:
I get these alerts even though the sensu-client is connecting and rabbitmq is talking from the clients to the master. When I click on each client I see something like this:
No keepalive sent from client for 32555 seconds (>=180) 9 hours ago
But the sensu-client is connecting and Rabbitmq shows an active connection to the sensu master.
Are these keepalive alerts false positives or something? What can I do to troubleshoot it?
No keepalive sent from client for 32546 seconds (>=180)
9 hours ago
No keepalive sent from client for 1367 seconds (>=180)
23 minutes ago