Sensu client 0.20.3 received signal TERM after one hour

Sensu Classic (EOL)
1

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

2

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 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