argusarchive.

[Carter Bullard]

Hmmm, a core dump in a system routine.  That's
not too good.  ArgusHandleClientData() is calling
ArgusWriteOutSocket(), which is the routine that
handles the output record queue for a particular
socket.  We call write() in this routine, when
we've got records that are queue'd on the socket,
so we're doing the right thing.

If the output file is gone, we will close it, and
reestablish the output file, swap the file
descriptors and be on our way, but there must be
something nefarious going on.  With the stack looking
corrupted, we may have lost a pointer or an index
number, so ....  let me take a look around.

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 588-9133
Fax   +1 212 588-9134
http://qosient.com


> -----Original Message-----
> From: Scott A. McIntyre [mailto:scott at xs4all.nl] 
> Sent: Thursday, November 01, 2001 9:02 AM
> To: Carter Bullard
> Cc: 'Argus Mailing List'
> Subject: Re: argusarchive.
> 
> 
> 
> 
> Well, got a core dump on this one, Carter:
> 
> #0  0x40102bc4 in write () from /lib/libc.so.6
> #1  0x08143f48 in ?? ()
> #2  0x0804f29e in ArgusHandleClientData (asock=0x8165078, 
> buf=0x81652dc "\001\004\001D", len=324, clientdata=0x8143e28) 
> at ./ArgusOutput.c:992 #3  0x08051e34 in ArgusReadSocket 
> (asock=0x8165078, ArgusThisHandler=0x804f1a8 
> <ArgusHandleClientData>, data=0x8143e28) at ./ArgusUtil.c:847 
> #4  0x0804ed27 in ArgusClientProcess (client=0x8143e28, 
> wfile=0x8143df0) at ./ArgusOutput.c:715 #5  0x0804e1bc in 
> ArgusInitOutputProcess () at ./ArgusOutput.c:294 #6  
> 0x0804e3df in ArgusOutputProcess () at ./ArgusOutput.c:410 #7 
>  0x0804dd07 in ArgusInitOutput () at ./ArgusOutput.c:128 #8  
> 0x0804a8d6 in main (argc=3, argv=0xbffffd34) at ./argus.c:379 
> #9  0x400586ef in __libc_start_main () from /lib/libc.so.6
> 
> 
> Scott
> 
> 
>