Sensu client windows service dies rather than retry after losing connection to Rabbitmq


#1

Hi,

For some reason I have to restart a sensu server. The client service on a windows box died rather pool for new connection. Here is what I see in the log files:

{“timestamp”:“2015-02-24T13:03:51.375750+1100”,“level”:“warn”,“message”:“reconnecting to transport”}

{“timestamp”:“2015-02-24T13:04:11.501862+1100”,“level”:“info”,“message”:“reconnected to transport”}

{“timestamp”:“2015-02-24T13:07:16.926100+1100”,“level”:“warn”,“message”:“reconnecting to transport”}

{“timestamp”:“2015-02-24T13:08:51.682585+1100”,“level”:“warn”,“message”:“reconnecting to transport”}

{“timestamp”:“2015-02-24T13:08:51.682585+1100”,“level”:“fatal”,“message”:“transport connection error”,“error”:“failed to connect to rabbitmq”}

{“timestamp”:“2015-02-24T13:08:51.682585+1100”,“level”:“warn”,“message”:“stopping”}

{“timestamp”:“2015-02-24T13:08:51.682585+1100”,“level”:“info”,“message”:“completing checks in progress”,“checks_in_progress”:}

{“timestamp”:“2015-02-24T13:08:52.432478+1100”,“level”:“warn”,“message”:“stopping reactor”

Is it possible to make the client continue to poll rather than stop?

Cheers, Tony