Sensu is not healthy says sensu-cli ... Now what?

Sensu Classic (EOL)
1

Is there a tool
(or some steps)

that’ll give me a clue to what to do?

This is a new install

ruby 1.9.3

on Centos 6.5

sensu-cli info

sensu: {“version”=>“0.14.0”}

transport: {“keepalives”=>{“messages”=>0, “consumers”=>1}, “results”=>{“messages”=>0, “consumers”=>1}, “connected”=>true}

redis: {“connected”=>true}

sensu-cli client list

···

name: ws00

address: localhost

subscriptions: [“all”]

version: 0.14.0

timestamp: 1413400367

2

Health looks at two things:
minimum number of consumers
maximum number of messages

Based on your transport from sensu-cli info it “seems” healthy as you
have 1 consumer and no messages in the queue.

What are you doing for a sensu-cli health command?

* This should return healthy in the above scenario
sensu-cli health --consumers 1 --messages 100

You can also mimic this right in the browser:
http://127.0.0.1:4567/health?consumers=1&messages=100

If you get a 204, it is healthy.

Thanks,
Bryan

···

On Wed, Oct 15, 2014 at 2:26 PM, clay tyler <theclaytyler@gmail.com> wrote:

Is there a tool
(or some steps)
that'll give me a clue to what to do?

This is a new install
ruby 1.9.3
on Centos 6.5

# sensu-cli info
sensu: {"version"=>"0.14.0"}
transport: {"keepalives"=>{"messages"=>0, "consumers"=>1},
"results"=>{"messages"=>0, "consumers"=>1}, "connected"=>true}
redis: {"connected"=>true}

# sensu-cli client list
-------
name: ws00
address: localhost
subscriptions: ["all"]
version: 0.14.0
timestamp: 1413400367

3

HI Bryan,

I was busy reinstalling it

.

All done now.

Still suffering though.

The /health …

Well, I ran

sensu-cli health -c 3 -m 100

It still says

Sensu is not healthy.

In uchiwa I get these:

/health

{"uchiwa":"ok","sensu":{"Sensu":{}}}

/health/sensu

{"sensu":{"Sensu":{}}}

/health/uchiwa

{"uchiwa":"ok"}

I’m thinking the sensu entries shouldn’t be empty?

Don’t know.

Thanks to your message,

I tried sensu-cli health again - I changed consumers to 1.

Guess what ?? !!!

It said Sensu is healthy! :slight_smile:

Yay!!

Looked at another way though, that is a real bummer.

I had thought that that output from cli health would help me track down the real problem.

Now, I’m back where I began - without a clue about how to track down and fix it.

Here’s the problem …

There’s a big red box flashing in uchiwa that says: “Error with Sensu API Sensu”

I’ve checked permissions, credentials … permissive selinux doesn’t help - maybe it’s the SSLs?

Whatever it is I can’t find a clue anywhere. I just have a broken sensu.

Any ideas?

They’re MIGHTY welcome

Thanks!

···

On Wednesday, October 15, 2014 2:45:08 PM UTC-5, agent462 wrote:

Health looks at two things:
minimum number of consumers
maximum number of messages

Based on your transport from sensu-cli info it “seems” healthy as you
have 1 consumer and no messages in the queue.

What are you doing for a sensu-cli health command?

  • This should return healthy in the above scenario
    sensu-cli health --consumers 1 --messages 100

You can also mimic this right in the browser:
http://127.0.0.1:4567/health?consumers=1&messages=100

If you get a 204, it is healthy.

Thanks,
Bryan

On Wed, Oct 15, 2014 at 2:26 PM, clay tyler thecla...@gmail.com wrote:

Is there a tool
(or some steps)
that’ll give me a clue to what to do?

This is a new install
ruby 1.9.3
on Centos 6.5

sensu-cli info

sensu: {“version”=>“0.14.0”}
transport: {“keepalives”=>{“messages”=>0, “consumers”=>1},
“results”=>{“messages”=>0, “consumers”=>1}, “connected”=>true}
redis: {“connected”=>true}

sensu-cli client list

name: ws00
address: localhost
subscriptions: [“all”]
version: 0.14.0
timestamp: 1413400367

4

FIXED

FIXED - replaced /etc/sensu/conf.d/*.json files with (near) stock copy of config.json.example

···

On Wednesday, October 15, 2014 2:26:14 PM UTC-5, clay tyler wrote:

Is there a tool
(or some steps)

that’ll give me a clue to what to do?

This is a new install

ruby 1.9.3

on Centos 6.5

sensu-cli info

sensu: {“version”=>“0.14.0”}

transport: {“keepalives”=>{“messages”=>0, “consumers”=>1}, “results”=>{“messages”=>0, “consumers”=>1}, “connected”=>true}

redis: {“connected”=>true}

sensu-cli client list

name: ws00

address: localhost

subscriptions: [“all”]

version: 0.14.0

timestamp: 1413400367