Troubleshooting the BMC Helix Intelligent Integrations issues
This topic describes the issue that you might encounter when using BMC Helix Intelligent Integrations.
Issue symptoms
The following error message is displayed when you access the BMC Helix Intelligent Integrations on-premises gateway UI for which authentication is enabled:
400 error: This page isn't working.
In addition, the swp-authproxy container logs contain the following error message:
No valid user identifier was found, redirecting to the RSSO Server.
Resolution
Make sure that the OAuth client is registered correctly. For more information, see Setting up authentication for the on-premises gateway.
Issue symptoms
After you install or upgrade the on-premises gateway, some of the containers might go into the restarting state due to permission issues, and the container logs show error messages similar to the following:
- swp-prometheus container: /var/lib/prometheus/queries.active: permission denied
- swp-grafana container: attempt to write a readonly database
This issue might occur if the user context for a container is set to a non-root user.
Issue scope
This issue occurs during fresh installation or upgrade of the on-premises gateway.
Resolution
Perform the following steps to resolve the issue:
- Go to the server where the on-premises gateway is deployed.
Stop the docker-compose or podman-compose service:
docker compose downpodman compose -f podman-compose.yaml down- Open the /<IIGateway_INSTALL_DIR>/hii/docker-compose.yaml or podman-compose.yaml file with a text editor.
Locate the section corresponding to the container that is in the restarting state and set the user context:
For example, if the swp-prometheus container is in restarting state, locate the prometheus section, and add the following line:user: rootThe following code snippet shows the sample section:
prometheus:
image:attach:xwiki:Helix-Common-Services.Intelligent-Integrations.BMC-Helix-Intelligent-Integrations.bhii244.Troubleshooting.Troubleshooting-the-BMC-Helix-Intelligent-Integrations-issues.WebHome@filename containers.bmc.com/bmc/hii-prometheus:v2.55.1-GA
container_name: swp-prometheus
user: root
volumes:
- ./conf/prometheus:/etc/prometheus
- prometheus_data:/prometheus- Save the file.
Start the docker-compose or podman-compose service:
docker compose up -dpodman compose -f podman-compose.yaml up -d