Can't find evidence of sensu-client working

I’ve followed the instructions in http://sensuapp.org/docs/0.12/guide to get started with sensu and almost everything appears to work.

I have the dashboard up, but there are no clients listed. I’ve tried various things for about an hour with no luck.

Below are logs from sensu-client.log and sensu-server.log I would expect something about the cron_check handler to appear somewhere, either in the dashboard or in the client log every minute. The cron check should actually fail because the process is cron and not crond.

I’d appreciate any help.

Thanks,

  • Peter

Note, I sent service sensu-client restart at 15:27:07

/etc/sensu/conf.d/client.json:

{
“client”: {
“name”: “services”,
“address”: “127.0.0.1”,
“subscriptions”: [ “all” ]
}

}

/etc/sensu/conf.d/check_cron.json:

{
“checks”: {
“cron_check”: {
“handlers”: [“default”],

  "command": "/etc/sensu/plugins/check-procs.rb -p crond -C 1 ",
  "interval": 60,
  "subscribers": [ "all" ]
}

}
}

rabbitmq log:

=INFO REPORT==== 6-May-2014::15:27:08 ===
accepting AMQP connection <0.932.0> (10.0.0.10:53388 -> 10.0.0.10:5671)

sensu-client.log

{“timestamp”:“2014-05-06T15:27:07.339425+0000”,“level”:“warn”,“message”:“stopping reactor”}
{“timestamp”:“2014-05-06T15:27:07.972221+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/dashboard.json",“changes”:{“dashboard”:[null,{“port”:25535}]}}

{“timestamp”:“2014-05-06T15:27:07.972649+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/check_cron.json",“changes”:{“checks”:{“cron_check”:[null,{“handlers”:[“default”],“command”:"/etc/sensu/plugins/check-procs.rb -p crond -C 1 ",“interval”:60,“subscribers”:[“all”,“cobalt”,“frontend”,“services”]}]}}}

{“timestamp”:“2014-05-06T15:27:07.972958+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/rabbitmq.json",“changes”:{“rabbitmq”:[null,{“ssl”:{“cert_chain_file”:"/etc/sensu/ssl/cert.pem",“private_key_file”:"/etc/sensu/ssl/key.pem"},“host”:“sensu.internal”,“port”:5671,“vhost”:"/sensu",“user”:“sensu”,“password”:“REDACTED”}]}}

{“timestamp”:“2014-05-06T15:27:07.973224+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/api.json",“changes”:{“api”:[null,{“host”:“localhost”,“port”:4567,“user”:“admin”,“password”:“REDACTED”}]}}

{“timestamp”:“2014-05-06T15:27:07.973484+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/client.json",“changes”:{“client”:[null,{“name”:“services”,“address”:“127.0.0.1”,“subscriptions”:[“all”]}]}}

{“timestamp”:“2014-05-06T15:27:07.973743+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/redis.json",“changes”:{“redis”:[null,{“host”:“localhost”,“port”:6379,“password”:“REDACTED”}]}}

{“timestamp”:“2014-05-06T15:27:07.986210+0000”,“level”:“info”,“message”:“loaded extension”,“type”:“mutator”,“name”:“only_check_output”,“description”:“returns check output”}

{“timestamp”:“2014-05-06T15:27:07.989749+0000”,“level”:“info”,“message”:“loaded extension”,“type”:“handler”,“name”:“debug”,“description”:“outputs json event data”}

sensu-server.log

{“timestamp”:“2014-05-06T15:26:21.507869+0000”,“level”:“info”,“message”:“pruning aggregations”}
{“timestamp”:“2014-05-06T15:26:31.512184+0000”,“level”:“info”,“message”:“determining stale clients”}

{“timestamp”:“2014-05-06T15:26:41.508357+0000”,“level”:“info”,“message”:“pruning aggregations”}
{“timestamp”:“2014-05-06T15:27:01.508913+0000”,“level”:“info”,“message”:“pruning aggregations”}

{“timestamp”:“2014-05-06T15:27:01.512595+0000”,“level”:“info”,“message”:“determining stale clients”}
{“timestamp”:“2014-05-06T15:27:21.509436+0000”,“level”:“info”,“message”:“pruning aggregations”}

{“timestamp”:“2014-05-06T15:27:31.513134+0000”,“level”:“info”,“message”:“determining stale clients”}
{“timestamp”:“2014-05-06T15:27:41.509935+0000”,“level”:“info”,“message”:“pruning aggregations”}

{“timestamp”:“2014-05-06T15:28:01.510408+0000”,“level”:“info”,“message”:“pruning aggregations”}
{“timestamp”:“2014-05-06T15:28:01.513581+0000”,“level”:“info”,“message”:“determining stale clients”}

Mattch just helped me out on IRC.

Having done nothing else other than change the address to be something other than 127.0.0.1, we ran:

echo ‘{“name”:“test”, “output”:“test - please ignore”, “status”:0}’ | nc localhost 3030

and this did show up in the dashboard.

So the remaining mystery is why the “cron” check isn’t showing up.

···

On 6 May 2014 16:37, Peter Waller peter@scraperwiki.com wrote:

I’ve followed the instructions in http://sensuapp.org/docs/0.12/guide to get started with sensu and almost everything appears to work.

I have the dashboard up, but there are no clients listed. I’ve tried various things for about an hour with no luck.

Below are logs from sensu-client.log and sensu-server.log I would expect something about the cron_check handler to appear somewhere, either in the dashboard or in the client log every minute. The cron check should actually fail because the process is cron and not crond.

I’d appreciate any help.

Thanks,

  • Peter

Note, I sent service sensu-client restart at 15:27:07

/etc/sensu/conf.d/client.json:

{
“client”: {
“name”: “services”,
“address”: “127.0.0.1”,
“subscriptions”: [ “all” ]
}

}

/etc/sensu/conf.d/check_cron.json:

{
“checks”: {
“cron_check”: {
“handlers”: [“default”],

  "command": "/etc/sensu/plugins/check-procs.rb -p crond -C 1 ",
  "interval": 60,
  "subscribers": [ "all" ]
}

}
}

rabbitmq log:

=INFO REPORT==== 6-May-2014::15:27:08 ===
accepting AMQP connection <0.932.0> (10.0.0.10:53388 -> 10.0.0.10:5671)

sensu-client.log

{“timestamp”:“2014-05-06T15:27:07.339425+0000”,“level”:“warn”,“message”:“stopping reactor”}
{“timestamp”:“2014-05-06T15:27:07.972221+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/dashboard.json",“changes”:{“dashboard”:[null,{“port”:25535}]}}

{“timestamp”:“2014-05-06T15:27:07.972649+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/check_cron.json",“changes”:{“checks”:{“cron_check”:[null,{“handlers”:[“default”],“command”:"/etc/sensu/plugins/check-procs.rb -p crond -C 1 ",“interval”:60,“subscribers”:[“all”,“cobalt”,“frontend”,“services”]}]}}}

{“timestamp”:“2014-05-06T15:27:07.972958+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/rabbitmq.json",“changes”:{“rabbitmq”:[null,{“ssl”:{“cert_chain_file”:"/etc/sensu/ssl/cert.pem",“private_key_file”:"/etc/sensu/ssl/key.pem"},“host”:“sensu.internal”,“port”:5671,“vhost”:"/sensu",“user”:“sensu”,“password”:“REDACTED”}]}}

{“timestamp”:“2014-05-06T15:27:07.973224+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/api.json",“changes”:{“api”:[null,{“host”:“localhost”,“port”:4567,“user”:“admin”,“password”:“REDACTED”}]}}

{“timestamp”:“2014-05-06T15:27:07.973484+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/client.json",“changes”:{“client”:[null,{“name”:“services”,“address”:“127.0.0.1”,“subscriptions”:[“all”]}]}}

{“timestamp”:“2014-05-06T15:27:07.973743+0000”,“level”:“warn”,“message”:“config file applied changes”,“config_file”:"/etc/sensu/conf.d/redis.json",“changes”:{“redis”:[null,{“host”:“localhost”,“port”:6379,“password”:“REDACTED”}]}}

{“timestamp”:“2014-05-06T15:27:07.986210+0000”,“level”:“info”,“message”:“loaded extension”,“type”:“mutator”,“name”:“only_check_output”,“description”:“returns check output”}

{“timestamp”:“2014-05-06T15:27:07.989749+0000”,“level”:“info”,“message”:“loaded extension”,“type”:“handler”,“name”:“debug”,“description”:“outputs json event data”}

sensu-server.log

{“timestamp”:“2014-05-06T15:26:21.507869+0000”,“level”:“info”,“message”:“pruning aggregations”}
{“timestamp”:“2014-05-06T15:26:31.512184+0000”,“level”:“info”,“message”:“determining stale clients”}

{“timestamp”:“2014-05-06T15:26:41.508357+0000”,“level”:“info”,“message”:“pruning aggregations”}
{“timestamp”:“2014-05-06T15:27:01.508913+0000”,“level”:“info”,“message”:“pruning aggregations”}

{“timestamp”:“2014-05-06T15:27:01.512595+0000”,“level”:“info”,“message”:“determining stale clients”}
{“timestamp”:“2014-05-06T15:27:21.509436+0000”,“level”:“info”,“message”:“pruning aggregations”}

{“timestamp”:“2014-05-06T15:27:31.513134+0000”,“level”:“info”,“message”:“determining stale clients”}
{“timestamp”:“2014-05-06T15:27:41.509935+0000”,“level”:“info”,“message”:“pruning aggregations”}

{“timestamp”:“2014-05-06T15:28:01.510408+0000”,“level”:“info”,“message”:“pruning aggregations”}
{“timestamp”:“2014-05-06T15:28:01.513581+0000”,“level”:“info”,“message”:“determining stale clients”}