This article reviews how to work with Okta RADIUS Agent logs. This includes the locations of the logs in Windows and Linux and how to modify the logging levels for the RADIUS Agent. This is essential knowledge when working with the Okta RADIUS Agent, as this allows Okta Administrators to perform health checks, log reviews for users, and general troubleshooting.

• Okta RADIUS Agent (All Versions) 
• Windows Server 
• Linux Server Operating System

For Windows

Okta RADIUS Agent log files can be found in the agent installation directory. Default location is C:\Program Files (x86)\Okta\Okta RADIUS Agent\current\logs

• okta_radius.log
  • This is the main log that admins will need to reference. This log contains authentication messages, errors, and the health status of the agent.
• okta_radius.access.log
  • This log only contains RADIUS access requests and responses. 
• commons-daemon.<year>-<month>-<day>
  • This log contains more details on the Okta RADIUS agent service/daemon. 

Change logging level

• Versions earlier than 2.15.0

1. Open log4j.properties, which can be found in the installation folder directory: C:\Program Files (x86)\Okta\Okta RADIUS Agent\current\user\config\radius\
2. Change the logging level. For example, increase the logging level by changing all three instances of info to debug. Which, when updated, should resemble:
   • log4j.logger.app=debug, app
   • log4j.logger.access=debug, access
   • log4j.rootLogger=debug, app, stdout

• Version 2.15.0 and later

1. Open log4j.xml, which can be found in the installation folder.
2. Change the logging level. For example, increase the logging level by changing all three instances of info to debug. Which, when updated, should resemble:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="error" name="OktaRadiusLogConfig">
     <Appenders> . . . </Appenders>
     <Loggers>
          <Logger name="app" level="debug" additivity="false">
               <AppenderRef ref="app"/>
     </Logger>
          <Logger name="access" level="debug" additivity="false">
               <AppenderRef ref="access"/>
               <AppenderRef ref="app"/>
     </Logger>
          <Root level="debug">
               <AppenderRef ref="STDOUT"/>
               <AppenderRef ref="app"/>
          </Root>
     </Loggers>
</Configuration>

For Linux

Okta RADIUS Agent log files can be found in the logs directory under the installation directory, whose default location is /opt/okta/ragent/logs

All the logs in Linux can be combined by using a command similar to:

• tar -zcvf logs.tar.gz /opt/okta/ragent/logs

NOTE: The above command as is will zip all logs in the /opt/okta/ragent/logs directory, and save them in a file called logs.tar.gz, in whatever directory the command was run from. For example, if this command was issued from /Users/Admin/tmp that is where the file will be saved. Specify an alternate directory is needed by adding the desired directory ahead of the file name, for example, "tar -zcvf /var/tmp/logs.tar.gz /opt/okta/ragent/logs". 
 

Change logging level

Set the logging level by modifying log4j.properties or log4j.xml, depending on the version of Okta RADIUS Agent.

• Versions earlier than 2.15.0

1. Open log4j.properties, which can be found in the installation folder /opt/okta/ragent/user/config/radius
2. Change the logging level. For example, increase the logging level by changing all three instances of info to debug. Which, when updated, should resemble:
   • log4j.logger.app=debug, app
   • log4j.logger.access=debug, access
   • log4j.rootLogger=debug, app, stdout

• Version 2.15.0 and later

1. Open log4j.xml, which can be found in the installation folder.
2. Change the logging level. For example, increase the logging level by changing all three instances of info to debug. Which, when updated, should resemble:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="error" name="OktaRadiusLogConfig">
     <Appenders> . . . </Appenders>
     <Loggers>
          <Logger name="app" level="debug" additivity="false">
               <AppenderRef ref="app"/>
          </Logger>
          <Logger name="access" level="debug" additivity="false">
               <AppenderRef ref="access"/>
               <AppenderRef ref="app"/>
          </Logger>
          <Root level="debug">
               <AppenderRef ref="STDOUT"/>
               <AppenderRef ref="app"/>
          </Root>
     </Loggers>
</Configuration>