Re: Leak in BOPM

tabris <[email protected]>
Newsgroups gmane.network.irc.bopm
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 22 August 2004 3:13 pm, Andy Smith wrote:
> 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:
>
12:55:19 <+WCProxyBot> Uptime: 2 days, 23:42:32
12:55:19 <+WCProxyBot> DNSBL: 96 successful lookups from opm.blitzed.org
12:55:19 <+WCProxyBot> DNSBL: 4 reports sent
12:55:19 <+WCProxyBot> Found 1 (HTTP) open.
12:55:19 <+WCProxyBot> Found 3 (HTTPPOST) open.
12:55:19 <+WCProxyBot> Number of connects: 169902 (39.49/minute)
and the RSS is sitting at 21MB (none in swap). i haven't seen it go up 
for about a day... but that's still pretty big and one wonders why it 
doesn't free() any of the memory for the scan queue...

- --
tabris
- -
Probable-Possible, my black hen,
She lays eggs in the Relative When.
She doesn't lay eggs in the Positive Now
Because she's unable to postulate How.
		-- Frederick Winsor
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBLhZ71U5ZaPMbKQcRAuV1AJ9DqqHz6UPo1xEoWrOBMpmTinNShACfeBKa
0PVpGkcwh8lho9J9ZynSbAg=
=Sjmr
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.