Really dumb question...Linux Client?

[Marc Powell]

On Jan 21, 2009, at 2:08 PM, Marty Nelson wrote:

> Hi all.
>
> I have what’s probably as simple of a question as there is.  I have  
> Nagios running on a dedicated machine, and so far it’s monitoring  
> all of my Windows server, switches and printers.  What I have yet to  
> figure out is how to monitor my Linux servers.  Currently it’s  
> monitoring itself, but that’s about the extent of the Linux  
> monitoring ;p
>
> I feel like I’ve looked all over the web for an answer and have yet  
> to come across one, so I’m hoping you kind folks can help.  I’m a  
> Linux noob, but was able to get Nagios running and monitoring what  
> it’s currently doing, but could really use some help with the Linux  
> monitoring side of things.

While not fully fleshed out, the Nagios documentation does  
specifically talk about this and gives you some pointers. It's always  
a good place to look when you have questions.

http://nagios.sourceforge.net/docs/3_0/monitoring-linux.html

Essentially there are three common ways -
	-active checks from the nagios machine using NRPE to run plugins  
living on the remote host
	-active checks from the nagios machine using check_by_ssh (configured  
with authorized_keys access on the remote host) to run plugins living  
on the remote host
	-passive checks with NSCA. plugins on the remote host are run out of  
cron or some other method and their results sent to the nagios machine  
using send_nsca.

I use all three in various situations.

--
Marc


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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