Set up logs for the SecureAuth IdP RADIUS server for several reasons, including the following examples:
- Discover why an end user is unable to log into the VPN server.
- View metrics about how long it takes for connections to occur between the VPN server and end-user login.
End users are experiencing problems logging into the VPN server.
Discover why the SecureAuth RADIUS server is not responding or is responding slowly by enabling the logs.
Set up logs for the SecureAuth IdP RADIUS server by completing the following:
- Download the following log configuration file, and place it in a temporary folder on the SecureAuth RADIUS server.
- Rename C:\idpRADIUS\bin\conf\log4j2.xml so you can use it to disable logging when you finish debugging.
The paths you use might be different, depending on your RADIUS server version or the destination folder selected when you installed the RADIUS server. The following are examples of default paths:
- C:\Program Files (x86)\SecureAuth Corporation\SecureAuth IdP RADIUS Agent\bin\conf\log4j2.xml
- C:\Program Files\SecureAuth Corporation\SecureAuth IdP RADIUS Agent\bin\conf\log4j2.xml
- Place the downloaded log4j2.xml file in the *\bin\conf folder, which is the same folder used in step 2.
- Run the services.msc application, then restart the SecureAuth RADIUS service.
- Replicate the issue you have encountered.
- Find log files stored in *\bin\Logs\saRadiusServer.log.
- Receive assistance with resolving the issue by forwarding log files to the SecureAuth Support team when you create a support ticket.
- Restore the original log4j2.xml after debugging is completed.
Trace level logging uses a substantial amount of disk space and can create disk space issues over time.