Log files

Use the installation log files and validation reports to help troubleshoot problems that occur during the installation.

Installation log files

Log files for a deployment are stored on the installation server in the <installation_server_home>/src/deployment/<deployment-name>/logs/nodes directory.

For example, if your deployment is named CorporateFinance, the log files for each deployed server are located in: <installation_server_home>/src/deployment/CorporateFinance/logs/nodes

The nodes directory contains a subdirectory for each server in your deployment, for example:
Application Server1
Application Server2
Database Server
Global Search Server
Report Server1
As a deployment progresses through the Validate, Install, and Configure phases, the following log files are created in the subdirectories:
  • pre-vali.log
  • install.log
  • config.log

You might also see a restart.log file in the application server subdirectories.

When a component is installed remotely, the log files are copied from the remote server to the appropriate subdirectory on the installation server automatically. For example, if Application Server2 is installed on a remote computer, the files from the remote computer are copied to the Application Server2 directory on the installation server computer.

The subdirectories also contain JSON files that contain metadata relevant to the deployment of that server. Do not delete the JSON files.

The base directory, <installation_server_home>/src/deployment/<deployment-name>/logs/ also contains a log file that is named installer.log that contains logging information about the installation server.

Most log file entries contain a time stamp followed by the log message's status (error, warn, or info). Examine the log files for entries that contain error for any issues that might need to be addressed.

The info entries are primarily progress messages.

The warn entries indicate that a non-fatal issue was encountered. Some post-installation action might be needed.

The error entries indicate that an issue occurred. In most cases, you must take corrective action in order for the deployment to proceed.

Validation reports

During a deployment, the validation process runs at various points. If you are using the installation app, for example, the validation process runs each time that you click Validate.

The status of each validation is summarized in a color-coded Validation_Report.pdf file. If you are using the installation app, you can click a link to download the validation report.

Figure 1. Viewing the validation log
The installation app shows a link called View log here. You can click it to download the validation log.

The validation reports are stored on the installation server in the<installation_server_home>/src/deployment/<deployment-name>/validation directory.

On the individual servers where the installer agents are running, validation reports for each server are stored in a validation subdirectory within each server-specific directory. For example: <agent_install_home>/src/deployment/<deployment-name>/logs/nodes/Database Server/validation.

New PDF files are generated each time that a validation is run.