Chris Wilson <[email protected]> wrote: > On Mon, 13 Apr 2009, Johannes Formann wrote:
Hi Chris, > >>>> Apr 13 17:20:01 server1 pmacctd[12419]: ERROR ( default/mysql ): > >>>> Duplicate entry > >>>> '0-00:1b:8f:61:55:c9-00:1c:c0:ab:8a:48-0-91.22.172.35-84.38.74.24' for > >>>> key 1 > >>> > >>> As this crash is so early, perhaps the thread isn't initialised properly? > >> > >> Well, the first update (into the complet empty table) was successfull, > >> and I think that has used the same kid of thread. > > > > I have now a guess whre the "duplicated" keys error come from: > > > > Assume the updates are done at :30 with sql_history_roundoff: 1h and > > sql_refresh_time: 3600 (1h) (so long for simplifikation) > > > > at 0:30 for each recorded flow a row is inserted with the timestamp 0:00 > > at 1:30 for log flow a row is inserted for 0:00 and 1:00 ... > > > > at least if I understood the dokumentation right, that makes the error, > > since to identical inserts should be done... > > My understanding is that with those settings, a row would be inserted just > after 0:00, with stamp_inserted = 0:00, and another one just after 1:00, > with stamp_inserted 1:00, so there should not be a conflict. It should ... > What makes you think that anything should happen at 0:30 or 1:30? Also, > the second insert should have stamp_inserted = 1:00 not 0:00, as far as I > know. ... but the last Updated timestamp shows something at least some secounds after that, so I guessed that might be the reason. Also fits to the observation, that the first insert into the empty database (although more than one row) does't report any errors. cheers, Johannes _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
