Hi Brent,
Good to see progress.
The entries stay forever, there is not an aging-out mechanism. Reason
being you are supposed to do it yourself, at regular intervals, to build
a time reference for the counters.
For example a simplistic scenario is a cronjob entry, set up every 5
minutes, that
Paolo -
when I try to run pmacct -s -e I get a disconnected memory pipe and
have to restart the daemon to get it back.
bash-3.2$ pmacct -s -e -p /tmp/sfacctd_prefixes.pipe
...snp...
For a total of: 1391302 entries :)
bash-3.2$ pmacct -s -e -p /tmp/sfacctd_prefixes.pipe
Hi Brent,
Thanks very much for the feedback. I've just corrected the issue
and will commit it to the CVS shortly later today.
Cheers,
Paolo
On Thu, Mar 11, 2010 at 09:26:57AM -0800, Brent Van Dussen wrote:
Paolo -
Just tried to build the latest CVS version and am getting compile errors
Thanks Paololooks like our dst_mask is showing up now in the
memory tables! (sql way too slow and IO constrained)
I wanted to ask about these messages we're getting in the logs now
that we're using mem tables:
WARN ( prefixes/memory ): Unable to allocate more memory pools, clear
Hi Brent,
On Thu, Mar 11, 2010 at 10:01:26AM -0800, Brent Van Dussen wrote:
I wanted to ask about these messages we're getting in the logs now that
we're using mem tables:
WARN ( prefixes/memory ): Unable to allocate more memory pools, clear
stats manually!
WARN ( as_path/memory ):
Good news, no longer getting the errors and my system hasn't fallen on
its face yet.
Also have 2-3x more entries in the memory tables so that's excellent
as well.
My next question is regarding aging of entries in the memory table,
how is this done? At first I checked one of the tables
Hi Brent,
On Fri, Feb 19, 2010 at 10:51:21AM -0800, Brent Van Dussen wrote:
I was curious if there was a way to have sfacctd only insert into the
database if a certain number of packets and/or bytes threshold is
reached.
It seems you are looking for the sql_preprocess directive - and
