[Check_mk (english)] Why CRIT?

Archive checkmk-en
1

Anyone know why this is coming up as CRIT?

Service Overall state

Event OK → CRITICAL

Address 192.168.168.86

Date / Time Mon Aug 20 09:11:04 CDT 2018

Plugin Output CRIT - Entity state: redCRIT, Power state: poweredOn

Additional Output

Host Metrics rta=0.149ms;200.000;500.000;0; pl=0%;80;100;; rtmax=0.197ms;;;; rtmin=0.115ms;;;;

Service Metrics

So…it’s powered on…why CRIT?

cmk -D hostname shows no issues, CRITs, alarms, nor does connecting to the VMware host and checking out the health. Everything is green across the board.

Documentation states: CRIT if vsphere reports overall state of red or grey or if the ESX host is in power state poweredOff

We can see it’s not powered off and I can’t find any health issues whatsoever.

Brian

2

Hi Brian,

This state is reported from the ESX host them self or your vCenter. It is possible to run the special agent command with the addition if “–tracefile ” option to get the raw response from your queried system.

With this trace file you can check for the health output.

There inside should be some text about the reported issue.

Best regards

Andreas

···

Brian Binder via checkmk-en checkmk-en@lists.mathias-kettner.de schrieb am Mo., 20. Aug. 2018 um 17:00 Uhr:

Anyone know why this is coming up as CRIT?

Service Overall state

Event OK → CRITICAL

Address 192.168.168.86

Date / Time Mon Aug 20 09:11:04 CDT 2018

Plugin Output CRIT - Entity state: redCRIT, Power state: poweredOn

Additional Output

Host Metrics rta=0.149ms;200.000;500.000;0; pl=0%;80;100;; rtmax=0.197ms;;;; rtmin=0.115ms;;;;

Service Metrics

So…it’s powered on…why CRIT?

cmk -D hostname shows no issues, CRITs, alarms, nor does connecting to the VMware host and checking out the health. Everything is green across the board.

Documentation states: CRIT if vsphere reports overall state of red or grey or if the ESX host is in power state poweredOff

We can see it’s not powered off and I can’t find any health issues whatsoever.

Brian

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

Manage your subscription or unsubscribe

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

3

I am going to investigate this some more. Thanks very much for this information because I haven’t seen this on any of my systems before. I’ll see what I can find and post back.

Thanks, Andreas!!!

···

From: Andreas Döhler andreas.doehler@gmail.com
Reply: Andreas Döhler andreas.doehler@gmail.com
Date: August 22, 2018 at 9:34:23 AM
To: Brian Binder brianjbinder@icloud.com
Cc: Check_MK List checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] Why CRIT?

Hi Brian,

This state is reported from the ESX host them self or your
vCenter. It is possible to run the special agent command with the
addition if “–tracefile ” option to get the raw
response from your queried system.

With this trace file you can check for the health
output.

There inside should be some text about the reported
issue.

Best regards

Andreas

Brian Binder via checkmk-en checkmk-en@lists.mathias-kettner.de
schrieb am Mo., 20. Aug. 2018 um 17:00 Uhr:

Anyone know why this is coming up as CRIT?

Service Overall state

Event OK → CRITICAL

Address 192.168.168.86

Date / Time Mon Aug 20 09:11:04 CDT 2018

Plugin Output CRIT - Entity state: redCRIT, Power
state: poweredOn

Additional Output

Host Metrics rta=0.149ms;200.000;500.000;0;
pl=0%;80;100;; rtmax=0.197ms;;;; rtmin=0.115ms;;;;

Service Metrics

So…it’s
powered on…why CRIT?

cmk -D
hostname shows no issues, CRITs, alarms, nor does connecting to the
VMware host and checking out the health. Everything is green
across the board.

Documentation states: CRIT if vsphere reports overall state of
red or grey or if the ESX host is in power state
poweredOff

We can see
it’s not powered off and I can’t find any health issues
whatsoever.

Brian

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

Manage your subscription or unsubscribe

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

4

Well of course I had 2 hosts exhibiting this behavior and I’m ready to test this out aaaaand they reset on their own.

I was going to look at this thread as well for a little more information and follow what was mentioned (which is what you mentioned): http://checkmk-en.mathias-kettner.narkive.com/rOeQoW5e/check-mk-english-agent-vsphere-hw-sensors-not-clearing

So, I’ll do that next time it happens.

Thanks again :wink:

···

From: Brian Binder brianjbinder@icloud.com
Reply: Brian Binder brianjbinder@icloud.com
Date: August 22, 2018 at 9:39:08 AM
To: Andreas Döhler andreas.doehler@gmail.com
Cc: Check_MK List checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] Why CRIT?

I am going to investigate this some more. Thanks very much
for this information because I haven’t seen this on any of my
systems before. I’ll see what I can find and post back.

Thanks, Andreas!!!

From: Andreas Döhler andreas.doehler@gmail.com

Reply: Andreas Döhler
andreas.doehler@gmail.com

Date: August 22, 2018 at 9:34:23
AM

To: Brian Binder brianjbinder@icloud.com

Cc: Check_MK List checkmk-en@lists.mathias-kettner.de

Subject: Re: [Check_mk (english)]
Why CRIT?

Hi Brian,

This state is reported from the ESX host them self or
your vCenter. It is possible to run the special agent command with
the addition if “–tracefile ” option to get the
raw response from your queried system.

With this trace file you can check for the health
output.

There inside should be some text about the reported
issue.

Best regards

Andreas

Brian Binder via checkmk-en checkmk-en@lists.mathias-kettner.de
schrieb am Mo., 20. Aug. 2018 um 17:00 Uhr:

Anyone know why this is coming up as CRIT?

Service Overall state

Event OK → CRITICAL

Address 192.168.168.86

Date / Time Mon Aug 20 09:11:04 CDT
2018

Plugin Output CRIT - Entity state: redCRIT,
Power state: poweredOn

Additional Output

Host Metrics rta=0.149ms;200.000;500.000;0;
pl=0%;80;100;; rtmax=0.197ms;;;; rtmin=0.115ms;;;;

Service Metrics

So…it’s powered on…why CRIT?

cmk -D
hostname shows no issues, CRITs, alarms, nor does connecting to the
VMware host and checking out the health. Everything is green
across the board.

Documentation states: CRIT if vsphere reports overall
state of red or grey or if the ESX host is in power state
poweredOff

We can
see it’s not powered off and I can’t find any health issues
whatsoever.

Brian

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

Manage your subscription or unsubscribe

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

Manage your subscription or unsubscribe

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en