check host alive by passive

[D.Parise at iaea.org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

This will not work if the service is passive, as the command_line will be check_dummy that will always return the value that is imposed in the configuration.

Thanks,

Davide


- -----Original Message-----
From: Janet Post [mailto:janetpost at gmail.com] 
Sent: Thursday, 23 August 2007 14:29
To: PARISE, Davide
Subject: Re: [Nagios-users] check host alive by passive

Hello Davide,

It sounds like you need to make your service check into a host check.
You can do this by changing your check_host command in your hosts.cfg
file.  For example:

Change the default:

define host{
        ...
        check_command                   check-host-alive
        ...
}

to:

define host{
        ...
        check_command                   check-host-alive-custom
        ...
}

and in your checkcommands.cfg file add the check thusly:

define command{
        command_name    check-host-alive-custom
        command_line       path/to/command
        }


This will turn your service check into a host check.  You will still
need to leave your service check in place because host checks are not
performed unless a service check comes back with an error.   This way,
when the service check fails, the host will immediately be checked.
And since the two checks are the same, the host check will also fail,
and give you the host down status you require.

Janet




On 8/23/07, D.Parise at iaea.org <D.Parise at iaea.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Not really: the point is that I want the host to be down when a certain service is down and the service is passive. I am monitoring some systems connected in dial up, that why I can't use active or ping.
>
> Regards,
>
> Davide
>
>
> - -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Hugo van der Kooij
> Sent: Thursday, 23 August 2007 07:57
> To: Nagios Users mailinglist
> Subject: Re: [Nagios-users] check host alive by passive
>
> On Wed, 22 Aug 2007, D.Parise at iaea.org wrote:
>
> > One question: how can I use something like check host alive only with
> > passive checks? I have for one host only one passive service, and I
> > would like the status of the host to go to critical if this service is
> > critical.
>
> Hosts and services are two different things. It sounds like you want to
> abandon that concept.
>
> Hugo.
>
> - --
>         hvdkooij at vanderkooij.org        http://hugo.vanderkooij.org/
>             This message is using 100% recycled electrons.
>
>         Some men see computers as they are and say "Windows"
>         I use computers with Linux and say "Why Windows?"
>         (Thanks JFK, for this quote of George Bernard Shaw.)
>
> - -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
> -----BEGIN PGP SIGNATURE-----
> Version: 9.5.3 (Build 5003)
>
> wsBVAwUBRs0s8h+K8IX89MUJAQiz3gf/XjsoXf1Q9yBGCgDHltcpvLAyukdXMGhc
> buD+s/n2DzTCc/VfbWWdVCWy60IPdN0rFpmXXnrB93h0JtYAKg2HZNjAEnVQFZL2
> cxaQDFGLms7Q6Rc54L7kHvdjUGa0QJ97MuwKT2yr3r2TcpjERL1xpE106zGg6gaI
> CSpsIbECafwehGN8H+tAMppBYK6AmTzVoqj5+c5EsA5mijrJS83sorwZ+uGsjUiV
> lUWjidTSQtrThFQ68KNoch+mRWK+ETwgTsTAD7CmatU9nMuCAXqI+oLa6nno1mRV
> wWt5dq+pBzIqndTR0noch+wfPpGlsDu5FHX/X4E4OUWmUg7HmrSRvg==
> =DO2l
> -----END PGP SIGNATURE-----
>
> This email message is intended only for the use of the named recipient.
> Information contained in this email message and its attachments may be
> privileged, confidential and protected from disclosure. If you are not the
> intended recipient, please do not read, copy, use or disclose this
> communication to others. Also please notify the sender by replying to this
> message and then delete it from your system.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>

-----BEGIN PGP SIGNATURE-----
Version: 9.5.3 (Build 5003)

wsBVAwUBRs2zkB+K8IX89MUJAQhaGQf/Y6tzIW9u5tKewV6B2Mfar8zmUWSMlYG1
6kj7v9rlrsSwg6TbiJQ2CgkrA5BorkSvPGFbaOXmmTnHiqhH8UchweC24VZUmoRq
DJoXO1Y7Ar0Pmxwq1otCvw4XT/0eGcfNyJHYXmeLSl0l4eIQNY8TmPboUJek0mk3
9fgLUBRCkDxLLBFnlzNtzPzs8EniGlpzsYkd5M6iBlJ7QqO+Hk+9ETLgr7mN5O8g
s4mn9KOgJ1VsW6pV6C6fZ7CVhrSJ1iLH4tItCgRSDaSdAPHweeRl2ENvX/ghGFrj
qSzIwSuW096nkd7tI2+Ya/dCJJMbHpEG5bgfEUsGCc3xbMXJP9hkTg==
=9BAo
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null