Hello Gregory, your 'combined' configuration looks fine. Being scrupolous enough, i've tested it. And it works. Which kind of issue are you experiencing (ie. it doesn't display any data, it returns an error, everything is ok but you are seeing wrong/not expected data, everything is ok but the memory table seems to remain void) ? Let me know !
While waiting to hear from you, just two quick hints: - because of buffering - 2048 bytes from your configuration -, attaching pmacctd to a very-low traffic interface (ie. the only traffic listened by pmacctd is generated by yourself via a ping) can result in a void memory table until sufficient data are collected into the buffer. - are you remembering to supply the trailing '-p' to pmacct client ? For example - referring to your configuration -: pmacct -s -p /tmp/port_in.pipe pmacct -s -p /tmp/port_out.pipe I've saved the following lines into a file 'gregory.conf': > ! pmacct: In + Out > !daemonize: true > ! > interface: eth0 > ! > aggregate[in]: src_port > aggregate[out]: dst_port > plugins: memory[in], memory[out] > plugin_buffer_size[in]: 2048 > plugin_buffer_size[out]: 2048 > plugin_pipe_size[in]: 2048000 > plugin_pipe_size[out]: 2048000 > imt_path[in]: /tmp/port_in.pipe > imt_path[out]: /tmp/port_out.pipe > pidfile: /var/run/pmacctd_porttraf.pid i've rewritten the last line: "pidfile: /tmp/pmacctd_porttraf.pid" to match my system. I've fired 'pmacctd -f gregory.conf'. And then i've been able to read data with the pmacct client: pmacct -s -p /tmp/port_in.pipe pmacct -s -p /tmp/port_out.pipe Cheers, Paolo
