Paolo,
Yes, it is working, thanks.
And I analyzed some flows related to expiring orphan, and most of them
seems to be related to torrents, but I'm not sure.
After some time (2hours+) running pmacctd and nfacctd, I start
receiving a lot of
WARN: expecting flow '817086981' but received
Hi,
To wrap-up this thread - unless new details emerge:
On Tue, May 04, 2010 at 11:53:59AM +, Paolo Lucente wrote:
* one capturing some torrent traffic, so that i can replay it in a
testbed and see if i can reproduce and validate the behaviour.
Orphan fragments are really there.
Paolo,
I think the problem is in the SELECT.
SELECT returns PGRES_TUPLES_OK, which means, a PGRES_COMMAND_OK plus
result data.
I dont know another way to circumvent this without recompiling pmacct.
The change here is in line
746 if (PQresultStatus(PGret) != PGRES_COMMAND_OK) {
I just want
Hi Sergio,
Good point.
I've just marked PGRES_TUPLES_OK as valid return code within the
PG_create_dyn_table() function - and committed the change to the
CVS. Can you please confirm it works OK for you?
Cheers,
Paolo
On Mon, May 03, 2010 at 10:10:18AM -0300, Sergio Charpinel Jr. wrote:
Hi Sergio,
On Thu, Apr 29, 2010 at 11:23:35AM -0300, Sergio Charpinel Jr. wrote:
Does anyone know what this mean? I getting a lot of them in pmacctd.log
Expiring orphan fragment: ip_src=210.197.202.84 ip_dst=200.137.66.1 proto=17
id=8885
It means some IP fragments have been staying too long
I did the function. But I'm calling it with select
function_name(table_name) , and I getting errors in nfacctd.log:
ERROR ( default/pgsql ):
ERROR ( default/pgsql ):
Here is the function, if anyone wanna do something similar:
CREATE OR REPLACE FUNCTION cria_tab_pmacct(text)
RETURNS void AS $$
Hi,
Does anyone know what this mean? I getting a lot of them in pmacctd.log
Expiring orphan fragment: ip_src=210.197.202.84 ip_dst=200.137.66.1 proto=17
id=8885
Regarding the topic, when using dynamic tables with postgreSQL, How can I
verify if a table already exists before trying to create
