Setting up a passive check problem

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Lewis Getschel
> Sent: Tuesday, April 12, 2005 11:42 AM
> To: Nagios Users
> Subject: [Nagios-users] Setting up a passive check problem
> 
> All-
>     After 8 months of tweaking our 1.2 system with active checks (that
> work fine), I now find myself at a loss to setup a passive "service
> check".
> 
> I have 5 file servers in a "farm" that log themselves to a single
syslog
> file.
> I wrote a script that deals with that and can submit the passive
result
> to Nagios to be processed.
> 
> My problem _seems_ to be my understanding of the basic setup for a
> passive service check.
> The docs say: "...service checks to Nagios, a service must have
already
> been defined in the object configuration file
> <http://nagios.sourceforge.net/docs/1_0/configobject.html>"

This means that when you submit an entry to the command file, there must
be a matching host_name and service_description that nagios already
knows about or it will be ignored.

 
> What "check_command" does a passive service "need"? (it needs a
> command???) I don't want nagios to _DO_ anything, just accept the
> passive results from another process.
> 
> When I tried to leave a check_command out, nagios complains "... check
> command is NULL"

As you can see, there must be one defined. What it is depends on if
you're going to be using active checks or freshness checking or not. If
you are going to be using them then the command must be valid as nagios
will actively execute it to determine the state of the service at the
expiration of the freshness interval.

If you are not using freshness checking than the command can be anything
you like. I use the same command that is executed on my distributed
servers for consistency but it could be check_dummy or any other command
as it will never actually be run. 



> services.cfg:
> define service{
>         use                               linux-service
>         name                            ibm_disk_array_status
>         service_description             ibm_disk_array_status
>         active_checks_enabled           0
>         passive_checks_enabled          1
>         check_command                   check_passive_disklog
>         register                        0
>         }
> 
> commands.cfg:
> # 'ibm_disk_array_status' command definition
> define command{
> command_name    check_passive_disklog
> command_line    $USER1$/check_passive_disklog
>         }
> 
> hosts.cfg:
> define service{
>      use           ibm_disk_array_status
>      host_name     fs004,fs005,fs006,fs007,fs008
> }
> 

I haven't used this type of construct personally but it looks fine.

> Can someone point out where I'm going wrong to simply allow a service
> status to be accepted passively, please.

Instead of making an assumption about what your problem is, why don't
you tell us the symptoms and error messages that you are seeing?

--
Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
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