segfault at 000000000311c000 rip 000000000040fb46 rsp 0000007fbffff830 error 4

[Gunnar Lindberg]

We switched from argus-3.0.0 to argus-3.0.1.beta.3 to avoid previous
segfault crashes. Now, it's hard to tell how many crashes we should
have had during this period had we not changed :-) but my gut feeling
is that things became slightly better.

An observation, slightly random and maybe not correlated with crash.
We now see a lot of

May  4 14:28:59 argc argus:   ArgusWarning: argus[24678]: 04 May 09 14:28:59.086200 ArgusNewFlow() flow key is not correct len equals zero
May  6 09:05:40 argc argus:   ArgusWarning: argus[24678]: 06 May 09 09:05:40.532448 ArgusNewFlow() flow key is not correct len equals zero
May  6 09:10:26 argc argus:   ArgusWarning: argus[24678]: 06 May 09 09:10:26.630149 ArgusNewFlow() flow key is not correct len equals zero

I note that the test and printout is in argus-3.0.0 too, but whether
it never happened before or it just didn't print before is beyond me.

	Gunnar Lindberg, wating for a crash dump :-)

>From argus-info-bounces+gunnar.lindberg=chalmers.se at lists.andrew.cmu.edu  Thu May  7 05:11:50 2009
>Date: Wed, 6 May 2009 20:11:01 -0700
>From: Peter Van Epp <vanepp at sfu.ca>
>To: argus-info at lists.andrew.cmu.edu
>Message-ID: <20090507031101.GA25745 at sfu.ca>
>References: <200905041331.n44DVJOH022155 at grunert.cdg.chalmers.se>
>	<200905061455.n46EtjJo012403 at grunert.cdg.chalmers.se>
>In-Reply-To: <200905061455.n46EtjJo012403 at grunert.cdg.chalmers.se>
>Subject: Re: [ARGUS] segfault at 000000000311c000 rip 000000000040fb46
>	rsp	0000007fbffff830 error 4

>On Wed, May 06, 2009 at 04:55:45PM +0200, Gunnar Lindberg wrote:
>> I'm afraid I have bad news.
>> 
>...
>	Well you don't appear to be alone for what thats worth :-). SFU (my
>former employer) is reporting segfaults after upgrading to the latest beta
>on a system with a sensor machine writing to a socket to another machine where
>ra is reading and storing to disk.
>...