On Jan 04, "Todor Dragnev" wrote: > Hello list, > > I use flow-control from about 1 week. My OS is FreeBSD 6.0-RELEASE #0 > for AMD64. All works fine but yesterday I found this in dmesg: > > Jan 4 21:30:58 katana kernel: swap_pager_getswapspace(16): failed > Jan 4 21:30:58 katana kernel: swap_pager_getswapspace(12): failed > Jan 4 21:30:58 katana kernel: swap_pager_getswapspace(6): failed > > I have 512MB RAM and 2GB swapspace > On this PC I have squid-cache running, but when check which program use more > memory I found this: > > last pid: 49917; load averages: 0.94, 0.96, 0.79 up 1+05:58:05 21:58:29 > 187 processes: 2 running, 184 sleeping, 1 lock > CPU states: 5.5% user, 0.0% nice, 25.6% system, 21.3% interrupt, 47.6% > idle > Mem: 678M Active, 59M Inact, 166M Wired, 36M Cache, 111M Buf, 1636K Free > Swap: 2048M Total, 2048M Used, K Free, 100% Inuse, 4K In, 32K Out > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND > 518 root 1 96 0 2648M 104M select 0:33 0.00% flow-capture > 635 www 1 4 0 18504K 8908K kqread 0:22 0.00% thttpd > > > My starting line for flow-capture is: > > /usr/local/bin/flow-capture -p /var/run/flow-capture.pid -n 287 -N 0 -w > /var/log/netflows/ -S 5 /127.0.0.1/8899 > > Is that huge memory usage is memory leak or I do something wrong ?
There could be a 64-bit problem. Our setup has some 32-bit collectors that feed (among other things) a 64-bit cruncher. Building out the 64-bit cruncher lead me to finding some 32-bit vs. 64-bit bugs: http://mailman.splintered.net/pipermail/flow-tools/2004-December/002501.html But I haven't had to deal with flow-capture on 64-bit.... Is anybody out there running flow-capture on amd64/x86_64 or another 64 bit platform? I think the easiest way to start looking at this would be to run flow-capture under a memory debugger of some sort, like efence (Electric Fence Malloc Debugger). Mike _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
