Hi Paolo,
many thanks for the fast answer
2006/9/5, Paolo Lucente <[EMAIL PROTECTED]>:
With release rc1 the problem it remains.
Now I have launch the rc3 and I try
About the negative packets/bytes increments, they are ok because
OK, I will try also without classification.
still thanks for the answer
Corrado
Hi Conraid,
On Tue, Sep 05, 2006 at 10:12:00AM +0200, Conraid Lista wrote:
> the strange aspect is that packets and bytes short themself
> (packets=packets-2 and bytes=bytes-88)
> (in ita: la dimensione decrementa invece di incrementarsi)
>
> ...
>
> Then, in database (Mysql) I found a record with an overflow value in
> acct_totin and acct_totout table. In 1 minute this
> record reaches the biggest possible dimension. In a log file I didn't found
> the relative line of this error.
The very short answer is: please upgrade to the latest version as
some overflow problems (strictly connected to the classification)
got solved recently with the 0.11.x releases. If you manage to do
the upgrade, let me know whether you see them disappearing.
With release rc1 the problem it remains.
Now I have launch the rc3 and I try
About the negative packets/bytes increments, they are ok because
you have enabled classification and sql_aggressive_classification.
What this directive does is explained in CONFIG-KEYS document. The
movement of unknown packets into a well-known class generates such
negative (usually small) amounts. Then, ideally it would be ok to
find some records of 'unknown' class with 0 packets/bytes/flows.
Ideally, because for this to happen we should have the 'perfect'
classification mechanism.
OK, I will try also without classification.
Corrado
_______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
