Troubleshooting - Data360_DQ+ - 11.2

Data360 DQ+ Enterprise Installation
Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
11.2
ft:locale
en-US
Product name
Data360 DQ+
ft:title
Data360 DQ+ Enterprise Installation
Copyright
2024
First publish date
2016
ft:lastEdition
2024-10-15
ft:lastPublication
2024-10-15T15:12:18.685000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Infogix
L4_Investment_Segment
Data 360
L5_Product_Group
Data 360
L6_Product_Name
DQ+

Docker issues

During the application of a patch, you may run into a situation where a Docker container fails to start or remains in restarting mode in a loop. There are multiple reasons why this may occur; however, common cases are as follows.

Docker Service failure

In this case, try to restart the Docker Service and monitor the Docker Service logs. Instructions on how to monitor the Docker Service logs can be found here:

https://docs.docker.com/engine/reference/commandline/service_logs/

Often, logging out and relogging in the current user can also fix the Docker Service or any command availability related issues.

Docker image entry-point resources are unavailable

If this occurs, stop the Docker container. Then, try to start a new container with a different entry-point, using the following command:

docker run -it --entrypoint /bin/bash <image id>

This command will start the container and will skip the image’s default entry-point execution. This should eliminate the execution of any resource access issues that were occurring during the execution of the default entry-point. At this point, you can then look at the entry-point’s implementation and try to understand what may have caused the issue. Note that this approach will not fix the issue, but it will provide you with an effective method of analysis to find the issue’s root cause.

Docker container corruption

You may potentially run into a situation where a Docker container becomes corrupted or damaged. In this case, you can purge the damaged container and start a new one.

To initialize a brand new Docker container, run the following commands:

Note: Please note that unless a container starts successfully, you cannot use the Sagacity library scripts to take a backup. Please ensure that once you purge a container you do not delete any of the directories (mapped volumes), so that when the new container starts it will use existing data and state.
  1. Purge existing container

    docker rm -f <container name or id>

  2. Create a container

    Web/Application Server: <dqplus home>/bin/startApplication

    Postgres/Application DB: <dqplus home>/bin/startApplicationDb

    NGINX/Load Balancer: <dqplus home>/bin/startLoadBalancer