Troubleshooting Integration Controller issues

When you install Integration Controller by using the installation command, Docker Engine and Docker Compose are installed automatically (if they were not installed earlier). For information about how to install Integration Controller, see Installing and configuring sites to run on-premises connectors. If you experience issues during the Integration Controller installation or usage, refer to the following information for troubleshooting.

Related topics

Troubleshooting

Troubleshooting BMC Helix Connector Designer issues

Troubleshooting connector configuration issues

Troubleshooting flows

How to work with Docker logs

The following table shows issues that might occur while installing and using Integration Controller, and corresponding corrective actions to fix them:

IssueCorrective action
Unable to install Docker Engine

Upgrade the operating system. Recommended versions are as follows:

  • Ubuntu 16.04,x
  • CentOS 7.03
  • Red Hat Enterprise Linux 7.4
Docker Compose fails to pull or start containers
  1. Verify the Docker Engine version. 
    If the Docker Engine version is earlier than version 18.0x, upgrade to version 18.0x or later.
  2. Verify the Docker Compose version. 
    If the Docker Compose version is earlier than version 1.9, upgrade to version 1.9 or later.


Cannot connect to Integration Service from an on-premises network that is behind a proxy. Docker login fails during installation with error message:

Error response from daemon: Get https://registry.integrate.bmc.com/v2/: dial tcp 54.209.152.200:443: getsockopt: connection refused

  1. Follow the instructions outlined in the Docker HTTP/HTTP proxy documentation.
  2. Create an https-proxy.conf file at /etc/systemd/system/docker.service.d/https-proxy.conf with your proxy configuration.


The site goes offline, even though Integration Controller is installed and the same site was previously onlineRestart Docker from your installation directory.

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:

  1. On the server where Integration Controller is installed, run the following command: docker ps 
    The list of all docker containers is displayed.
  2. 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_name
    • docker logs container_ID

  • The logs of the specified container are displayed.

Note

To learn the advanced options of Docker logs processing, see the official Docker documentation .


Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Iassen Manov

    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

    Oct 19, 2017 11:32
    1. Iassen Manov

      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

      Oct 23, 2017 07:04
      1. Tashfeen Mahmud

        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).

        Apr 05, 2018 01:52
  2. Iassen Manov

    Problem 2: Controller Installation succeeded but Status is shown as Not Installed under Sites

    panama-monitor@0.1.3 heartbeat /opt/panama-monitor node lib/heartbeat

    Queue connection established. Component: panama-flowengine last heartbeat @ 2017-10-23T13:12:23.954Z

    Oct 23, 2017 08:43
    1. Tashfeen Mahmud

      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.

      Jan 22, 2018 03:35