Looks like a new bug in clients ...

[Peter Van Epp]

On Fri, Aug 17, 2007 at 05:10:08PM -0400, Carter Bullard wrote:
> Argus does a stat on the output filename, periodically, to see if it  
> needs
> to close the moved file's file descriptor, and create a new one.  I  
> think
> your internal clock is getting screwed and so 'check filename' timestamp
> isn't getting exceeded, so it doesn't check and keeps writing out to the
> old file.  The file is growing somewhere in the filesystem, but the  
> link to
> it is gone, so, ....
> 
> I'm working on the leak, but the timestamp issue is still something
> that could be  a mystery still.
> 
> Carter
> 

	argusarchive has run clean since the clients were recompiled with no
threads earlier this afternoon. I'll turn threads back on and restart it and
see what tommorrow brings :-).

-rw-r--r--   1 vanepp  vanepp   33981508 Aug 17 08:00 com_argus.2007.08.17.07.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp   36480665 Aug 17 08:22 com_argus.2007.08.17.08.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  197615602 Aug 17 10:00 com_argus.2007.08.17.09.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  174326612 Aug 17 10:20 com_argus.2007.08.17.10.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  309033292 Aug 17 11:43 com_argus.2007.08.17.11.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  161719258 Aug 17 13:00 com_argus.2007.08.17.12.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  476553769 Aug 17 14:00 com_argus.2007.08.17.13.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp   55332786 Aug 17 15:00 com_argus.2007.08.17.14.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  511566867 Aug 17 16:00 com_argus.2007.08.17.15.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp  394054147 Aug 17 17:00 com_argus.2007.08.17.16.00.02.0.gz
-rw-r--r--   1 vanepp  vanepp   48935926 Aug 17 18:00 com_argus.2007.08.17.17.00.00.0.gz
-rw-r--r--   1 vanepp  vanepp   24995067 Aug 17 19:00 com_argus.2007.08.17.18.00.00.0.gz

	I expect the last two are smallish because of this:

ps auxwwww | grep argus
root     14108  2.2 92.3 4673968 3634852 ?     DLsl 14:53   6:37 argus -dJR -P 560 -i eth0 -i eth1 -U 512 -m -F /scratch/argus.conf

I'll also kill and restart the argus to free some memory. The no threads change
was a good one, it appears there is a threads bug in ArgusModeler which may
break threading (because it won't mutex when it should):


*** argus/ArgusModeler.c.orig	2007-08-17 20:11:01.000000000 -0700
--- argus/ArgusModeler.c	2007-08-17 20:13:27.000000000 -0700
***************
*** 286,292 ****
     int done = 0;
  
     queue->turns++;
! #if !defined(ARGUS_THREADS)
     pthread_mutex_lock(&queue->lock);
  #endif
     while ((!done)) {
--- 286,292 ----
     int done = 0;
  
     queue->turns++;
! #if defined(ARGUS_THREADS)
     pthread_mutex_lock(&queue->lock);
  #endif
     while ((!done)) {
***************
*** 351,357 ****
        } else 
           done++;
     }
! #if !defined(ARGUS_THREADS)
     pthread_mutex_lock(&queue->lock);
  #endif
  
--- 351,357 ----
        } else 
           done++;
     }
! #if defined(ARGUS_THREADS)
     pthread_mutex_lock(&queue->lock);
  #endif