Hi Morgan, The memory plugin comes with some default settings to avoid taking over all system memory. Chance might be some aggregates might not fit in the default table. You can verify if this is the case by either enabling debug (very verbose!) or adding a "imt_mem_pools_number: 0" line to your configuration. Then you can take it from there: read documentation to fine tune it and adapt to your scenario. Let me know if this helps.
Cheers, Paolo On Thu, Jun 17, 2010 at 02:48:03PM +0200, Morgan Sellier wrote: > Hi, > > I have a problem with pmacct, sometimes I don't have the traffic in two > directions. > > For example : > > [r...@ugestiontst ~]# pmacct -s -p /tmp/global.pipe | grep 10.224.12. | grep > 3389 | grep -v 128.1.1.10 | sort > SRC_IP DST_IP SRCP DSTP PACKETS BYTES > 10.224.12.20 10.225.12.32 3389 1767 3 177 > 10.224.12.20 10.225.12.41 3389 1522 932 398831 > 10.224.12.20 128.1.1.62 3389 20037 272 130991 > 10.225.12.32 10.224.12.20 1767 3389 4 251 > 128.1.1.62 10.224.12.20 20037 3389 200 43842 > 128.1.1.62 10.224.12.20 40432 3389 73 36059 > > > Here for the host 10.225.12.41 we have the traffic just in one direction ! > > My pmacctd.conf is like it : > > ! > daemonize: true > interface: eth1 > promisc: true > aggregate: src_host,src_port,dst_host,dst_port > plugins: memory[traffic] > imt_path[traffic]: /tmp/global.pipe > > Help me please ! _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
