Deployment logs are generated during the deployment or installation of the Hybrid Data Pipeline server. These logs may be useful for viewing deployment configurations and troubleshooting deployment issues. The log files you use and how you obtain them may vary, depending on whether you install the server on Linux or deploy the server with Docker.

Server deployment logs

When an installation directory is successfully created, server deployment logs are written to the Linux installation directory or the Docker container directory.

Server deployment log descriptions

Server deployment log files are written to the following directory:

opt/Progress/DataDirect/Hybrid_Data_Pipeline/Hybrid_Server/ddcloud

Server deployment logs include the following files:

  • deploy.log

    The deploy.log file provides details on the deployment process. In particular, this log file contains all parameters used in the configuration of the Hybrid Data Pipeline server, as well as any modifications to the system database schema.

  • error.log

    The error.log file provides error and warning messages received during the deployment process. If any error is received during deployment, the error message, or exception, is logged to this file.

  • final.log

    The final.log file provides the overall status of a Hybrid Data Pipeline server deployment. If no errors were received during the deployment process, the file will contain the message "Hybrid Data Pipeline deployment complete." If an error does occur during the deployment process, this file will contain a message that indicates where the deployment script encountered the error.

Accessing server deployment logs

While they may be accessed directly, server deployment logs are bundled with system log files. Therefore, they may be obtained with system log files through the Web UI, the API, or the getlogs.sh script. For details, refer to Obtaining system logs in the User's Guide.

If you want to access server deployment logs directly in a Docker deployment, you must use a Docker shell to reach them. The following command opens a Docker shell:

docker exec -it container_name bash

After opening the shell, you may navigate to the Docker container directory. For example:

cd opt/Progress/DataDirect/Hybrid_Data_Pipeline/Hybrid_Server

Linux installation program log file

The InstallAnywhere installation program is used to install the Hybrid Data Pipeline server on Linux. With the successful installation of the server, the following log file is written to the installation directory:

install_dir/_ProgressHDPServer_installation/Logs/Progress_DataDirect_Hybrid_Data_Pipeline_Server_Install.log

This file includes Java version information, user inputs during installation, a list of files overwritten during an upgrade, and a list of deployment settings.

Docker stdout and stderr logs

For Docker deployments, deployment information may be gathered through the stdout and stderr streams. You may use the followingdocker logs command to view this output:

docker logs container_name

The stdout logs show command outputs and includes information about services used to run Hybrid Data Pipeline. The stderr logs show message error output.

System database log

In addition to the deploy.log file, you may gather further information about the system database by reviewing the hdpCloudSchema.datestamp.log file. This log file is created during Linux installations or Docker deployments. It records information about the Hybrid Data Pipeline schema created in the system database. This file is written to the utility logs directory. For example:

opt/Progress/DataDirect/Hybrid_Data_Pipeline/Hybrid_Server/ddcloud/utils/logs

Installation failure logs

Linux installation

For a Linux installation, when the installer fails to create an installation directory, the following file is written to the machine's default temporary directory:

Progress_DataDirect_Hybrid_Data_Pipeline_Server_InstallFailed.txt

Docker deployment

When a Docker deployment fails, any logs present at the time of failure are bundled into a compressed archive file named hdp_logs.datetimestamp.tar.gz and written to the shared file location.

Silent installation logs

Silent installation is supported only with Linux installations. When performing a silent installation, the following logs may be written to the user's home directory.

  • SilentInstallError.log

    The SilentInstallError.log is generated when a silent installation fails. It provides information on why the installation failed.

  • SilentInstallInfo.log

    The SilentInstallInfo.log file is generated when hostname and port validation are skipped by specifying the following settings in the silent installation response file.

    SKIP_HOSTNAME_VALIDATION=true
SKIP_PORT_VALIDATION=true 
SKIP_LB_HOSTNAME_VALIDATION=true