Deskpro instances run in Docker containers. A problem is raised if any of these containers are not running.

Remediation

If you receive feedback from the OPC that your instance containers are not running (either on the instance page or via the Problems page), please try these troubleshooting tips to get the containers started.

1. Check if the instance containers are actually running by logging into the OPC host via SSH and running sudo docker ps. This should provide a list of all running containers and you should expect to see 2 containers running for the OPC, and 2 containers running for each of your instances:

CONTAINER ID   IMAGE                                          COMMAND                  CREATED        STATUS        PORTS                                     NAMES
8f1091caaf8d   deskpro/deskpro-opc-dev:0.0.0-dev.8279365227   "/usr/local/bin/entr…"   22 hours ago   Up 22 hours   8080/tcp, 127.0.0.1:40337->40337/tcp      opc_webgui
df5b24723962   deskpro/deskpro-opc-dev:0.0.0-dev.8279365227   "/usr/local/bin/entr…"   22 hours ago   Up 22 hours   8080/tcp                                  opc_queue
a6aa96f9bc01   deskpro/deskpro-product:2024.11.0              "/usr/local/bin/entr…"   41 hours ago   Up 41 hours   80/tcp                                    deskpro_helpdesk_tasks
93b82991a744   deskpro/deskpro-product:2024.11.0              "/usr/local/bin/entr…"   41 hours ago   Up 41 hours   0.0.0.0:44703->80/tcp, :::44703->80/tcp   deskpro_helpdesk_web
 copy

1. If do not see your instance containers running, please run sudo systemctl start deskpro@<Instance Name> (e.g. sudo systemctl start deskpro@helpdesk) and then run sudo docker ps again to confirm the containers are now running.

Troubleshooting

If the instance containers do not start, or only start temporarily and then stop, please check for these common causes of failure.

Low disk space

Run the command df -h to see the remaining disk space on your server. If you are running low, you may want to delete some old backups, purge your database binary logs or grow your disk space.

Low memory

Run the command free -h to check your available memory. If your available memory is too low, then the instance will refuse to start. You will need to allocate additional memory to the server for the instance to start.

If you have checked the above and your instances are still failing to start, please contact Deskpro Support for further assistance.