argus crash problem

[Lei Wei]

Hello Peter and Carter,

I've been trying to repeat the crash problem again recently. I ran 
argus with the debug option enabled from Sunday night until now. It 
never crashed. The only debug information it outputed was several lines 
when argus started to run and nothing more. The CPU usage right now is 
till about 99% but the output data file grows well and now is about 
144G already. I'm not sure why I can't repeat the crash again and there 
shouldn't be too much difference in the amount of traffic between this 
and last week. By the way, the link I'm monitoring is the campus border 
link to the ISP and the traffic load is more than 1G per second.  I 
wonder if there's any difference running in debug mode that could 
possibly play a role in it...  Anyway, I'll keep monitoring it and see 
what happens.

Lei



Quoting Peter Van Epp <vanepp at sfu.ca>:

> On Fri, Jan 25, 2008 at 12:10:36PM -0500, Lei Wei wrote:
>> Hey Carter and Peter,
>>
> <snip>
>>
>> I don't quite understand the following in Peter's email: "assuming
>> you have corelimit set to a non zero value gdb on the core will give
>> Carter good information.", could you give me some instrutions on how to
>> do it so that I can provide more helpful info?
>>
>> Again, thanks for all your help.
>>
>> Lei
>>
>
> 	Looks like corelimit is a solarisizm :-). Your shell may have a
> limit on core size (usually 0) so when a program cores the core isn't saved.
> I don't remember what FreeBSD does (it may be non zero by default in which
> case you will be fine) but on SUSE Linux you need to add
>
> ulimit -c unlimited
>
> to your bash profile because it defaults to 0 and you won't get a core.
> Mac OS10.4 does create cores by default and FreeBSD may too.
>
> Peter Van Epp / Operations and Technical Support
> Simon Fraser University, Burnaby, B.C. Canada
>