AW: Nagiostat

[Schwenderman, Jack]

Well, there are certainly enough posts in this list to indicate that
this odd behavior needs a little more documentation.  Like maybe instead
of the * in the config file, put a one line comment like... 

"Retaining State also retains this setting and your configuration
changes won't take effect unless you delete your status.sav file."

Just my 2cents


-----Original Message-----
From: Marc Powell [mailto:marc at ena.com]
Sent: Wednesday, October 27, 2004 3:02 PM
To: Schwenderman, Jack; nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] RE: AW: Nagiostat


 

________________________________

From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of
Schwenderman, Jack
Sent: Wednesday, October 27, 2004 1:07 PM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] RE: AW: Nagiostat



I've been busting my balls on the same issue all day.  I finally found
something in a prior post that helped me solve my problem.  I suspect
that this may be your problem too.

Delete or Rename your status.sav file.  This is in ${prefix}/var/ 

This is only supposed to save the last state of each host or service,
but it must be a bug in Nagios or the Docs, because it seems to also
save the fact that Performance Data is turned OFF.  As soon as I removed
this file and restarted Nagios, I finally saw that performance data was
enabled.

<marc>

It's not a bug and it's documented --

http://nagios.sourceforge.net/docs/1_0/xodtemplate.html

Retention Notes 

It is important to point out that several directives in host and service
definitions may not be picked up by Nagios when you change them. Host
and service directives that can exhibit this behavior are marked with an
asterisk (*). The reason for this behavior is due to the fact that
Nagios chooses to honor values stored in the state retention file over
values found in the config files, assuming you have state retention
enabled on a program-wide basis. 

One way to get around this problem is to disable the retention of
non-status information using the retain_nonstatus_information directive
in the host and service definitions. Disabling this directive will cause
Nagios to take the initial values for these directives from your config
files, rather than from the state retention file when it (re)starts.
Using this option is not recommended, as it may result in some
unexpected (from your point of view) results. 

Alternatively, you can issue the appropriate external command or change
the value of the host or service directive via the web interface, so
that it matches what you've changed it to in the config files. This is
usually done by using the extended information CGI. This option takes a
bit more work, but is preferable to disabling the retention of
non-status information (mentioned above). 
...

process_perf_data *: This directive is used to determine whether or not
the processing of performance data is enabled for this host. Values: 0 =
disable performance data processing, 1 = enable performance data
processing.  

</marc>


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_______________________________________________
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