Hi Fabien,
It smells like a crash. Please follow:
https://github.com/pmacct/pmacct/blob/master/QUICKSTART#L2031-L2060
We can then follow-up 1:1 with any output you may be able to gather.
Cheers,
Paolo
On Tue, Feb 13, 2018 at 10:21:54PM +0100, Fabien VINCENT wrote:
> Hi all,
>
> Trying to us
Hi Pavel,
Can we follow-up privately for some further investigation? I'd
start with a memory profile, ie. collect every few secs/minute
memory usage of every pmacct process, to determine how memory
utilization changes over time - and where that leads to. In
general i would say: if you keep the da
bject: Re: [pmacct-discussion] print plugin and src_as_path
>
> Hi Mario, All,
>
> A quick note to say this has now been implemented:
>
> http://www.mail-archive.com/pmacct-commits@pmacct.net/msg01006.html
>
> Cheers,
> Paolo
>
>
Hi Mario, All,
A quick note to say this has now been implemented:
http://www.mail-archive.com/pmacct-commits@pmacct.net/msg01006.html
Cheers,
Paolo
On Thu, Feb 20, 2014 at 04:27:31PM +, Paolo Lucente wrote:
> Hi Mario,
>
> Thanks for bringing this up, as you are scratching on a limbo
> s
Hi Mario,
Thanks for bringing this up, as you are scratching on a limbo
situation which is good to iron out. My take on src_as_path,
src_local_pref, src_std_comms, etc. is that they are all evil
since are based on reverse BGP lookups. Hence i've removed
mentions from official docs and stopped impl
