Random crashing with rc.40 on Linux
carter at qosient.com
carter at qosient.com
Thu Mar 8 09:08:14 EST 2007
Hey Scott,
Put the break in the routine ArgusLog.
gbd> b ArgusLog
gdb> run -F conf.file
Abd see what happens!! I'll take a look at the packet dump, but if you can try running argus against it, that may help!!
argus -r dump.file -w out.file
Just to see if it complains in the same way.
Carter
Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax
-----Original Message-----
From: "Scott A. McIntyre" <scott at xs4all.net>
Date: Thu, 08 Mar 2007 13:42:36
To:carter at qosient.com
Cc:Argus <argus-info at lists.andrew.cmu.edu>
Subject: Re: [ARGUS] Random crashing with rc.40 on Linux
Hey Carter,
>
> But as Peter suggested, running under gdb() and doing a back trace and looking at the packet that is the culprit, or inserting some code to dump core in the ArgusLog() routine is the easiest way to get a view into what is going on!!!
>
Sadly:
Starting program: /usr/local/argus3/sbin/argus -F
/usr/local/argus3/argus.conf
argus[26162]: 08 Mar 07 07:39:16.113912 started
argus[26162]: 08 Mar 07 07:39:16.114317 ArgusGetInterfaceStatus:
interface eth1 is up
argus[26162]: 08 Mar 07 08:18:55.517916 ArgusAddToQueue (0x815106c,
0xa0c1520) obj in queue 0x815106c
Program exited normally.
(gdb) bt
No stack.
(gdb)
I'll run a tcpdump as well though, will see if that gets it sorted. It
tends to die pretty quickly...
Regards,
Scott
More information about the argus
mailing list