Re: Leak in BOPM

On Sun, Aug 22, 2004 at 12:02:28PM -0700, Erik Fears wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > 	I'm running a central BOPM on a medium sized network (approx 1000 
> > users), and it is appear to be leaking memory (i've seen it running at 
> > a couple hundred MB). My current workaround is to /kill it every 60 
> > minutes, but that's hardly a fix.
> > 
> > 	I do run multiple DNSBLs (cbl.abuseat njabl, and opm.blitzed), and 
> > there's just one BOPM for the entire network (unreal3.2.1 with NICKIP, 
> > listening for far-connects). Any other information required, I will 
> > provide as soon as I can procure it.
> >
> 
> Are you sure this is a leak and not the scan queue filling up. There is no max limit on the scan queue, so if your scanner can't keep up then it will quickly fill up your memory.

Yes, tabris, please let us know these stats:

20:06:23 <@grifferz> MangoBOPM stat
20:06:23 <+MangoBOPM> Uptime: 4 weeks, 4 days, 12:32:44
20:06:23 <+MangoBOPM> DNSBL: 149 successful lookups from opm.blitzed.org
20:06:23 <+MangoBOPM> DNSBL: 71 reports sent
20:06:23 <+MangoBOPM> Found 37 (HTTP) open.
20:06:23 <+MangoBOPM> Found 27 (HTTPPOST) open.
20:06:23 <+MangoBOPM> Found 10 (SOCKS4) open.
20:06:23 <+MangoBOPM> Number of connects: 518654 (11.07/minute)
20:10:13 <@grifferz> MangoBOPM fdstat
20:10:13 <+MangoBOPM> Total open FD: 231/11095

Incidentally, using NJABL and CBL to protect an IRC network isn't
usually the best idea because they don't expire dynamic IPs very
often.  Other people who have tried this have found the need to
whitelist dynamic IPs by using a dynamic IP DNSBL as a DNS whitelist
(with the bopm DNS whitelists patch).

-- 
Andy Smith -- Occasional BOPM Developer And Support Monkey.  Please copy
all BOPM support queries to the BOPM list, _not_ just directly to me!
If I've helped you with BOPM then please check my wishlist!
http://www.amazon.co.uk/exec/obidos/registry/23IJ4U7N4J3X9

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBKPBLIJm2TL8VSQsRAnTTAJsHCihIj7zREWIV6eLCB5flSdUmBwCg/neT
GCSUUyq2vZL1IOWY/5/rWzA=
=icg8
-----END PGP SIGNATURE-----