Database Woes, status information.

[Marc Powell]

> -----Original Message-----
> From: Paul Hirschorn [mailto:phirschorn at brave.net]
> Sent: Tuesday, November 25, 2003 2:19 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Database Woes, status information.
> 
> I am experiencing a problem when using the database for status
> information.
> The information is successfully written and updated, however if I
restart
> nagios It takes like 20 minutes to re-check host status.  Even after
> running
> I am getting "(Host assumed to be up) "  in the Host Status Details
For
> All
> Host Detail interface.  However the service detail is returning the
> correct
> information.  i.e. TCP OK - 0.001 second response time on port 80.  I
am
> using mysql same authentication for all database types.

This is not a problem, it's coded behavior and is the same with or
without database support. Nagios never checks the status of a host until
a service on that host fails. The logic is that if a service on a host
is working then the host must be up so why check it (hence it's assumed
to be up).

--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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