Hi Jeff, If i'm getting this correctly, you see everything working except for the table creation error you get back.
If this is the case, i wouldn't say you are doing something wrong; pmacct tries to create the table every time the SQL cache scanner kicks in (sql_refresh_time interval); table name is a string, just it gets compiled in at runtime with dynamic tables. So, the failure to create the table derives from the fact the table name changes monthly in your case whereas data is inserted every 5 minutes. In summary: this is an harmless and not impacting issue. Why in the end this log message is labelled by pmacct as "ERROR"? pmacct just reports what the SQL library says - it has no clue of the severity of the content itself. This should really be an informational one. Cheers, Paolo On Tue, Dec 22, 2009 at 03:44:16AM -0800, Jeff Welling wrote: > Hi again, > So it seems I spoke too soon >< . It looks like its accumulating > information in the database in the right tables, but I don't know that > the information is correct or why its trying to create the table even > though it already exists..? > > I'm seeing this in my syslogs, one per table but here's the output from > just one; > > Dec 22 03:35:15 Gir pmacctd[10365]: ERROR ( incoming/mysql ): PRIMARY > 'mysql' backend trouble. > Dec 22 03:35:15 Gir pmacctd[10365]: ERROR ( incoming/mysql ): The SQL > server says: Table 'pmacct_v7_incoming_200912' already exists > > It shows up, I'm guessing, every time it tries to update the sql > database. Any idea what I did wrong? > Anything at all will be appreciated :) > Thanks, > Jeff. _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
