Hi!,
When i increase "normal_check_interval" value from default(10min.) to
15min. or greater for any service, nagios stops receiving performance data
in .rrd files.
I also checked it with increasing
"perfdata_timeout<http://nagios.sourceforge.net/docs/3_0/configmain.html#perfdata_timeout>"
value but it didn't work.
Nagios version: Nagios Core 3.5.0 or 3.2.3
plugin version: nagios-plugins-1.4.16
Nagiosgraph version: nagiosgraph-1.4.4
OS: Redhat 5.8 64bit
Service configuration:
define service{
use generic-service
host_name Server-10
service_description Disk-Boot Partition Free Space
check_command check_nrpe!check_disk_boot_partition
*normal_check_interval 30*
}
*PS*: Services with default "normal_check_interval" value, giving
perfdata continually.
Any help would be appreciated.
Thanks,
Pankaj Sain
*Please do not print this mail unless it is necessary...*
This e-mail, together with any attachments, is confidential, and may be
privileged. It may be read, copied and used only by the intended recipient.
Access to this e-mail or any of its attachments by anyone else and
disclosure or copying of its contents or any action taken (or not taken) in
reliance on it, is unauthorized and may be unlawful. If you have received
it in error, please notify the sender immediately by e-mail or telephone
and destroy all copies of this message and any attachments.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
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
