Additional troubleshooting issues

Consult this topic for information about additional troubleshooting issues.

The deployment manager aborts due to network drop

Perform the following steps:

Run the following command:
$helm ls --all -n <namespace> | grep pending-install
helm delete <each of the service in previous step> -n <namespace>
Re-run the installer ./deployment-manager.sh

The deployment for a service fails

Run the following command:
$helm ls --all -n <namespace> | grep -I fail
Create a zip of the log files and share the logs folder with BMC Support team.

The installer exits

The installer exits because some service or job has taken more time to pull the image or Job ActiveDeadlineSeconds has exceeded.

Rerun the installer.

$./deployment-manager.sh

Kafka scripts fail with exception

If kafka scripts fail with below exception, run "export JMX_PORT=5560" to use different port to mitigate the issue.

$ kafka-topics.sh --list --zookeeper kafka-zookeeper:2181"
Defaulting container name to kafka.
Use 'kubectl describe pod/kafka-2 -n dark-helmet' to see all of the containers in this pod.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use (Bind failed)

The selections in the drop-down list in the configurations screens of monitor are not displayed

Run the following SQL script to update the Cassandra database:

./commons/run_cql_query.sh

The tenant entry is not added for intelligent integration DB (tdc_integration)

Run the following SQL script to update the PostgreSQL database ONLY if the tenant entry is not added for intelligent integration DB (tdc_integration).

./commons/run_sql_query.sh

rsso-prod-dbinit pod is seen in Error state and the installation aborts

~]# helm delete rsso -n <namespace>

Workaround: Delete the PostgreSQL pods, wait for PostgreSQL pod to come into running state.

Troubleshooting issues when publishing REST API services

You can publish REST services by using AR System REST API. The REST API uses a dedicated Java Server Pages (JSP) Engine Jetty.

To troubleshoot the Jetty server and REST API connection issue issues, see Troubleshooting issues when publishing REST API services in BMC Helix Innovation Suite documentation.