argus crash problem

[Lei Wei]

Hey Carter and Peter,

I apologize to not respond timely. The monitor machine I'm now using is 
a shared machine which has several users, so I always have to reserve 
it before getting a chance to use...  sorry about that.

I did check the /var/log/message, but I didn't find any useful output 
there. Argus could generate the record with no problem except it 
stopped at some point. I'll do your suggestions this afternoon. And 
since it usually takes more than 10 hours to repeat the crash, it might 
be later that I can get back to you.

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




Quoting Carter Bullard <carter at qosient.com>:

> Hey Lei,
> I must ask you to be more considerate of the list by providing feedback
> when someone does something for you, and by providing more detail
> other than "i have a crashing issue and I don't know what to do".
>
> Did the changes we make for you work at any level?
> Did argus generate records?
> Do you know how to run a debugger?
>
> Carter
>
> On Jan 24, 2008, at 1:56 PM, Lei Wei wrote:
>
>> Hello,
>>
>> I've met with some crashing issue when using argus to continously  
>> monitoring the dag interface. The version I'm now using is argus-3.  
>> It happened several times that after about 10 hours of monitoring,  
>> the argus process died by itself for some reason. The system is a  
>> Freebsd5.4 on a 2G memory and 2G CPU machine. I periodically checked 
>>  the memory usage of argus process when it's running, it seemed that 
>>  most of the time it consumed under 400Mb of memory and above 50% 
>> CPU  usage, and sometime even 99% of CPU usage. Could anyone give me 
>> some  hint on what could possibly cause argus to crash and what I 
>> could do  to prevent it?
>>
>> Thanks.
>> Lei
>>
>