Open topic with navigation

TIBCO ActiveMatrix® Service Grid - Container Edition 1.0.0

# Troubleshooting

If you encounter problems with installation, make sure that your system meets all the prerequisites. Next, check the logs for potential problems.

Problem

Docker image build fails while downloading base image.

Troubleshooting tips

Ensure that you can pull the Docker image.

Pull the image by using `docker pull` command and then try building the image.

Example:

For UBI7 Docker image, you can manually pull the Docker image from the Docker registry by using following command:

    docker pull registry.access.redhat.com/ubi7/ubi:latest

Problem

When building the application Docker image the following error occurs:

    failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c ./config.sh]: exit code: 1

Troubleshooting tips

This error comes from Docker by default when any build process returns non-zero code. Ensure that application configuration YAML file is valid. Use the `checkConfig` script in the `amsgce-runtime-<version>/daautil/bin` folder to validate the configuration. For more information about validating configuration YAML file, see TIBCO ActiveMatrix® Service Grid - Container Edition Administration.

Problem

Pod console logs do not print timestamp at start of each line.

Troubleshooting tips

To print the timestamp in logs, add the following lines in the console appender logging configuration:

    %d{dd MMM yyyy HH:mm:ss,SSS}

Example:

    <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
    <param name="Target" value="System.out"/>
    <param name="Threshold" value="TRACE"/>
    <layout class="com.tibco.tpcl.org.apache.log4j.PatternLayoutEx">
    <param name="ConversionPattern" value="%d{dd MMM yyyy HH:mm:ss,SSS}%t] [%-5p] %c - %m%n"/>
    </layout>
    </appender>

Alternatively, for kubectl, use `timestamps` flag to print timestamps in logs:

    kubectl logs <POD> -n <Namespace_Name> --timestamps

Problem

The following error occurs in the Application Configurator container logs when running Application Configurator in Docker. You can also view this error when running a TIBCO ActiveMatrix application in Docker:

    AMXCENode [Start Level Event Dispatcher] [ERROR] com.tibco.hkce.konex - Failed to initialize HAWK agent, tcp_self_url and/or ami_agent_url not specified

Troubleshooting tips

This error is because the Hawk microagent needs Hawk agent details to connect. When running the Application Configurator, you do not need to run TIBCO Hawk - Container Edition. Therefore you can ignore this error. But if you are running TIBCO ActiveMatrix application in Docker and want to run TIBCO Hawk - Container Edition with it, you must pass the `agent_ami_session_url` and `tcp_self_url` environment variables. For more information about these variables, refer TIBCO Hawk - Container Edition documentation.

For example:

    docker run --rm -d -p 7777:7777 --name bookstore -e agent_ami_session_url=hawkagent:2571 -e tcp_self_url=<hostname>:2551   --network amxce-net bookstore

Viewing Hostname Information for the Running Java Processes

You can view the hostname for the running java processes in the JVM arguments. Using the hostname, you can identify a container, where the process is running. To view the hostname for the running java processes, run the following command:

    ps -eaf | grep java

JVM arguments contain the hostname, as highlighted in the following sample command output:

    1001280+ 30842 30836 2 Oct13 ? 00:22:29 java -DTIBCO_HOME=/opt/tibco/tibco.home -DSCRIPT_VERSION=3 -DHOSTNAME=amxce-bookstore-deployment-547748b7b5-ltjzt -Dcom.tibco.amf.hpa.tibcohost

Copyright © 2020-2021. TIBCO Software Inc. All Rights Reserved.