Table of Contents
Debugging for FreeRADIUS
Enabling debug mode requires restarting RADIUS.
Enabling debug mode
- Enable the FreeRADIUS control-socket:
ln -s /etc/raddb/sites-available/control-socket /etc/raddb/sites-enabled/
This module allows the RAdmin administration tool to work.
- Configure RAdmin write permissions in
/etc/raddb/sites-available/control-socket:mode = rw
Possible values:
- ro = read-only access (default)
- rw = read and write access
- Verify that the module is added to the main config:
ls -la /etc/raddb/sites-enabled/
- Restart radiusd:
systemctl restart radiusd
Restarting does not terminate subscriber sessions (neither auth nor acct), but during the restart Proxy packet loss may occur from SSG to RADIUS, for example several Interim-Update or Access-Request packets. They will be resent after the restart.
Working with RAdmin
- Open RAdmin:
radmin
- Logging is written to the directory defined in
/etc/raddb/radiusd.conf, by default it isradius.log - Enable debug mode
debug level 4
The logging verbosity can be set from 0 (disable logging) to 4 (debug mode, similar to
radiusd -X).
Important! Even with logging level 1, debug mode generates a large number of logs, so it is not recommended to keep logging enabled for a long time to avoid filling system storage.
- Select a file for writing logs:
debug file [filename]
Commands must be entered sequentially; they cannot be used simultaneously as in:
debug level 3 debug file [filename]
- If an error occurs after restarting
radiusdor when attempting to connect to RAdmin — check whether the socket/var/run/radiusd/radiusd.sockexists and what permissions are assigned to it.
If there are no access permissions (default is radiusd) — change thegidanduidparameters to "root" in/etc/raddb/sites-available/control-socket.uid— the user name allowed to connect to the control socket.gid— the group name allowed to connect to the control socket.
Was this information helpful?