I have setup sensu on a Centos 6.5 box and installed/configured the client on the sensu box so it monitors itself like so
/etc/sensu/conf.d/client.json
{
"client": {
"name": "sensu",
"address": "10.100.1.200",
"subscriptions": [
"ALL"
]
}
}
This works fine and it shows up in Uchiwa, but now I have another host I want to register with Sensu/Uchiwa and it does not show up in clients under Uchiwa/Sensu
Here's the configuration on the client "coffee"
/etc/sensu/conf.d/rabbitmq.json
{
"rabbitmq":{
"host": "10.100.1.200",
"port": "5672",
"vhost": "/sensu",
"user": "user",
"pass": "pass"
}
}
/etc/sensu/conf.d/client.json
{
"client": {
"name": "coffee",
"address": "10.100.1.19",
"subscriptions": [
"ALL"
]
}
}
When I tail the /var/log/sensu/sensu-client.log on coffee I see the following:
{"timestamp":"2015-07-13T07:15:52.856009-0500","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/client.json"}
{"timestamp":"2015-07-13T07:15:52.856157-0500","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/client.json","changes":{"client":{"subscriptions":[["ALL","ALL"],["ALL"]]}}}
{"timestamp":"2015-07-13T07:15:52.856235-0500","level":"warn","message":"loading config file","file":"/etc/sensu/conf.d/rabbitmq.json"}
{"timestamp":"2015-07-13T07:15:52.856330-0500","level":"warn","message":"config file applied changes","file":"/etc/sensu/conf.d/rabbitmq.json","changes":{"rabbitmq":{"port":[5672,"5672"],"pass":"REDACTED"}}}
{"timestamp":"2015-07-13T07:15:52.859696-0500","level":"warn","message":"loading extension files from directory","directory":"/etc/sensu/extensions"}
{"timestamp":"2015-07-13T07:15:53.051176-0500","level":"warn","message":"reconnecting to transport"}
It looks like it's talking to RabbitMQ but for some reason the client does not appear in Uchiwa. How can I dive into this further and figure out what's going on and get the coffee server to register?
The issue was caused by a significant time difference between the
sensu-client
andsensu-server
.vs.
Solution
The issue was solved by synchronizing the clocks using
timedatectl
:and changing the timezone by issuing:
synchronized the time on the server with the client:
After restarting the
sensu-services
andrabbitmq
the client was found in thesensu-api
and registered in Uchiwa.