passif_check behavior

[nelmo]

Hi,

i have got a problem whith behavior of check_passif

We uses check_dummy for differently passif_check .
We uses this plugin habitualy for submit an CRITICAL state if Nagios don't receive status after 1h00 .... .

Last day, i have find a déclaration (in my nagios configuration) of check_dummy for a passive_check without args déclaration. It's bad, but is not the question. I think i have miss déclaration for this service and i must clean that ....

But,
Service is configured for passive_check. But, at a random time, i see an alert for this service : check_dummy: Could not parse arguments.
I thinks it's logical because check_dummy is executed without args ....

For why nagios execute this check although his déclaration of passive check = 1 ?

What append when nagios restart ? It's a problem for read status.dat at a random time ?


Excuse for my bad english :/


--
Nelmo,

[jsmurphy]

I'm not 100% sure I understand your question but I think it is "Why does check_dummy get executed when the check is set to passive?"

If you assign a command to a passive check and set a freshness threshold, when that freshness threshold is crossed the command is executed. The freshness threshold is the time that service has gone without receiving any information.

I'm not sure however I understand the second parts of your question... "What append when nagios restart ? It's a problem for read status.dat at a random time ?" I'm not sure what you are asking, you might need to clarify that for me.

[nelmo]

hi, thanks for your reply.

In fact, if i add a check_dummy on service without arguments and without freshness, with check_passif =1, I think this check as never executed by nagios. Just an alert if a message is reveive for this service. But, when i have test that, at a random time, i have see an alert type : check_dummy: Could not parse arguments.

I search to find why Nagios have éxecute this check.

It's not really a problem, but i would understand this behavior.

Thanks,

[nelmo]

thanks for your reply

In fact, when i assign a command check_dummy configured without arguments and without freshness, and with option passive_check enable, Nagios, at a random time, post an alert type : check_dummy: Could not parse arguments. This error is explain because i haven't défine args for chedk_dummy. OK, but :

In this configuration, Why nagios execute this check ? This behavior arrived sometimes and i just want understand this.

Best regards,

[mguthrie]

If you have active checks enabled for this host or service, Nagios will run the check_dummy at the regular check_interval. I'm guessing that's what's happening here. Make sure active checks are disabled for this host/service. If it's still having an issue, go ahead and post the host/service configuration that's having the issue.

[nelmo]

Ok,

I look that tomorrow.

Thanks you for this way


Best regards,