It doesn't actually appear to be clearing the statistics that cause
the memory to balloon.. I've started clearing both imt tables I have
setup every 2 minutes and:

# ps aux | grep -e 'USER\|nfacct'
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      1512  0.0  6.7 208380 129404 ?       Ss   08:10   0:02
nfacctd: Core Process [default]
root      1514  0.0  6.7 210916 130180 ?       S    08:10   0:02
nfacctd: Tee Plugin [fanout]
root      1527  0.0  6.8 211172 132232 ?       Ss   08:10   0:02
nfacctd: Core Process [default]
root      1529  0.0  7.4 221128 142364 ?       S    08:10   0:03
nfacctd: PostgreSQL Plugin [as]
root      1554  0.1 13.5 340128 261184 ?       Ss   08:10   0:05
nfacctd: Core Process [default]
root      1556  0.3 10.5 282840 203400 ?       S    08:10   0:12
nfacctd: IMT Plugin [full]
root      1557  0.2 27.5 608480 529064 ?       S    08:10   0:10
nfacctd: IMT Plugin [dst]
root      2740  0.0  0.0 103256   816 pts/0    R+   09:17   0:00 grep
-e USER\|nfacct

# ps aux | grep -e 'USER\|nfacct'
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      1512  0.0  6.7 208380 129384 ?       Ss   08:10   0:03
nfacctd: Core Process [default]
root      1514  0.0  6.7 210916 130160 ?       S    08:10   0:02
nfacctd: Tee Plugin [fanout]
root      1527  0.0  6.8 211172 132212 ?       Ss   08:10   0:04
nfacctd: Core Process [default]
root      1529  0.0  7.4 221260 142452 ?       S    08:10   0:04
nfacctd: PostgreSQL Plugin [as]
root      1554  0.1 13.5 340128 261164 ?       Ss   08:10   0:07
nfacctd: Core Process [default]
root      1556  0.3 10.9 288932 209520 ?       S    08:10   0:18
nfacctd: IMT Plugin [full]
root      1557  0.2 35.7 765692 686324 ?       S    08:10   0:14
nfacctd: IMT Plugin [dst]
root      3114  0.3  0.8 222716 16044 ?        S    09:40   0:00
nfacctd: pgsql Plugin -- DB Writer [as]
root      3160  0.0  0.0 103256   816 pts/0    R+   09:42   0:00 grep
-e USER\|nfacct


Is it possible my query is causing this?

This runs every 2 minutes:

pmacct -p /tmp/nfacctd-dst.pipe -l -O json -a -c "tag2" -M "2;3" -T
"packets,1000"

Configuration:

daemonize: true
nfacctd_port: 5680
plugins: memory[full], memory[dst]

aggregate[full]: tag, tag2, in_iface, out_iface, src_as, dst_as,
src_host, dst_host, proto, src_port, dst_port, tcpflags, ext_comm,
src_ext_comm
aggregate[dst]: tag, tag2, in_iface, dst_as, dst_host

imt_path[full]: /tmp/nfacctd-full.pipe
imt_path[dst]: /tmp/nfacctd-dst.pipe

pre_tag_map: /opt/pmacct/etc/pretag.map

! Not sure if needed
nfacctd_time_new: true
!
nfacctd_renormalize: true

plugin_pipe_size: 131072000
plugin_buffer_size: 6400
imt_buckets: 65537
imt_mem_pools_size: 1024000
imt_mem_pools_number: 160


On Mon, Jun 23, 2014 at 4:13 PM, Paolo Lucente <[email protected]> wrote:
> Hi,
>
> Can you then verify/confirm if it's the clearing of the statistics
> generating the issue? Determining how to reproduce the issue would
> help a lot to quickly solve the bug.
>
> Cheers,
> Paolo

_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Reply via email to