Forgot to mention I am using pmacctd to read accounting data from several interfaces to be stored in a mysql db for further processing. I see this effect in pmacct v1.6.1 as well as in v1.7.0. Obviously the script started using sql_trigger_exec is running into some problems... ;-)
On 03/08/2018 03:04 AM, Johannes Maybaum wrote: > Hi, > > I am having a problem with the environment variables that is run after > the cache is pruged(sql_trigger_exec). As soon as I set > sql_startup_delay, some environment variables are not set anymore. > > sql_startup_delay not set: > > set | grep SQL -> > EFFECTIVE_SQL_TABLE=acct_20180308_02 > SQL_ACTIVE_WRITERS=0 > SQL_DB=pmacct > SQL_HISTORY_BASETIME=1520472300 > SQL_HISTORY_TIMESLOT=300 > SQL_MAX_WRITERS=10 > SQL_REFRESH_TIME=300 > SQL_TABLE=acct_%Y%m%d_%H > SQL_USER=pmacct > > > sql_startup_delay set: > > set | grep SQL -> > SQL_DB=pmacct > SQL_MAX_WRITERS=10 > SQL_REFRESH_TIME=300 > SQL_TABLE=acct_%Y%m%d_%H > SQL_USER=pmacct > > > Has anybody else seen this problem? > > > thanks, > > Johannes > > > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
