Additional rasqlinsert information

[Dave Edelman]

Carter,

Thanks, this is looking much better. I did have to drop the tables that had
the problem data and then everything started to work well.

--Dave

> -----Original Message-----
> From: Carter Bullard [mailto:carter at qosient.com]
> Sent: Tuesday, May 14, 2013 7:58 AM
> To: Dave Edelman; Jesse Bowling
> Cc: Argus
> Subject: Re: [ARGUS] Additional rasqlinsert information
> 
> Hey Dave,
> I believe that the fixes in argus-clients-3.0.7.9, which I'm putting up
right
> now,
> address this problem.  The issue is that I turned FLOW_CORRECTION on by
> default, and the aggregation routines, including rasqlinsert(), were doing
> flow
> direction correction, even when the aggregation model was not the default
> 5-tuple flow definition.  This would generate unexpected CIDR addresses,
> 0.0.0.0 entries, etc, when the proto field was a part of the model.
> 
> This release also fixes a number of issues with using floating point in
the
> filter, to support the new " abr " metrics.
> 
> Grab these clients, and please give it a try.
> 
>    http://qosient.com/argus/dev/argus-clients-3.0.7.9.tar.gz
> 
> Carter
> 
> 
> On May 14, 2013, at 7:08 AM, "Dave Edelman" <dedelman at iname.com>
> wrote:
> 
> > Carter,
> >
> > It looks like changing the CIDR notation parameter may be masking the
> > problem rather than fixing it. I found a bunch of MySQL error messages
in
> > the system message log so I restarted rasqlinsert with -D 3.
> >
> > For some reason redirection of STDERR prevented the program from
> running so
> > I just used cut and paste into a file.
> >
> >
> >
> > --Dave
> > <rasqlinsert.txt>