To debug and troubleshoot problems, you can view the Workspace ONE Access connector log files, which are stored on the connector server. The Directory Sync, User Auth, and Kerberos Auth services each have their own log files.
|Type of Log File||Log File Location||Description|
|Installation log file||ConnectorInstallerFolder\Workspace_ONE_Access_Connector_Installer.log||Messages related to installation|
|User Auth service log files||INSTALL_DIR\Workspace ONE Access\User Auth Service\logs\eas-service.log||Messages related to authentication|
|Directory Sync service log files||INSTALL_DIR\Workspace ONE Access\Directory Sync Service\logs\eds-service.log||Messages related to directory sync|
|Kerberos Auth service log files||INSTALL_DIR\Workspace ONE Access\Kerberos Auth Service\logs\eks-service.log||Messages related to Kerberos authentication|
|Enterprise services vertex logs||INSTALL_DIR/User Auth Service/logs/eas-vertx-access.log
INSTALL_DIR/Directory Sync Service/logs/eds-vertx-access.log
INSTALL_DIR/Kerberos Auth Service/logs/eks-vertx-access.log
|Information about the API requests on the enterprise services.|
|Enterprise services process standard output logs||INSTALL_DIR/User Auth Service/logs/UserAuthService.out.log
INSTALL_DIR/Directory Sync Service/logs/DirectorySyncService.out.log
INSTALL_DIR/Kerberos Auth Service/logs/KerberosAuthService.out.log
|Information about the process running the enterprise services.|
|Enterprise services process standard error logs||INSTALL_DIR/User Auth Service/logs/UserAuthService.err.log
INSTALL_DIR/Directory Sync Service/logs/DirectorySyncService.err.log
INSTALL_DIR/Kerberos Auth Service/logs/KerberosAuthService.err.log
|Error information about the process running the enterprise services.|
|Enterprise services process wrapper logs||INSTALL_DIR/User Auth Service/logs/UserAuthService.wrapper.log
INSTALL_DIR/Directory Sync Service/logs/DirectorySyncService.wrapper.log
INSTALL_DIR/Kerberos Auth Service/logs/KerberosAuthService.wrapper.log
|Information about the process running the enterprise services such as Java options and process ID.|
Enabling DEBUG Mode for Connector Log Files
To help troubleshoot issues with your deployment, you can enable DEBUG mode for the servicename-service.log files so that DEBUG messages are written to the log files. These messages give you more detailed information about the issue.
To turn on DEBUG mode, follow these steps:
- Log in to the connector server.
- Edit the log4j2-override.xml file for the service you are troubleshooting.
- To adjust the log level for the Directory Sync service, edit the INSTALL_DIR\Workspace ONE Access\Directory Sync Service\conf\log4j2-override.xml file.
- To adjust the log level for the User Auth service, edit the INSTALL_DIR\Workspace ONE Access\User Auth Service\conf\log4j2-override.xml file.
- To adjust the log level for the Kerberos Auth service, edit the INSTALL_DIR\Workspace ONE Access\Kerberos Auth Service\conf\log4j2-override.xml file.
- In the following lines, change INFO to DEBUG:
<Loggers> <Logger name="com.vmware" level="INFO"/> </Loggers> <Loggers> <Root level="INFO"> <AppenderRef ref="asyncFileLogger"/> </Root> </Loggers>
- Save the file.
The changes take effect in a few minutes. DEBUG mode is turned on for the service's servicename-service.log file. For example, if you edited the Directory Sync service's log4j2-override.xml file, DEBUG mode is turned on for the eds-service.log file.
Tailing Connector Log Files
You can tail log files to view the bottom n number of lines from a log file. You can also use the -wait option with the tail command to monitor the logs. With the -wait option, the specified number of lines are printed to the console every time the log is updated.
- In the connector server, open Windows PowerShell.
- Navigate to the folder that contains the log file.
- Enter the following command:
Get-Content logFile -Tail numberOfLines –wait
Get-Content eds-service.log -Tail 2 –wait
For information about increasing the size and number of log files, see Increasing the Size and Number of Workspace ONE Access Connector Log Files.