<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=304302114-12042007>I hadn't really had to pay attention to the perfdata
file before. From looking at the contents of my perfdata file, it looks
like it would normally be cleared or truncated or whatever Nagios does on its
own perhaps daily. The old data in the file was only about 24 hours
old. Looking at the file today, I see it's still
growing.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=304302114-12042007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=304302114-12042007>Now that someone else is reporting this problem after
going to 2.9, I'm suspicious of a bug in 2.9. The only thing I saw
in the changelog relating to this file was:</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=304302114-12042007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT><SPAN class=304302114-12042007>
<LI><FONT face=Arial color=#0000ff size=2>Fix for incorrect performance data
file write/append mode options</FONT></LI></DIV>
<DIV dir=ltr><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV dir=ltr><SPAN class=304302114-12042007><FONT face=Arial color=#0000ff
size=2>Perhaps there's a relationship.</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN class=304302114-12042007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN class=304302114-12042007><FONT face=Arial color=#0000ff
size=2>Mark</FONT></SPAN></DIV>
<DIV dir=ltr align=left></SPAN></FONT> </DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Einar Indridason
[mailto:einar.indrida@gmail.com] <BR><B>Sent:</B> Thursday, April 12, 2007
9:31 AM<BR><B>To:</B> Frost, Mark {PBG}<BR><B>Cc:</B>
nagios-users@lists.sourceforge.net<BR><B>Subject:</B> Re: [Nagios-users]
Having issue with process-service-perfdata running too
long<BR></FONT><BR></DIV>
<DIV></DIV><BR>
<DIV><SPAN class=gmail_quote>On 4/11/07, <B class=gmail_sendername>Frost, Mark
{PBG}</B> <<A
href="mailto:mark.frost1@pepsi.com">mark.frost1@pepsi.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid"><BR>Hello. I'm
running Nagios 2.9 with Nagiosgraph 0.8.2. This
combination<BR>has worked well for us for a while now.<BR><BR>My perdata
file has grown rather large:<BR><BR>$ wc -l perfdata.log<BR>817880
perfdata.log <BR></BLOCKQUOTE>
<DIV> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">I
like keeping the historical data, but I guess that would mean my <BR>perdata
file would grow infinitely large. I don't see any option
in<BR>nagios.cfg that controls how much data stays in the perfdata.log
file<BR>(i.e. a retention interval for data contained
therein). Maybe I missed <BR>it somewhere.<BR><BR>So it's
starting to seem like I should trim this file somehow myself,<BR>but I'm not
sure how to go about that.<BR><BR>What's odd is that Nagios did this
processing for me fine up until <BR>yesterday. I have not added
any new hosts since yesterday. I can't<BR>imagine that this ran
anywhere near 5 seconds prior to yesterday but it<BR>still
worked. My config file is the same. However, I did
upgrade to <BR>Nagios 2.9 yesterday.</BLOCKQUOTE>
<DIV><BR><BR>I have the same, or similar report. I was (and currently
am) running Nagios 2.8, and the services-perf log file is created, added to,
and eventually sent to a "process the perf data" (nagiosgraph 0.7 with some
local add-ons). <BR>Then, I updated nagios to 2.9, and suddenly the
perf-log file just got bigger, and bigger, and bigger, and bigger... and no
services-performance processing was done, until the available diskspace (20MB
all in all - stored on a ramdisk) was full, Nagios 2.9 then kept on running,
but didn't have any meaningful informations available through the cgi's... (as
the status.dat file is also stored on that
ramdisk).<BR><BR>Cheers,<BR>--<BR>EinarI<BR><BR>ps: my current perf settings
(both for 2.8, which worked, and for 2.9, which didn't)
are:<BR><BR>perfdata_timeout=60<BR>process_performance_data=1<BR>host_perfdata_file=/usr/local/nagios/var/status.dir/host_perfdata.log<BR>service_perfdata_file=/usr/local/nagios/var/status.dir/service_perfdata.log
<BR>host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$<BR>service_perfdata_file_template=$LASTSERVICECHECK$||$HOSTNAME$||$SERVICEDESC$||$SERVICEOUTPUT$||$SERVICEPERFDATA$
<BR>host_perfdata_file_mode=a<BR>service_perfdata_file_mode=a<BR>host_perfdata_file_processing_interval=0<BR>service_perfdata_file_processing_interval=300<BR>service_perfdata_file_processing_command=process-service-perfdata
<BR><BR></DIV></DIV></BLOCKQUOTE></BODY></HTML>