memory error

Andreas Ericsson ae at op5.se
Mon Oct 4 16:40:53 CEST 2004


Martinus Nel wrote:
> Andreas,
> 
> I have seen the complaints to do with the embedded perl interpreter, but 
> I was under the impression that is only for Nagions 2.0 ?  On top of 
> that, like I said, this has been running without problems until 
> recently.  I have a feeling it is something I have switched on in the 
> configuration - the problem is, I don't know where to start searching 
> for a problem.
> 

It's not. Nagios won't eat memory unless like that unless something is 
wrong with the code, and the only thing I can think of is the embedded 
perl interpreter.

> As it is going now, I switched on 09:00 this morning, it was using 22%.  
> Now, it's 15:20 and I am on 33%.  Memory = 128 MB.  Current checks = 128 
> active, 10 passive over 33 hosts.
> 

Then perhaps some of your checks are hanging in non-interruptable mode? 
Are you using any plugins that you've rolled yourself?

> As for the PID ... it's just a number I typed in, I don't think you will 
> easily see 12345 as a PID/PPID.
> 

Unless you've fiddled with the kernel, pids are allocated in a round 
robin manner from 1 to 2^16 in which case 12345 is actually more likely 
to see than any higher number. Just a mathematical sidetrack.

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


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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





More information about the Users mailing list