Request logging mssing on Freeradius 2.1.12
What option(s) need enabling to log freeradius requests for a new service in /etc/freeradius/sites-enabled/servicename ? I have files, auth_log, redutmp and pre_proxy_log and post_proxy_log options enabled. No logs for the new service is being generated. Have I missed something? e.g. radius-servicename-2016-01-05.log in /var/log/freeradius folder. Log entries would look like: Mon Jan 4 00:10:04 2016 : Auth : Logon ok : [username@hud.ac.uk] (from client roaming.ja.net port 4 cli xx-xx-xx-xx-xx-xx-xx) Any ideas? Peter Hutchison MCP Senior Network Systems Specialist * 01484 473716 Infrastructure Team University of Huddersfield | Queensgate | Huddersfield | HD1 3DH University of Huddersfield inspiring tomorrow's professionals. [http://marketing.hud.ac.uk/_HOSTED/EmailSig2014/EmailSigFooter.jpg] This transmission is confidential and may be legally privileged. If you receive it in error, please notify us immediately by e-mail and remove it from your system. If the content of this e-mail does not relate to the business of the University of Huddersfield, then we do not endorse it and will accept no liability.
Hi,
What option(s) need enabling to log freeradius requests for a new service in /etc/freeradius/sites-enabled/servicename ? I have files, auth_log, redutmp and pre_proxy_log and post_proxy_log options enabled.
output of the debug log when these calls are made in the virtual server? - just output of radiusd -X when an authentication request passes through this virtual server (can be easily acheived with local eapol_test t localhost if localhost is defined to be virtual_server = servicename in the clients.conf file.... alan
On Jan 6, 2016, at 11:01 AM, Peter Hutchison <p.j.hutchison@hud.ac.uk> wrote:
What option(s) need enabling to log freeradius requests for a new service in /etc/freeradius/sites-enabled/servicename ?
The main server logs go to the standard log destination. This is the same for *all* virtual servers.
I have files, auth_log, redutmp and pre_proxy_log and post_proxy_log options enabled.
Those are modules. They don't affect the main server log.
No logs for the new service is being generated. Have I missed something?
e.g. radius-servicename-2016-01-05.log in /var/log/freeradius folder.
Where did you see the configuration option that would create files named like that? The server doesn't magically know what you want. It behaves as documented in the configuration files. Alan DeKok.
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Peter Hutchison