No keepalive sent from client


#1

In the past days I see this kind of message in Uchiwa and in the Sensu server log

No keepalive sent from client for 677837 seconds (>=180)

This is a local client setup

client.json

{
“client”: {
“name”: “devtest”,
“address”: “my-vm.example.com”,
“environment”: “development”,
“subscriptions”: [
“dev”,
“base”,
“test”
],
“socket”: {
“bind”: “my-vm.example.com”,
“port”: 3030
}
},
“checks”: {
“test”: {
“command”: “echo -n OK”,
“subscribers”: [
“test”
],
“interval”: 60
},
“local-disk-space”: {
“command”: “/usr/local/nagios/libexec/check_disk -n -l -e -w 68% -c 67% /tmp”,
“subscribers”: [
“test”
],
“interval”: 60
}
}
}

``

.Changing the bind to 127.0.0.1 did not solve the problem

NTP seems to be working fine on the server, as the time is very accurate.

client.log shows it’s publishing keepalive:

{“timestamp”:“2016-09-14T10:56:18.805200+0300”,“level”:“debug”,“message”:“publishing keepalive”,“payload”:{“name”:“devtest”,“address”:“my-vm.example.com”,“environment”:“development”,“subscriptions”:[“dev”,“base”,“test”],“socket”:{“bind”:“127.0.0.1”,“port”:3030},“version”:“0.25.7”,“timestamp”:1473839778}}

``


#2

I was able to fix this by restarting the Sensu server.
:slight_smile:

···

On Wednesday, September 14, 2016 at 10:58:37 AM UTC+3, Yaron Yogev wrote:

In the past days I see this kind of message in Uchiwa and in the Sensu server log

No keepalive sent from client for 677837 seconds (>=180)

This is a local client setup

client.json

{
“client”: {
“name”: “devtest”,
“address”: “my-vm.example.com”,
“environment”: “development”,
“subscriptions”: [
“dev”,
“base”,
“test”
],
“socket”: {
“bind”: “my-vm.example.com”,
“port”: 3030
}
},
“checks”: {
“test”: {
“command”: “echo -n OK”,
“subscribers”: [
“test”
],
“interval”: 60
},
“local-disk-space”: {
“command”: “/usr/local/nagios/libexec/check_disk -n -l -e -w 68% -c 67% /tmp”,
“subscribers”: [
“test”
],
“interval”: 60
}
}
}

``

.Changing the bind to 127.0.0.1 did not solve the problem

NTP seems to be working fine on the server, as the time is very accurate.

client.log shows it’s publishing keepalive:

{“timestamp”:“2016-09-14T10:56:18.805200+0300”,“level”:“debug”,“message”:“publishing keepalive”,“payload”:{“name”:“devtest”,“address”:“my-vm.example.com”,“environment”:“development”,“subscriptions”:[“dev”,“base”,“test”],“socket”:{“bind”:“127.0.0.1”,“port”:3030},“version”:“0.25.7”,“timestamp”:1473839778}}

``