Argus memory issues

[Carter Bullard]

Hey Peter,
The warning is not a problem as that call is not being exercised.

It looked to me that cpu utiliazation was way down, so not sure about the sluggishness?

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: Peter Van Epp <vanepp at sfu.ca>

Date: Wed, 22 Aug 2007 08:23:12 
To:argus-info at lists.andrew.cmu.edu
Subject: Re: [ARGUS] Argus memory issues


On Tue, Aug 21, 2007 at 11:14:37PM -0400, Carter Bullard wrote:
> Gentle People,
> I've just uploaded a small memory model for argus.  This is just the flow
> modeler engine with a small memory strategy.  Run this as you would
> run a normal argus, however it does not generate any output records,
> as it is just a flow model test harness.  Please give this a run to see how
> it does with memory utilization.  It should run fine, with significantly
> smaller foot print.
> 
> ftp://qosient.com/dev/argus-3.0/argus-3.0.0.smallmemory.rc.1.tar.gz
> 
> Thanks, and if this works, I'll convert all of argus-3.0.0 over to this 
> model.
> 
> Carter
> 
	
	Just compiled and ran it. Interactive response on the machine is 
horrible, but argus doesn't look to be doing anything deadly:

top - 08:17:32 up 3 days, 15:02,  1 user,  load average: 5.54, 3.37, 1.43
Tasks:  81 total,   1 running,  80 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.5%us,  0.7%sy,  0.0%ni, 17.5%id, 79.8%wa,  0.1%hi,  1.4%si,  0.0%st
Mem:   3936076k total,   103044k used,  3833032k free,     1564k buffers
Swap:  6202496k total,    18132k used,  6184364k free,     2476k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
  363 root      16   0 43608 4664  148 D    2  0.1   0:05.37 argus              
  354 root      10  -5     0    0    0 D    1  0.0 450:35.23 kswapd0            
  376 root      16   0  2720  352  224 R    0  0.0   0:00.10 top                
    1 root      18   0   808    4    4 S    0  0.0   0:23.71 init               
   12 root      10  -5     0    0    0 S    0  0.0   0:06.81 events/2          
	
	I'll reboot the machine in case there is something left over from  
a previous run and see what happens.
	The compile had a warning which may or may not be deadly:

gcc -O3 -m64 -fPIC -I.  -I./../include  -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STRING_H=1 -DHAVE_FCNTL_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_VFPRINTF=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRFTIME=1 -DHAVE_SETLINEBUF=1 -DHAVE_ALARM=1 -DHAVE_STRERROR=1 -DHAVE_STRTOF=1 -DHAVE_SYS_BITYPES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_VSNPRINTF=1 -DHAVE_SNPRINTF=1 -DHAVE_ETHER_HOSTTON=1 -DHAVE_NETINET_ETHER_H=1 -DNETINET_ETHER_H_DECLARES_ETHER_HOSTTON= -DHAVE_DECL_ETHER_HOSTTON=1 -D_FILE_OFFSET_BITS=64 -DHAVE_PCAP_LIST_DATALINKS=1 -DHAVE_PCAP_SET_DATALINK=1 -DHAVE_PCAP_DATALINK_NAME_TO_VAL=1 -DHAVE_PCAP_DATALINK_VAL_TO_DESCRIPTION=1 -DHAVE_PCAP_BREAKLOOP=1 -DHAVE_PCAP_DUMP_FTELL=1 -DHAVE_TCP_WRAPPER=1 -DSTDC_HEADERS=1  -DARGUS_SYSLOG=1 -c ArgusUtil.c
ArgusUtil.c: In function bArgusWriteSocketb:
ArgusUtil.c:1388: warning: passing argument 1 of bArgusDeleteObjectb from incompatible pointer type

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada