Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

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.

Troubleshooting

Assess server current status

The application could be down because of two main reasons:

  1. The server is not online, in which case nothing can be done until the server is back online and accessible.

  2. The server is online, but the applications could not restart because something got corrupted.

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.

E.g. The eLearning server could be online, in which case it will appear as UP in the Metrics dashboard, but if Moodle is not running, it will show as DOWN in the Web apps dashboard.

  • No labels