A nice detailed leak report.  Coders, can you please investigate?

        Thanks,

Mike

-----Original Message-----
From: Mark Brooks [mailto:[email protected]] 
Sent: Thursday, May 06, 2010 6:33 AM
To: Mike Ayers
Cc: [email protected]
Subject: Re: Memory Leaking with NetSNMP V5.5

Sorry I ment 225 bytes not 255


On 6 May 2010 13:59, Mark Brooks <[email protected]> wrote:


        Ok we have had a further revelation after much testing we were able to 
work out that there is one particular OID that is leaking 255 bytes of data 
each time you run snmpwalk the oid in particular is:
        
.1.3.6.1.2.1.88.1.4.3.1.3.6.95.115.110.109.112.100.95.109.116.101.84.114.105.103.103.101.114.82.105.115.105.110.103
        or its shorter name is
         
DISMAN-EVENT-MIB::mteEventNotificationObjects."_snmpd".'_mteTriggerRising' 
        the result of which is - 
        
DISMAN-EVENT-MIB::mteEventNotificationObjects."_snmpd".'_mteTriggerRising' = 
STRING: _triggerFire
        
        we can quite happily run snmpwalk above and below this OID and get 
consistent memory usage with no sign of a leak.
        
        What we cant quite work out is what function is failing to free the 
memory after its run. 
        
        any help on how to debug this further would be much appreciated. 
        
        Mark 
        

        On 5 May 2010 16:17, Mark Brooks <[email protected]> wrote:
        


                        Mark


                          
                        
                        
                        On 29 April 2010 00:59, Mike Ayers 
<[email protected]> wrote:
                        

                                > From: Mark Brooks 
[mailto:[email protected]]
                                > Sent: Wednesday, April 28, 2010 1:27 PM
                                

                                > We are running the 2.6.32.7 kernel with 
Centos 5.3 and using the LVS
                                > SNMP module 
http://kb.linuxvirtualserver.org/wiki/Net-SNMP-LVS-Module
                                > the memory usage increases each time we use 
snmpwalk to poll the system,
                                > and increases with each query until the box 
crashes. Has anyone else
                                > come across this issue. Or could kindly push 
us in the right direction
                                > as where to look next.
                                
                                
                                       Run snmpd without the dlmod for the LVS 
module and try the same test.  If there is no memory leak, then the problem is 
with with the LVS module, and you'll have to get support from them.  If not, 
let us know.
                                
                                
                                       HTH,
                                
                                Mike
                                
                                






------------------------------------------------------------------------------
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to