Memory leak in 2.0b4

[Andreas Ericsson]

misc at viceconsulting.co.nz wrote:
> Hi All,
> 
> Seems to be a memory leak in Nagios 2.0b4.
> 
> I've just upgraded my 6 Nagios servers to 2.0b4 (5 are distributed, one is
> a central Nagios server).  Was previously using 2.0b2.
> 
> All 6 of them are exhibiting identical problems.
> 
> I restart Nagios once every 24 hours.
> 
> With 2.0b4: Within 24 hours, memory went from 80% free to 40% free, and
> swap from 512mb free to around 200mb free.
> 
> With 2.0b2: Within 24 hours, Memory drops about 10%, swap is untouched.
> 
> Additionally 2 of my distributed servers crashed stone cold.
> 
> I know my servers are losing memory and swap because I graph these metrics
> (data polled every 5 minutes).
> 
> Is this a known issue?  Is there any info I can supply to help developers
> troubleshoot this?
> 

Architecture, OS flavour and version, compiler flavour and version, 
library versions, Nagios ./configure options (not paths) and such would 
be the absolute minimum, I suppose. There are historically problems with 
embedded perl, but according to Stanley Hopcroft those issues have 
mostly been resolved (although I believe poorly written perl-scripts can 
still make it leak quite a bit, especially with perl version prior 5.8).

For reference though; On Openwall GNU/*/Linux, without embedded perl, 
Nagios 2.04b leaks nothing at all.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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