Accounting Relay to Fortigate - Issue with accounting file
Hi, I am setting up freeRADIUS to forward accounting requests to Fortigate. I have done the configuration but i am observing messages as below; Detail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 1.086950 secWaking up in 1.0 seconds.Polling for detail file /var/log/freeradius/radacct/detailDetail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 0.762697 secWaking up in 0.7 seconds.^Croot@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrttotal 4drwxr-xr-x 2 freerad freerad 4096 Oct 18 05:08 192.168.1.2root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrttotal 4drwxr-xr-x 2 freerad freerad 4096 Oct 18 05:08 192.168.1.2root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# cd 192.168.1.2/root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct/192.168.1.2# ls -lrttotal 8-rw------- 1 freerad freerad 141 Oct 17 18:14 auth-detail-20171017-rw------- 1 freerad freerad 1267 Oct 18 05:41 auth-detail-20171018root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct/192.168.1.2# FreeRADIUS Version 2.1.12 I have modified the modules/detail file to log all accounting packets to a single detail file as below Comment the line below by adding the # in front:# detailfile = ${radacctdir}/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d detailfile = ${radacctdir}/detail I can see that it is not creating detail file and above log messages keeps on repeating for polling the detail file. I have to prep this and the set up will be tested in next day. Any pointers are appreciated. Best Regards Hitesh Vinzoda
Cluttered Email - Resending again Hi, I am setting up freeRADIUS to forward accounting requests to Fortigate. I have done the configuration but i am observing messages as below; Detail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 1.086950 secWaking up in 1.0 seconds.Polling for detail file /var/log/freeradius/radacct/detailDetail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 0.762697 secWaking up in 0.7 seconds.^Croot@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrttotal 4drwxr-xr-x 2 freerad freerad 4096 Oct 18 05:08 192.168.1.2root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrttotal 4drwxr-xr-x 2 freerad freerad 4096 Oct 18 05:08 192.168.1.2root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# cd 192.168.1.2/root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct/192.168.1.2# ls -lrttotal 8-rw------- 1 freerad freerad 141 Oct 17 18:14 auth-detail-20171017-rw------- 1 freerad freerad 1267 Oct 18 05:41 auth-detail-20171018root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct/192.168.1.2# FreeRADIUS Version 2.1.12 I have modified the modules/detail file to log all accounting packets to a single detail file as below Comment the line below by adding the # in front:# detailfile = ${radacctdir}/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d detailfile = ${radacctdir}/detail I can see that it is not creating detail file and above log messages keeps on repeating for polling the detail file. I have to prep this and the set up will be tests in next day. Any pointers are appreciated. Best Regards Hitesh Vinzoda On Tuesday, 17 October 2017 9:52 PM, Hitesh Vinzoda via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote: Hi, I am setting up freeRADIUS to forward accounting requests to Fortigate. I have done the configuration but i am observing messages as below; Detail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 1.086950 secWaking up in 1.0 seconds.Polling for detail file /var/log/freeradius/radacct/detailDetail listener /var/log/freeradius/radacct/detail state unopened signalled 0 waiting 0.762697 secWaking up in 0.7 seconds.^Croot@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrttotal 4drwxr-xr-x 2 freerad freerad 4096 Oct 18 05:08 192.168.1.2root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# ls -lrttotal 4drwxr-xr-x 2 freerad freerad 4096 Oct 18 05:08 192.168.1.2root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct# cd 192.168.1.2/root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct/192.168.1.2# ls -lrttotal 8-rw------- 1 freerad freerad 141 Oct 17 18:14 auth-detail-20171017-rw------- 1 freerad freerad 1267 Oct 18 05:41 auth-detail-20171018root@user-To-be-filled-by-O-E-M:/var/log/freeradius/radacct/192.168.1.2# FreeRADIUS Version 2.1.12 I have modified the modules/detail file to log all accounting packets to a single detail file as below Comment the line below by adding the # in front:# detailfile = ${radacctdir}/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/detail-%Y%m%d detailfile = ${radacctdir}/detail I can see that it is not creating detail file and above log messages keeps on repeating for polling the detail file. I have to prep this and the set up will be tested in next day. Any pointers are appreciated. Best Regards Hitesh Vinzoda - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Oct 17, 2017, at 12:24 PM, Hitesh Vinzoda via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Cluttered Email - Resending again
Fix your mailer to post text, not HTML. That way it won't mangle the debug output. The text you posted is incomprehensible, so I won't bother trying to figure it out. Instead, I'll suggest that you follow the documentation. See the file sites-available/decoupled-accounting. That contains examples and documentation for how to configure detail file relaying. Or, see sites-available/copy-acct-to-home-server. That contains more examples and documentation. i.e. instead of giving a partial summary of what you did and asking "what went wrong?", you should follow the existing documentation and examples. If it doesn't work, you can then explain what you did, and what happened. And post messages which aren't mangled. That makes it much easier to help you. Alan DeKok.
participants (2)
-
Alan DeKok -
Hitesh Vinzoda