Troubleshooting

Issue

What is happening

Solution

Run docker ps, but the elasticsearch container is not present. The same results occur even on retry.

Insufficient memory has been set for Docker on the local server.

Increase Docker memory.

In a Linux server/VM, run docker ps, the containers are complete. After a while, the elasticsearch container is closed and another one is created. A check of the logs for the elasticsearch container shows that the vm.max_map_count is too low.

The max_map_count has been set too low. By default, this is about 60K+.

Set the vm.max_map_count to be 262144.

Running docker images or docker ps -a shows a long list of old images or closed containers.

 

Run docker system prune -f.

Run docker ps, the arcoserver container goes up and down. A check of the logs for the closed container shows a network connection issue.

The container cannot connect to the SQL Server/instance.

Fix the connection string - make sure to use IP.

Make sure that the SQL Server allows SQL log in and that Port 1433, on the server where SQL is located, is open.

Sonitrol CORE has been set up to use http, all containers are running, but Sonitrol CORE is not displaying in the browser.

HTTP is being used by another service.

Either stop the HTTP service (net stop http) or change the port.

Some of the containers are not running.

Either the correct images have not been loaded or are in the process of being loaded.

Pull/load the images of the missing container using docker pull spgcontrols/<image>:<branch>

After updating Sonitrol CORE, the arcoservice container is erratic. One moment it is running, the next it is not.

There has been a database schema change in the update which has not been implemented.

Rebuild the views/state of the database.

Docker cannot start because there is an instance already running.

Docker is already being run as a server, so running Docker again causes this issue.

Stop Docker from starting up on boot.

Go to Docker > Settings and untick Start on Login.

Running arcoservice using docker service create -secret SQL_CONNECTION ... does not work because it uses the incorrect connection string.

Secrets were removed (left swarm) or have not been created at all.

Use docker run and add the connection strings as environment variables or create the docker secrets.

When installing the gateway schemas, logs indicate that there is an unauthorized token.

The gateway username or password has been changed.

When installing the gateway schemas, supply the environment variables ARCO_USER and ARCO_PASSWORD.

Sonitrol CORE occasionally crashes.

The user who set up Docker is logged out from the server.

Run Sonitrol CORE as a service using NSSM or remove the automatic log out.

 

See Also  

Appendix