Nagios Support Forum

The check_procs can monitor processes. Lots of options.

Here are my services.cfg entries define service{ use local-service host_name xxxxxxxx service_description NSCP VERSION check_command check_nt!CLIENTVERSION max_check_attempts 3 notification_interval 480 notification_options c,u contact_groups denver } define service{ use local-service,srv-pnp host_n...

The following page will give you the instructions for installing and configuring NSClient++. As can be seen, cpu, memory, disk space, service states, etc. are available from NSClient++ (via check_nt) http://nagios.sourceforge.net/docs/3_0/monitoring-windows.html The NRPE for WIN instructions can be ...

Also look in the nagios.log file.

What is the error? What is happening? Check the logs to see if anything stands out (status.dat, perfdata.log, messages, etc)

From a command line - yes.
To get the syntax, append the -h switch. Example
/usr/local/nagios/libexec/check_ping -h

The check_nt does more than CPU. It will do disk usage, memory, paging file Another solution, one that I did, is to install cygwin. Then you can install the nrpe and create UN*X like shell scripts for monitoring. If you cannot install cygwin, look again at check_nt. I did a google search using only ...

The NDO needs to be started first.

Stop nagios, start NDO, start nagios

Change the max_check_attempts from 1 to 2 and change the retry_check_interval from 3 to 5. The max_check_attempts is saying that on the 1st check that a problem is found, send an alert. Changing that to 2 with a retry of 5 says, on 1st check, if problem found then retry the check in 5 min, if proble...

For your virtual definition, you have DocumentRoot=/usr/local/nagios/share. For ScriptAlias you have /nagios/cgi-bin. Not sure how you want to setup but here is an example from my config (nagios is installed in /usr/local/nagios) DocumentRoot=/usr/local ScriptAlias /cgi-bin /usr/local/nagios/cgi-bin...