Hi Paolo,

I was in the process of writing an email to ask why our nfacctd daemon was
not creating dynamic tables when I noticed something a little strange.

It would appear that the dynamic tables are only created when the current
time coincides with the sql_history_roundoff value. Our nfacctd is
configured with:

sql_history: 1h
sql_history_roundoff: h

This was observed with both 0.11.6 and 0.12.0rc3.

If the end user attempts to start *acctd with an empty database, the system
will complain that the tables do not exist:

Oct 31 00:54:53 usage nfacctd[23604]: INFO ( default/core ): Start logging
...
Oct 31 00:54:53 usage nfacctd[23604]: INFO ( default/core ): waiting for
NetFlow data on :::2100
Oct 31 00:57:41 usage nfacctd[23664]: ERROR ( outbound/pgsql ): PRIMARY
'pgsql' backend trouble.
Oct 31 00:57:41 usage nfacctd[23664]: ERROR ( outbound/pgsql ): The SQL
server says: ERROR:  relation "ro_200910" does not exist
Oct 31 00:57:41 usage nfacctd[23664]: ALERT ( outbound/pgsql ): recovery for
PgSQL operation failed.
Oct 31 00:57:41 usage nfacctd[23663]: ERROR ( inbound/pgsql ): PRIMARY
'pgsql' backend trouble.
Oct 31 00:57:41 usage nfacctd[23663]: ERROR ( inbound/pgsql ): The SQL
server says: ERROR:  relation "ri_200910" does not exist
Oct 31 00:57:41 usage nfacctd[23663]: ALERT ( inbound/pgsql ): recovery for
PgSQL operation failed.

>From PostgreSQL's log:

<traffictest%localhost%2009-10-31 00:57:41 EST>LOG:  statement: BEGIN; LOCK
ro_200910 IN ROW EXCLUSIVE MODE;
<traffictest%localhost%2009-10-31 00:57:41 EST>ERROR:  relation "ro_200910"
does not exist
<traffictest%localhost%2009-10-31 00:57:41 EST>STATEMENT:  BEGIN; LOCK
ro_200910 IN ROW EXCLUSIVE MODE;
<traffictest%localhost%2009-10-31 00:57:41 EST>LOG:  statement: BEGIN; LOCK
ri_200910 IN ROW EXCLUSIVE MODE;
<traffictest%localhost%2009-10-31 00:57:41 EST>ERROR:  relation "ri_200910"
does not exist
<traffictest%localhost%2009-10-31 00:57:41 EST>STATEMENT:  BEGIN; LOCK
ri_200910 IN ROW EXCLUSIVE MODE;
<traffictest%localhost%2009-10-31 00:57:41 EST>LOG:  unexpected EOF on
client connection
<traffictest%localhost%2009-10-31 00:57:41 EST>LOG:  unexpected EOF on
client connection

This all magically corrected itself as the clock hit 1AM. Perhaps it would
be a little more user friendly if the daemon attempted to create the table
straight away?
  
Regards,

David Hill
eStation Australia Pty Ltd
http://www.estation.com.au
---------------------------
Telephone  03 9725 8759
Facsimile  03 9725 6388

Address    Suite 4, 6 Thomas Brew Lane, Croydon, Victoria, 3136
Postal     PO Box 4084, Croydon Hills, Victoria, 3136

eStation Australia Pty Ltd
ACN        097 354 348
ABN        51 097 354 348
---------------------------


_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists

Reply via email to