racluster crash

[carter at qosient.com]

Hey Dietmar,
As I suggested in the first email, this is a bug.  I recommended that you change the status timer to make it shorter than the idle timer to see if it didn't make a difference.   Its a bit frustrating for me to suggest a few things, and then you do the opposite, and then ask why it doesn't work.  If you want to send me the argus file that can create the problem, I can try to fix it for you.

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: Dietmar Goldbeck <goldbeck at e-trend.de>
Date: Sun, 13 Aug 2006 21:17:34 
To:carter at qosient.com
Cc:Argus <argus-info at lists.andrew.cmu.edu>
Subject: Re: [ARGUS] racluster crash

On Sun, Aug 13, 2006 at 06:12:13PM +0000, carter at qosient.com wrote:
> Yes, I think your missing a concept here.
> The status timer should be shorter than the idle timer.
> 
  Hi Carter,

I want to put aggregated flows in a database. If a flow is completely
inactive for more than 5 minutes, i want racluster to report it.  OTOH
i want to have long lived flows every 15minutes or so.

This is working fine with argus2/ragator. 
Is there any reason for argus3 not supporting this any longer? 

  Ciao
     Dietmar

-- 
 Alles Gute / best wishes  
     Dietmar Goldbeck         E-Mail: dietmar.goldbeck at schotterweg.de
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization?  Gandhi: I think it would be a good idea.