check_nagios and ps problem

[Voon, Ton]

Copying to nagiosplug-help list. Can future replies remove the nagios-users
list

Which version of check_nagios? Which OS? What does configure say your ps
command is?

There have been some changes to check_nagios so that it uses the same ps
command as check_procs. Can you try with the latest CVS version - use the
snapshot at http://nagiosplug.sf.net/snapshot. Use the -v flag to see what
is being seen.

Ton

> -----Original Message-----
> From:	Shawn McCool [SMTP:smccool at ascendantmedia.com]
> Sent:	Wednesday, March 26, 2003 6:53 PM
> To:	nagios-users at lists.sourceforge.net
> Subject:	[Nagios-users] check_nagios and ps problem
> 
> check_nagios gets a ps list and searches for the final arguement in the
> check_nagios command line
>  
> nagios_check_command=/usr/local/nagios/libexec/check_nagios
> /usr/local/nagios/var/status.log 5 '/usr/local/nagios/bin/nagios'
>  
> In this case it checks for /usr/local/nagios/bin/nagios
>  
>  
>  
> The Documentation:
>  
> # Note: If you are using the check_nagios plugin here, the first
> # argument should be the physical path to the status log, the 
> # second argument is the number of minutes that the status log 
> # contents should be "fresher" than, and the third argument is the
> # string that should be matched from the output of the 'ps' 
> # command in order to locate the running Nagios process.  That
> # process string is going to vary depending on how you start
> # Nagios.  Run the 'ps' command manually to see what the command
> # line entry for the Nagios process looks like.
>  
> Suggest that i should run 'ps' to see what it returns.
>  
> Wether I am the Nagios user or root ps has inappropriate return values for
> this check command.
>  
> # ps 
>   PID TTY          TIME CMD
>   534 tty1     00:00:00 mingetty
>   535 tty2     00:00:00 mingetty
>   536 tty3     00:00:00 mingetty
>   537 tty4     00:00:00 mingetty
>   538 tty5     00:00:00 mingetty
>   539 tty6     00:00:00 mingetty
>  1860 pts/8    00:00:00 bash
> 14765 pts/3    00:00:00 bash
> 11225 pts/6    00:00:00 bash
> 12483 pts/9    00:00:00 bash
> 12490 pts/9    00:00:01 ssh
> 12509 pts/10   00:00:00 bash
> 12540 pts/10   00:00:00 ssh
> 12774 pts/11   00:00:00 bash
> 12805 pts/11   00:00:00 ssh
> 19339 pts/2    00:00:00 bash
> 22771 pts/5    00:00:00 shell
> 22772 pts/5    00:00:00 ssh
> 24309 pts/12   00:00:00 bash
> 28146 pts/6    00:00:01 ssh
> 28993 pts/13   00:00:00 bash
> 29269 pts/12   00:00:00 ssh
> 29309 pts/14   00:00:00 bash
> 29316 pts/14   00:00:00 ssh
>  8053 pts/15   00:00:00 bash
> 11875 pts/0    00:00:00 bash
> 14706 pts/2    00:00:00 ps
>  
> Although I assure you nagios IS running
>  
> # ps waux | grep nagios
> nagios   12253  0.0  0.0  1560  880 ?        S    12:32   0:00 ./nagios -d
> ../etc/nagios.cfg
>  
> Is there a way to change the command line for ps so that I can have it
> return the appropriate information?


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
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