Hi Christian, I'm not sure how a change to the frontend can influence that way the backend. Two things to check: 'sql_history' is in use (as it generates the timestamp used at a later stage to work out the name of the dynamic table) and sql_table_schema file is readable.
Moreover, something related to dynamic SQL tables was fixed in just released 0.12.0rc1 version - and it's been in the CVS for quite a while. If you are not using either of these versions, another chance is to upgrade and see if this solves the issue. Otherwise we may have to dig deeper into it. Let me know. Cheers, Paolo On Mon, Aug 03, 2009 at 11:51:13AM +0200, christian wrote: > > hello world, > > since i have changed my 'frontend' to slack64 on a e5520, pmacctd doesn't > create weekly tables any more on my 'backend' server. > > it seems it doesn't even try.. > > when i create them manually, they get populated. > > a typical sunday/monday switch looks like this: > > __cut__ > Aug 3 00:00:04 ns pmacctd[7614]: ERROR ( default/mysql ): PRIMARY 'mysql' > backend trouble. > Aug 3 00:00:04 ns pmacctd[7614]: ERROR ( default/mysql ): The SQL server > says: Table 'pmacct.acct_ppp0_200931' doesn't exist > __cut__ > > no other error messages. > > i definitely *can* create these tables when doing `mysql` on the same > machine as user pmacct (just tested)... > > what am i possibly doing wrong, and how could i find or fix it? > > > thanks for reading! > > regards, > christian _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
