Argus seems to stop writing data that ra can read.

[Scott A. McIntyre]

Hi Carter,

On 9 Apr 2014, at 4:23, Carter Bullard wrote:

> Hey Scott,
> OK, sorry for the delay on this….  So we have in the clients a 
> sanity check
> for bogus metric values as we’re reading argus records from the 
> input,
> and these records that argus-3.0.7.5 is generating that have errant
> packet and byte counts are causing us to reject the stream, and stop
> processing.

Thanks for the explanation; I can see why the clients act the way they 
do.


>
> I have a fix in the clients to realize the error, zero the errant
> data and mark the flow record cause as ARGUS_ERROR, which puts an
> “ERR” for the flow status.  I don’t like the reason we’re 
> doing this,
> argus generating bogus data, but it allows us to continue to process
> the stream without propagating the corrupted record.
>
> So if this is agreeable,  I’ll have this up on the server later 
> today.
>
> Sorry for the inconvenience.


That works for me - thanks very much for looking at it.  ERR I can live 
with just fine -- it was the missing the rest of the data that was 
recorded that was getting a bit frustrating.

Cheers,

Scott