Accounting Relay to Fortigate - Issue with accounting file
aland at deployingradius.com
Tue Oct 17 21:49:43 CEST 2017
On Oct 17, 2017, at 3:31 PM, Hitesh Vinzoda via Freeradius-Users <freeradius-users at lists.freeradius.org> wrote:
> Detail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 1.086950 sec
> Waking up in 1.0 seconds.
> Polling for detail file /var/log/freeradius/radacct/detail
> Detail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 0.762697 sec
> Waking up in 0.7 seconds.
i.e. the file isn't there.
> root at user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrt
All of that is useless. The debug output shows you which file it's looking for. You're not verifying that the file exists.
All you need to check is:
$ ls -l /var/log/freeradius/radacct/detail
You'll also note that it's looking for one file. It's NOT doing a wildcard search.
i.e. You've configured it to look for ONE file "detail", which is located in the directory "/var/log/freeradius/radacct/"
While you're actually writing files to the directory "/var/log/freeradius/radacct/192.168.1.2", and writing files named like "auth-detail-20171017"
The disconnect between reader and writer should be obvious.
Again, read the examples and documentation. This is all documented.
- write detail files to ONE directory, not multiple sub-directories
- configure the detail file reader to read files (wildcard) from that directory.
- the wildcard needs to match the filenames it's writing...
On top of that, the detail file reader CANNOT read authentication packets. It can only read accounting packets. Again, this is documented.
The documentation really isn't that bad. It's certainly better to read the documentation than to ignore it entirely.
> FreeRADIUS Version 2.1.12
Ugh. Upgrade to 2.2.10 at least. It fixes lots of issues. Likely also issues with the detail files.
More information about the Freeradius-Users