buffered-sql problem

Alan DeKok aland at deployingradius.com
Thu Jan 26 21:36:39 CET 2017

> On Jan 26, 2017, at 10:57 AM, Jouni Soini via Freeradius-Users <freeradius-users at lists.freeradius.org> wrote:
>> Again, are you clear that writing to detail-20170125 does *not* mean that the packet is immediately read into the detail.work file?
> yes I am clear about it. the problem is not latency. some packets are NEVER read (or written) from detail file.

  You can manually check the contents of the detail file, too.

>> I just don't see how the server "misses" packets from the detail file.
> I think the logs is clear enough. if you check them you can see that two accounting packets are received for users 'test1' and 'test2' at the same time.
> both are written to the detail file successfully (or at least the debugs says so)
> but while reading from this detail file only user 'test2' is saved into sql. there is no evidence of the user 'test1' in debugs and there is no row for it in the mysql table.

  The debug log shows (at one point), it's reading an entry from the "detail" file, but that the entry contains no attributes.

  Please download the the v3.0.x branch from https://github.com/FreeRADIUS/freeradius-server/

  I've put more debugging in so that it's clearer what happens.  If you run with "-Xx", you'll see exactly what's going on.  Including the detail module skipping empty packets, and not writing them to the detail file.

  Alan DeKok.

More information about the Freeradius-Users mailing list