RE: Memory leakage in snmptrapd

[Andy Ford]

Title: Memory leakage in snmptrapd

I have been running snmptrapd on a new box that receives a large number of traps. On instantiation, memory utilisation grew to 11MB and over the past 1.5 hours has increased to …   PID   USERNAME  SIZE   RSS STATE  PRI NICE    TIME  CPU PROCESS/NLWP       23588 root       95M   93M sleep   58    0   0:00.37 0.4% snmptrapd/1   … and growing …     Andy     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Andy Ford Sent: Tuesday, March 29, 2005 2:25 PM To: Net-Snmp (E-mail) Subject: Memory leakage in snmptrapd   I am running snmptrapd with the Perl Traphandler and seeing a large amount of memory usage. With no incoming traps, the memory utilisation of the snmptrapd process is stable at 11MB. As traps are processed, memory utilisation rises considerably. After just four days, the memory utilisation rose to over 500MB. I am running snmptrapd with the following options … snmptrapd -Le -c /etc/snmp/conf/snmptrapd.conf ===========  snmptrapd.conf ==================== engineBoots 1 oldEngineID 0x800007e5806ee2381a74676940 perl do "/etc/snmp/conf/mytrapd.v2.pl"; ============================================   ========== outline of mytrapd.v2.pl ======== sub global_hash {         - read in from mySQL DB } sub my_receiver {         - walk through VARBINDS         - look in global hash for interface with VARBIND info         - forward trap } NetSNMP::TrapReceiver::register("all", \&my_receiver) || warn "failed to register our perl trap handler\n"; print STDERR "Loaded the assure:control perl snmptrapd handler\n"; =========================================== Any ideas how I can start debugging this? I have seen this bug on 5.2.rc3 and also 5.3.dev Or is this already a known bug? I am currently compiling the latest cvs source. Thanks Andy This e-mail is private and may be confidential and is for the intended recipient only. If misdirected, please notify us by telephone and confirm that it has been deleted from your system and any copies destroyed. If you are not the intended recipient you are strictly prohibited from using, printing, copying, distributing or disseminating this e-mail or any information contained in it. We use reasonable endeavours to virus scan all e-mails leaving the Company but no warranty is given that this e-mail and any attachments are virus free. You should undertake your own virus checking. The right to monitor e-mail communications through our network is reserved by us.