Troubleshooting Integration Controller issues
For information about the Integration Controller installation and usage, see Installing and setting up the connector development environment and Installing and configuring sites to run on-premises connectors.
If you experience any issues with Integration Controller, refer to the following information for troubleshooting.
Common Integration Controller issues
The following table lists issues that might occur while installing and using Integration Controller, and corresponding corrective actions to fix these issues.
| Issue | Corrective action |
|---|---|
| Unable to install Docker Engine | Upgrade the operating system. For more information about the system requirements for Integration Controller, see Installing and setting up the connector development environment. |
| Docker Compose fails to pull or start containers | Verify the Docker Engine and Docker Compose versions. For more information, see Installing and setting up the connector development environment. |
Cannot connect to BMC Helix Integration Service from an on-premises network that is behind a proxy. Docker login fails during installation with the following error message:
|
|
| The site goes offline, even though Integration Controller is installed and the same site was previously online | Restart Docker from your installation directory. Alternatively, use the validation utility to determine if the environment is set up correctly. For more information, see Validating the connector development environment. |
| Primary or secondary controllers are offline frequently, and ActiveMQ connectors loses connection to the ActiveMQ on the cloud | This issue can occur if there is insufficent memory for the ActiveMQ to run the processes when a flow is executed. Complete the following procedure to customize the Java heap space and increase the memory limits: To customize the Java heap space and increase the allocated memory |
To customize the Java heap space and increase the allocated memory
- Locate
reinitControllerscript on your controller's system and open the script to edit. - Locate an empty line after "fi" and before "$sh_c 'docker-compose down'" and add the following line in the located empty line:
echo -e "ACTIVEMQ_MIN_MAX=-Xms6G -Xmx6G" >> panama-on-premise.env
where-Xmsis the minimum memory limit and-Xmxis maximum memory limit. In this case, the limit is set to 6 GB, and you can change the value as required. - Save the file.
- Enter the following command to run the reinitController scripts:
./reinitController - Then execute the following command:
docker logs panama-activemq - In docker logs search for "JVM args:"
- Make sure that activemq java startup command contains memory limits set in step 2. For example, if you set the limits to 6 GB, the JVM args should mention:
JVM args: -Xms6G -Xmx6G -XX:...
To access Integration Controller logs
For more information about the errors that might occur during Integration Controller usage, you can check the Integration Controller logs. To access them, perform the following actions:
- On the server where Integration Controller is installed, run the following command:
docker ps
The list of all docker containers is displayed. Access the logs of a particular container by using the container name or the container ID, and running one of the following commands:
docker logs container_nameor
docker logs container_IDThe logs of the specified container are displayed.
Important
For more information about the Docker logs processing, see the official Docker documentation
.
Comments
With latest versions the installation goes to the point when possibly docker login fails with the message:
Error response from daemon: Get https://registry.integrate.bmc.com/v2/: dial tcp 54.209.152.200:443: getsockopt: connection refused
The below topic suggests that it might be due to SSL certificate problems: https://github.com/sameersbn/docker-gitlab/issues/890
However, the connection is still unsuccessful
and indeed
Solved: When connecting from on-premise network behind proxy follow the instructions here: https://docs.docker.com/engine/admin/systemd/#httphttps-proxy
and create a file /etc/systemd/system/docker.service.d/https-proxy.conf with correct proxy configuration
Thanks for finding the solution, Iassen. We will update the content soon And sorry again for the (very) late reply, strangely enough we didn't get automatic notifications for your comments like we usually do (something we're looking into).
Problem 2: Controller Installation succeeded but Status is shown as Not Installed under Sites
Queue connection established. Component: panama-flowengine last heartbeat @ 2017-10-23T13:12:23.954Z
Hi Iassen, somehow your comments slipped under our radar – we sincerely apologize. Do you still have problem 2? Please let us know. Sorry for the delay again.
Log in or register to comment.