# No keepalive sent from client

**URL:** <https://discourse.sensu.io/t/no-keepalive-sent-from-client/678>\
**Category:** Sensu Classic (EOL)\
**Created:** [September 14, 2016, 7:58am UTC](https://discourse.sensu.io/t/no-keepalive-sent-from-client/678 "2016-09-14T07:58:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yaron\_Yogev](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/yaron_yogev/32/401_2.png) [@Yaron\_Yogev](https://discourse.sensu.io/u/Yaron_Yogev)\
**Post date:** [September 14, 2016, 7:58am UTC](https://discourse.sensu.io/t/no-keepalive-sent-from-client/678/1 "2016-09-14T07:58:37Z")

</div>

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](http://my-vm.example.com)”,  
“environment”: “development”,  
“subscriptions”: [  
“dev”,  
“base”,  
“test”  
],  
“socket”: {  
“bind”: “[my-vm.example.com](http://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](http://my-vm.example.com)”,“environment”:“development”,“subscriptions”:[“dev”,“base”,“test”],“socket”:{“bind”:“127.0.0.1”,“port”:3030},“version”:“0.25.7”,“timestamp”:1473839778}}

``

---

<div class="post-metadata">

**Author:** ![Yaron\_Yogev](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/yaron_yogev/32/401_2.png) [@Yaron\_Yogev](https://discourse.sensu.io/u/Yaron_Yogev)\
**Post date:** [September 14, 2016, 9:57am UTC](https://discourse.sensu.io/t/no-keepalive-sent-from-client/678/2 "2016-09-14T09:57:11Z")

</div>

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

> **···**
>
> 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](http://my-vm.example.com)”,  
> > “environment”: “development”,  
> > “subscriptions”: [  
> > “dev”,  
> > “base”,  
> > “test”  
> > ],  
> > “socket”: {  
> > “bind”: “[my-vm.example.com](http://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](http://my-vm.example.com)”,“environment”:“development”,“subscriptions”:[“dev”,“base”,“test”],“socket”:{“bind”:“127.0.0.1”,“port”:3030},“version”:“0.25.7”,“timestamp”:1473839778}}
> 
> > ``
> 
> > 
> 
> > 
> 
> > 
> 
> >