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.
|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.|
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:
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_name
docker logs container_ID
The logs of the specified container are displayed.
For more information about the Docker logs processing, see .