# Sensu client 0.20.3 received signal TERM after one hour

**URL:** <https://discourse.sensu.io/t/sensu-client-0-20-3-received-signal-term-after-one-hour/839>\
**Category:** Sensu Classic (EOL)\
**Created:** [July 18, 2017, 4:09pm UTC](https://discourse.sensu.io/t/sensu-client-0-20-3-received-signal-term-after-one-hour/839 "2017-07-18T16:09:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mevzos\_Vlad](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@Mevzos\_Vlad](https://discourse.sensu.io/u/Mevzos_Vlad)\
**Post date:** [July 18, 2017, 4:09pm UTC](https://discourse.sensu.io/t/sensu-client-0-20-3-received-signal-term-after-one-hour/839/1 "2017-07-18T16:09:03Z")

</div>

Hello,

I have the following issue:

After updating RabbitMQ to the latest version RabbitMQ 3.6.10 Erlang 17.5.3 sensu clients stop itself after one hour of work.

I have the following at sensu-client’s log:

{“timestamp”:“2017-07-18T14:52:14.655109+0000”,“level”:“warn”,“message”:“received signal”,“signal”:“TERM”}

{“timestamp”:“2017-07-18T14:52:14.655443+0000”,“level”:“warn”,“message”:“stopping”}

{“timestamp”:“2017-07-18T14:52:22.161803+0000”,“level”:“info”,“message”:“closing client tcp and udp sockets”}

{“timestamp”:“2017-07-18T14:52:22.162339+0000”,“level”:“warn”,“message”:“stopping reactor”}

> **···**
>
> ~
> 
> What could be the reason of such behaviour?
> 
> Regards,
> 
> Vlad

---

<div class="post-metadata">

**Author:** ![Ben\_Abrams](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@Ben\_Abrams](https://discourse.sensu.io/u/Ben_Abrams)\
**Post date:** [August 8, 2017, 12:46am UTC](https://discourse.sensu.io/t/sensu-client-0-20-3-received-signal-term-after-one-hour/839/2 "2017-08-08T00:46:38Z")

</div>

Could you be using some automation that might be causing a TERM? Something asked for it to terminate and it did. Without more information I have nothing to go on. I have seen people have issues with newer versions of sensu if they do not patch erlang from the rabbitmq repos (ubuntu and epel are too old).

> **···**
>
> On Tuesday, July 18, 2017 at 9:09:03 AM UTC-7, [mevzo...@gmail.com](mailto:mevzo...@gmail.com) wrote:
> 
> > Hello,
> 
> > I have the following issue:
> 
> > 
> 
> > After updating RabbitMQ to the latest version RabbitMQ 3.6.10 Erlang 17.5.3 sensu clients stop itself after one hour of work.
> 
> > 
> 
> > I have the following at sensu-client’s log:
> 
> > {“timestamp”:“2017-07-18T14:52:14.655109+0000”,“level”:“warn”,“message”:“received signal”,“signal”:“TERM”}
> 
> > {“timestamp”:“2017-07-18T14:52:14.655443+0000”,“level”:“warn”,“message”:“stopping”}
> 
> > {“timestamp”:“2017-07-18T14:52:22.161803+0000”,“level”:“info”,“message”:“closing client tcp and udp sockets”}
> 
> > {“timestamp”:“2017-07-18T14:52:22.162339+0000”,“level”:“warn”,“message”:“stopping reactor”}
> 
> > ~
> 
> > What could be the reason of such behaviour?
> 
> > 
> 
> > Regards,
> 
> > 
> 
> > Vlad
> 
> >

---

<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:07am UTC](https://discourse.sensu.io/t/sensu-client-0-20-3-received-signal-term-after-one-hour/839/3 "2018-11-22T02:07:57Z")

</div>