SENSU CLIENT CONFIG FAILURE [amqp] Detected TCP connection failure

Sensu Classic (EOL)
1

SENSU CLIENT IS NOT WORKING.

BELOW ARE THE CONFIGURATIONS

tail -f /var/log/sensu/sensu-api.log

{“timestamp”:“2016-05-06T12:14:47.650477+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

{“timestamp”:“2016-05-06T12:15:07.667645+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

{“timestamp”:“2016-05-06T12:15:27.675219+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

{“timestamp”:“2016-05-06T12:15:47.692230+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

tail -f /var/log/sensu/sensu-client.log

{“timestamp”:“2016-05-06T12:14:57.688362+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

{“timestamp”:“2016-05-06T12:15:17.688331+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

{“timestamp”:“2016-05-06T12:15:37.688875+0530”,“level”:“error”,“message”:"[amqp] Detected TCP connection failure"}

rabbitmq log

=ERROR REPORT==== 6-May-2016::12:22:59 ===

closing AMQP connection <0.6869.0> (127.0.0.1:34294 -> 127.0.0.1:5672):

{handshake_timeout,handshake}

=INFO REPORT==== 6-May-2016::12:23:20 ===

accepting AMQP connection <0.6876.0> (127.0.0.1:34298 -> 127.0.0.1:5672)

=ERROR REPORT==== 6-May-2016::12:23:26 ===

closing AMQP connection <0.6876.0> (127.0.0.1:34298 -> 127.0.0.1:5672):

{handshake_timeout,handshake}

api.json

{

“api”: {

“host”: “127.0.0.1”,

“bind”: “0.0.0.0”,

“port”: 4567

}

}

client.json

{

“client”: {

“name”: “jenkins”,

“address”: “127.0.0.1”,

“subscriptions”: [

“jenkins”

]

}

}

rabbitmq.json

{

“rabbitmq”: {

“host”: server_ip,

“port”: 5672,

“vhost”: “/sensu”,

“user”: “sensu”,

“password”: “secret”

}

}

transport.json

{

“transport”: {

“name”: “rabbitmq”,

“reconnect_on_error”: true

}

}

2

Hi Imran,
Your rabbitmq log errors aren’t logged at the same as the disconnection issue, so they appear unrelated - and the API is also having trouble connecting - I’d recommend ensuring your rabbitmq server is online & available, and then making sure the server and API can connect to it without error before proceeding with the client setup.

Anthony

···

On Thursday, May 5, 2016 at 9:03:09 PM UTC-10, IMRAN SHAIK wrote:

SENSU CLIENT IS NOT WORKING.

BELOW ARE THE CONFIGURATIONS

tail -f /var/log/sensu/sensu-api.log

{“timestamp”:“2016-05-06T12:14:47.650477+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

{“timestamp”:“2016-05-06T12:15:07.667645+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

{“timestamp”:“2016-05-06T12:15:27.675219+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

{“timestamp”:“2016-05-06T12:15:47.692230+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

tail -f /var/log/sensu/sensu-client.log

{“timestamp”:“2016-05-06T12:14:57.688362+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

{“timestamp”:“2016-05-06T12:15:17.688331+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

{“timestamp”:“2016-05-06T12:15:37.688875+0530”,“level”:“error”,“message”:“[amqp] Detected TCP connection failure”}

rabbitmq log

=ERROR REPORT==== 6-May-2016::12:22:59 ===

closing AMQP connection <0.6869.0> (127.0.0.1:34294 → 127.0.0.1:5672):

{handshake_timeout,handshake}

=INFO REPORT==== 6-May-2016::12:23:20 ===

accepting AMQP connection <0.6876.0> (127.0.0.1:34298 → 127.0.0.1:5672)

=ERROR REPORT==== 6-May-2016::12:23:26 ===

closing AMQP connection <0.6876.0> (127.0.0.1:34298 → 127.0.0.1:5672):

{handshake_timeout,handshake}

api.json

{

“api”: {

“host”: “127.0.0.1”,

“bind”: “0.0.0.0”,

“port”: 4567

}

}

client.json

{

“client”: {

“name”: “jenkins”,

“address”: “127.0.0.1”,

“subscriptions”: [

“jenkins”

]

}

}

rabbitmq.json

{

“rabbitmq”: {

“host”: server_ip,

“port”: 5672,

“vhost”: “/sensu”,

“user”: “sensu”,

“password”: “secret”

}

}

transport.json

{

“transport”: {

“name”: “rabbitmq”,

“reconnect_on_error”: true

}

}