Status Info = Warning, but Status = Unknown

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of John Christian
> Sent: Tuesday, September 06, 2005 4:09 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Status Info = Warning, but Status = Unknown
> 
> Hello,
> 
> I'm looking at the "Service Detail" section on the web
> GUI. Most hosts/services are working fine, but a few
> services seem confused. Their Status Information (7th
> column) is "WARNING [details...]" or "OK [details...]"
> but their Status (3rd column) is still listed as
> "UNKNOWN".

Nagios determines the Status (3rd column) from the plugin exit code
_only_. The Status Information is just an explanation for human
readability. It would appear that the plugins you are using are exiting
with a different status code than the plugin output would suggest they
should be.
 
> The problem *seems* to be more common when using Jeff
> Scott's check_load_remote 1.1 or check_uptime_remote
> 1.1 in combination with the remote host running
> Sun_SSH_1.0.1. Sometimes they will clear-up (display
> statuseses that make sense) but usually they're in
> status UNKNOWN even though the status information
> shows WARNING or OK.
> 
> The same scripts used against hosts running
> OpenSSH_4.1 are always fine.

Is this a hint that you're executing these plugins via check_by_ssh?
Perhaps check_by_ssh isn't passing the exit code back properly or more
likely it's encountering problems itself and you're seeing it's exit
code. Have you tried running the commands by hand as the nagios user
exactly as they are defined from your central machine and verify the
exit code (echo $?)?

> 
> Why is Nagios displaying conflicting information?

The plugin exit code (very important) doesn't agree with the plugin
output (not important, at least to nagios). The 'plugin' in your case
could be check_load_remote or check_by_ssh if that's what you're using.

> How do I force Nagios to 'forget' everything about a
> host and start fresh?

If you're not using state retention, restart nagios. If you're using
state retention, stop nagios, remove the retention file and restart
nagios.

> Other tips?

Check your sshd log on the remote host for errors. Enable sshd debug
mode.

--
Marc


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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