# No keep-alive sent from client

**URL:** <https://discourse.sensu.io/t/no-keep-alive-sent-from-client/187>\
**Category:** Sensu Classic (EOL)\
**Created:** [May 7, 2014, 1:05pm UTC](https://discourse.sensu.io/t/no-keep-alive-sent-from-client/187 "2014-05-07T13:05:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![william\_pink](https://avatars.discourse-cdn.com/v4/letter/w/4af34b/32.png) [@william\_pink](https://discourse.sensu.io/u/william_pink)\
**Post date:** [May 7, 2014, 1:05pm UTC](https://discourse.sensu.io/t/no-keep-alive-sent-from-client/187/1 "2014-05-07T13:05:26Z")

</div>

Hi,

I’ve been using Sensu a little while now but recently I’ve been seeing a lot of " No keep-alive sent from client in over 120 seconds" alerts recently.

Some background

Sensu version 0.12.6 running on a single Ubuntu 12.04.3 LTS AWS instance

**rabbit** mq-server 3.1.5-1

Sensu-client 0.12.6 (We have Gentoo and Ubuntu clients but they are both having the same issue)

RabbitMQ is not clustered and is running locally on the Sensu server.

In my RabbitMQ logs I’m seeing the following

error on AMQP connection \<0.725.0\>: {ssl\_upgrade\_error,closed} (unknown POSIX error)

and also

connection\_closed\_abruptly

and sometimes

{amqp\_error,not\_found,“no queue ‘ **keepalive** s’ in vhost ‘/sensu’”,

I’ve done some googling and come to a bit of a blank.

Any help/guidance would be great,

Thanks,

Will

---

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [November 22, 2018, 2:05am UTC](https://discourse.sensu.io/t/no-keep-alive-sent-from-client/187/2 "2018-11-22T02:05:15Z")

</div>