I recently installed Nagios 3.2.3 and things appear to be working fine.
The "Duration" column (which shows the uptime of a host) appears to have
incorrect information for a few hosts in a hostgroup. After I click on the host
that has the incorrect information to see more detailed stats, the "Host
Status" shows the correct uptime, a duration that matches the rest of the hosts
in the group. The check_ping service was activated at the same time for all the
hosts in the group.
Is this a bug? I assume the "Duration" column and "Host Status" info should
match, right?
- Ahmed
______________________________________________________________________
Confidentiality Notice: The contents of this email, all related responses and
any files and/or attachments transmitted with it are CONFIDENTIAL and are
intended solely for the use of the individual or entity to whom they are
addressed. This email may contain legally privileged information and may not be
disclosed, copied or distributed to anyone without authorization from the
email's originator. It is strictly prohibited for unaddressed individuals or
entities to take any action based on upon information contained in this email.
If you have received this email in error, please notify the sender immediately
and delete all copies from your system.
______________________________________________________________________
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Nagios-users mailing list
Nagios-users@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
