radium fails (rc.50 from 2007-08-31)

[Carter Bullard]

Sorry for the delayed response.  Peter is correct on the radium issues.  Radium shares a lot of code from argus, so we're trying to figure out the memory issues, and I'll merge them into radium() when we're happy with it!!  Still a holiday here, but I'll start the radium work tonight, at least that is the plan.

So, it seems that we're pretty good, except for the "-R" option?  Have we got a 3.0.0 that has been running for days?

Hope everyone (US in particular) are having a great [ holi ] day !!!

Carter

Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax

-----Original Message-----
From: Peter Van Epp <vanepp at sfu.ca>

Date: Sun, 2 Sep 2007 11:12:00 
To:argus-info at lists.andrew.cmu.edu
Subject: Re: [ARGUS] radium fails (rc.50 from 2007-08-31)


On Sat, Sep 01, 2007 at 12:08:34PM +0200, Wolfgang Barth wrote:
> Hi,
> 
> if I start radium, I get an output like
> 
>    007-09-01 11:38:35starteddium[7261]: ???ii
> 
> Radium stops immediately. Same effect with an without .threads.
> 
> Wolfgang
> -- 
> <wob (at) swobspace de> * http://www.swobspace.de

	While Carter would be the final authority, I think radium may not yet
be updated. We just found a bug (or perhaps bugs) in memory allocation which
was causing the argus memory footprint to grow (thats what the various "small"
releases are about) and Carter just merged the changes back in on Friday (and
I think is now taking a well deserved rest :-)). 
	This is a copy of the latest argus (without threads) that has been 
running since Friday (even though traffic is well down):

ps auxwwww | grep argus
root     27229  3.8  9.1 364868 361352 ?       SL   Aug31 102:25 argus -P 560 -i eth0 -i eth1 -U 512 -m -F /scratch/argus.conf
vanepp   31939  0.0  0.0   3132   832 pts/0    S+   11:01   0:00 grep argus

previous versions would probably have been pegged at 4 gigs (all the memory
the machine has) by now.
	Hmmm, I just checked the threads version that I butchered to avoid a 
deadlock in shutdown and it is using an amazingly small amount of memory
(although on a different link so this may be a traffic type issue, I guess I 
should start a non thread version and see what happens :-)):

ps auxwwwww | grep argus
root     25148 12.2  0.4  19816 16112 ?        SL   Sep01 107:00 argus -P 560 -i eth2 -i eth3 -U 512 -m -D2 -F /spare/argus.conf
vanepp   26736  0.0  0.0   3132   832 pts/1    S+   11:03   0:00 grep argus

perhaps after poking a bit more at the threads version I'll move it to the
Intenet link (where it is it won't see most of the port scans that sweep
through which may be the difference). 

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada