Newbie needs help...."unknown" status?

[StacyWV]

Hi, Nagios Newbie here.....I am setting up Nagios to monitor multiple servers on my network. (Win 2003 server machines). I am running Nagios 3.2.1 on Ubuntu linux.

Three of my services being monitored work perfectly:
Memory Usage
NSClient++ Version
Uptime

The other four only ever return a status of "Unknown":
C: Drive Space
CPU Load
Explorer
W3SVC

I have checked the configuration files for the windows.cfg and from all I can tell, it looks OK, as does the nagios.cfg and the command.cfg.

Here is a sample of my service definitions for the checks *not* working:

Code: Select all

define service{
	use			        generic-service
	host_name		myserver
	service_description	CPU Load
	check_command	check_nt!CPULOAD!-1 5,80,90
	}

define service{
	use			        generic-service
	host_name		myserver
	service_description	C:\ Drive Space
	check_command	check_nt!USEDDISKSPACE!-l c -w 80 -c 90
	}

define service{
	use			        generic-service
	host_name		myserver
	service_description	W3SVC
	check_command	check_nt!SERVICESTATE!-d SHOWALL -1 W3SVC
	}

define service{
	use			        generic-service
	host_name		myserver
	service_description	Explorer
	check_command	check_nt!PROCSTATE!-d SHOWALL -l Explorer.exe
	}

Any pointers are greatly appreciated!!

~Stacy

[mguthrie]

I would check the configuration file on the NSClient, not all of the checks are enabled on the client by default, so you'll have to turn them on for it to send the data.

If that doesn't fix it, can you send the full "status information" message for each of these services. The error messages "should" point to where the problem is.

[tonyyarusso]

You also probably need to enable the "allow_arguments" (or something like that) setting in the NSClient++ config.

[StacyWV]

All of the modules in the nsc.ini are enabled with the exception of CheckWMI.dll:

Code: Select all

[modules]
NRPEListener.dll
NSClientListener.dll
FileLogger.dll
CheckSystem.dll
CheckDisk.dll
CheckEventLog.dll
CheckHelpers.dll
;# NSCLIENT++ MODULES
;# A list with DLLs to load at startup.
;  You will need to enable some of these for NSClient++ to work.
; ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
; *                                                               *
; * N O T I C E ! ! ! - Y O U   H A V E   T O   E D I T   T H I S *
; *                                                               *
; ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
FileLogger.dll
CheckSystem.dll
CheckDisk.dll
NSClientListener.dll
NRPEListener.dll
SysTray.dll
CheckEventLog.dll
CheckHelpers.dll
;CheckWMI.dll
;
; Script to check external scripts and/or internal aliases.
CheckExternalScripts.dll
;
; NSCA Agent if you enable this NSClient++ will talk to NSCA hosts repeatedly (so dont enable unless you want to use NSCA)
NSCAAgent.dll
;
; LUA script module used to write your own "check deamon".
LUAScript.dll
;
; RemoteConfiguration IS AN EXTREM EARLY IDEA SO DONT USE FOR PRODUCTION ENVIROMNEMTS!
;RemoteConfiguration.dll
; Check other hosts through NRPE extreme beta and probably a bit dangerous! :)
NRPEClient.dll
; Extreamly early beta of a task-schedule checker
CheckTaskSched.dll

I enabled the allow-arguments (set it to = 1 ?) and re-ran the check on that particular server with the same results.

Here are the status information messages showing in the web interface for these services:

C:\ Hard Drive Space

Code: Select all

Current Status:   UNKNOWN   (for 5d 23h 18m 17s) 
Status Information: Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]
 
Performance Data:  
Current Attempt: 3/3  (HARD state) 
Last Check Time: 09-08-2010 09:21:30 
Check Type: ACTIVE 
Check Latency / Duration: 0.161 / 0.028 seconds 
Next Scheduled Check:   09-08-2010 09:31:30 
Last State Change: 09-02-2010 10:07:30 
Last Notification: 09-08-2010 09:21:34 (notification 144) 
Is This Service Flapping?   NO   (0.00% state change) 
In Scheduled Downtime?   NO   
Last Update: 09-08-2010 09:25:44  ( 0d 0h 0m 3s ago) 

CPU Load

Code: Select all

Current Status:   UNKNOWN   (for 5d 23h 18m 11s) 
Status Information: Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]
 
Performance Data:  
Current Attempt: 3/3  (HARD state) 
Last Check Time: 09-08-2010 09:22:49 
Check Type: ACTIVE 
Check Latency / Duration: 0.171 / 0.027 seconds 
Next Scheduled Check:   09-08-2010 09:32:49 
Last State Change: 09-02-2010 10:08:49 
Last Notification: 09-08-2010 09:22:54 (notification 144) 
Is This Service Flapping?   NO   (0.00% state change) 
In Scheduled Downtime?   NO   
Last Update: 09-08-2010 09:26:54  ( 0d 0h 0m 6s ago) 

Explorer

Code: Select all

Current Status:   UNKNOWN   (for 5d 23h 17m 29s) 
Status Information: Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]
 
Performance Data:  
Current Attempt: 3/3  (HARD state) 
Last Check Time: 09-08-2010 09:24:08 
Check Type: ACTIVE 
Check Latency / Duration: 0.149 / 0.028 seconds 
Next Scheduled Check:   09-08-2010 09:34:08 
Last State Change: 09-02-2010 10:10:08 
Last Notification: 09-08-2010 09:24:14 (notification 144) 
Is This Service Flapping?   NO   (0.00% state change) 
In Scheduled Downtime?   NO   
Last Update: 09-08-2010 09:27:34  ( 0d 0h 0m 3s ago) 

W3SVC

Code: Select all

Current Status:   UNKNOWN   (for 5d 22h 44m 12s) 
Status Information: Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]
 
Performance Data:  
Current Attempt: 3/3  (HARD state) 
Last Check Time: 09-08-2010 09:27:52 
Check Type: ACTIVE 
Check Latency / Duration: 0.175 / 0.029 seconds 
Next Scheduled Check:   09-08-2010 09:37:52 
Last State Change: 09-02-2010 10:43:52 
Last Notification: 09-08-2010 08:57:54 (notification 143) 
Is This Service Flapping?   NO   (0.00% state change) 
In Scheduled Downtime?   NO   
Last Update: 09-08-2010 09:28:04  ( 0d 0h 0m 0s ago) 

I appreciate the help!! Let me know if there is any other info that could be helpful in tracking this problem down.

~Stacy

[mguthrie]

I guess the next step would be to check your arguments in the actual commandline to see what the output is.

Code: Select all

cd /usr/local/nagios/libexec
./check_nt (your commandline arguments)

I'd try messing with that until you get something returned for a status. There may be an invalid or missing argument or something in the command definition and that's the best way to check it.