<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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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>