On this page:
| Table of Contents | ||
|---|---|---|
|
Sudden shutdowns to the servers can cause multiple issues to the software running on them. The most common errors are due to corruption of Docker, containers, or database instance. If any of the systems running on the MoH servers is down, follow the below guidelines to troubleshoot, identify the cause and fix the errors.
...
| Info |
|---|
Access the monitoring server (https://bao-zwe.monitoring.psidigital.org/grafana) to verify the different servers status and applications. The ‘Metrics’ dashboard will display the server status and the current resources utilization. The ‘Web apps’ dashboard displays the status of the different applications running in any of the servers. |
If the server is online, but any application like Moodle is not running, continue to the next step.
Identify the issue
Enter the server using SSH and start by checking the application status.
Docker commands can only be executed with sudo privilegies or as the root user.
Execute the following command to check which Docker containers are not running:
| Code Block |
|---|
docker ps |
This is a list of the containers that every server should be running
eLearning server
moodle-moodle-1
moodle-postgresql-1
Analytics server
VMMC Server
First of all, try to start the stopped containers. If after some minutes the containers are still up, its probable that nothing is corrupted and a restart policy was not set for the containers. If the containers show an uptime of several minutes under the status column, the application most likely will be working.
Code Block docker ps -a #to display all containers, even stopped ones docker start <container-id> #start Docker containers
| Note |
|---|
If executing any of the above commands throws an error, it’s probably that Docker itself got corrupted and needs to be reinstalled on the machine. Follow the Docker documentation to perform this process. |