On Jan 25, 2017, at 3:28 PM, Jouni Soini <soini.jouni@yahoo.com> wrote:
Again, the *full* debug log is useful here. If you say that the debug log does (or doesn't) show something, then post the log. Not *part* of the log which doesn't show what you said.
The server doesn't randomly skip entries in the detail file. If something is skipped, there's a reason. And the reason is in the > debug log.
I don't see anything in logs. anyway I am sending the full logs starting from accounting request for 'test1' as you can see there is no sql section for this user
The users are being written to TWO detail files: /var/log/freeradius/radacct/detail-20170125 and /var/log/freeradius/radacct/debug/82.21.11.91/detail-20170125 You've configured the server to read from a detail file /var/log/freeradius/radacct/detail-*. which is fine. But, reading the REST of the debug output will help. The server prints out which detail files it's reading, and what it's doing. I don't see any of that in this tiny piece of the debug log. So what's happening is this: - server is reading from detail.work - packets are being written to detail-20170125 - you're wondering why packets written to detail-20170125 aren't in detail.work Well... keep reading the debug output. At some point, it will print this when it starts reading a detail file: DEBUG("detail (%s): Renaming %s -> %s", data->name, filename, data->filename_work); and it will print this when it's done reading the detail file: DEBUG("detail (%s): Unlinking %s", data->name, data->filename_work); Look for those. I've pushed some fixes to the v3.0.x branch which will make this a bit clearer. Alan DeKok.