# Enable SecureAuth RADIUS server logs

Administrators can enable SecureAuth RADIUS Server to save server logs for troubleshooting purposes. Some use cases for setting up server logs include:

• 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.

Follow these steps to enable server logs:

### Note

The directory paths you use depends on your SecureAuth RADIUS server version or the destination folder selected when you installed the SecureAuth RADIUS Server. The following are examples of default paths:

• C:\idpRADIUS\bin\conf\

• C:\Program Files (x86)\SecureAuth Corporation\SecureAuth IdP RADIUS Agent\bin\conf\

• C:\Program Files\SecureAuth Corporation\SecureAuth IdP RADIUS Agent\bin\conf\

1. Go to the directory where you have installed SecureAuth RADIUS Server.

2. Rename the log4j2.xml file in the *\conf folder to save it as a backup.

For example, rename it to log4j2backup.xml.

Alternatively, you can move the file to a new location.

3. Download the debugging SecureAuth RADIUS log4j2.xml log configuration file and save it in the in the *\bin\conf folder.

4. Open the Windows Task Manager and select the Services tab.

5. Run the services.msc application, then restart the SecureAuth RADIUS service.

6. Replicate the issue you encountered with SecureAuth RADIUS.

For example, if you are attempting to understand why an end user is unable to log into the VPN server, have the end user attempt to log in again.

7. Find log files stored in *\bin\Logs\saRadiusServer.log.

8. Receive assistance with resolving the issue by creating a support ticket and forwarding your log files to SecureAuth Support.

9. After debugging is complete, delete the debugging log4j2.xml file downloaded in Step 3 and restore the original log4j2.xml.

For example, rename log4j2backup.xml back to log4j2.xml.

### Caution

Trace level logging uses a substantial amount of disk space and can create disk space issues over time.