[Nagios-users] Nagios retention problem.

Andreas Ericsson ae at op5.se
Thu Nov 20 10:28:20 CET 2008


Markus.Almroth at teliasonera.com wrote:
> I move this thred to 'dev' instead. It seems to fit better there.
> 
> Problem solved. 
> 
> Nagios does'nt check the return value from the fclose() call when
> closing the tempfile used to write retention.dat. Before I upgraded to
> Nagios 3 I hade severe performance problems, so I moved all temp-files
> to ramdisks for higher performance which worked well. But when the
> number of services increased after upgrading the ramdisk was'nt big
> enough.
> 
> Since there were no log entry, and the ramdisks were only about 40-50%
> full, I did'nt think this was the problem - after all the ramdisk were
> only 100% full between the closing of the tempfile until Nagios changed
> the name of the tempfile to "retention.dat".
> 
> Anyway. I've rewritten the code a little so that Nagios checks the
> fclose() return value, and if there is a problem a log entry is written.
> Also Nagios does not change the name of the tempfile, so the old
> retention data is saved instead of the new corropt data.
> 
> Are you people interested in the patch?
> 

Yes.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/




More information about the Developers mailing list