Webinar

UrbanCode Deploy as a Container – Troubleshooting

Print

Overview

Did something go wrong when running UrbanCode Deploy as a container? This page contains information to help with debugging issues you may see when running the UrbanCode Deploy server as a container.

Checking the init Container

When you install a release of UrbanCode Deploy using the provided helm chart, two containers are created. The first is named init and performs some initialization steps, including initializing your database if needed.

To get logging information for the init container, enter the command:

kubectl logs [pod name] -c init

Part of the initialization process involves connecting to the database and pulling the UrbanCode Deploy version information from the database. If you are installing a new release of UrbanCode Deploy with a new database, the database will not be initialized and not yet contain an UrbanCode Deploy version. In this case, expected to see a message such as:

[Error] Table DS_DATABASE_VERSION does not exist.

After the error/warning message, you should see a message indicating the database has been initialized. It may take some time for the database to initialize.

If connecting to a previously initialized database, the version of UrbanCode Deploy used to initialize the database should be displayed.

Checking the ibm-ucd-prod Container

Once the init container has completed, the UrbanCode Deploy container should start. Installation and setup logs may be viewed by running:

kubectl logs [pod name] -c ibm-ucd-prod

Once the container is running, you may execute commands inside the container using:

kubectl exec -it [pod name] -- /bin/bash

The UrbanCode Deploy server is installed under /opt/ibm-ucd/server. You may navigate to that directory and explore settings and log files as you do with on-prem UrbanCode Deploy.