Alan, Thanks for your help, the problem was that I had 3 months of detail data previously that did have the problem. I misunderstood that adding Alan Dekok's block would fix the problem for my older data. I'm going to work on making sure it doesn't happen again, but for the time being my server is happily plowing through the detail data.
Much thanks, GG On Tue, Nov 8, 2011 at 11:10 AM, Alan Buxey <[email protected]> wrote: > Hi, >> I tried adding the noop block to the detail reader and doesn't seem to >> make a difference. I'm still seeing this suspicious debug: > > Alan Dekok already told you this > > " Read raddb/sites-available/default. Look for "zero". " > > > the trouble is, if you HAVE a zero thats sneaked in, then theres be > troubles... > so you need a wrapper around your sql-buffer reader...eg > > sql { > invalid = 2 > fail = 2 > } > if (fail || noop || invalid) { > ok > } > > in the buffered-sql (that syntax might work, take care!) > > or, even better, make sure the situation where the detail file > gets such a thing doesnt happen in the first place eg, in your > virtual server accounting section... > > if (Acct-Session-Time != 0) { > detail > } > else { > ok > } > > alan > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
