Info |
---|
Note: These steps apply to troubleshooting an opensrp server. For this Document we shall be using a boresha-aya staging server to show examples. |
...
1. Server Unavailability (Error code 4xx)
Case 1: Client is not able to access the server
You can use the following ways to check if the service is available.
Navigate to the server URL/IP
Use a locally installed browser to navigate to the server URL
Code Block https://boresha-afya-stage.smartregister.org/opensrp/ or 63.32.56.42
Ping the URL/IP address i.e
Code Block ping 63.32.56.42
Depending on the results of step 1, if the server returns a response that denotes that the service is available you can attempt any of the following steps
Connect to the server, you can use an ssh client for this:
Code Block ssh user@serverip.com
Check that the actual service in the server is running.
Use systemctl to check that OpenSRP , OpenMRSand/ nginx services are running. You can use these commands
Code Block systemctl status tomcat-openrsp
Code Block systemctl status tomcat-openmrs
Code Block systemctl status nginx
Use systemctl to start or restart any of the services that are down
Code Block systemctl restart ‘service-name’
If the services are running , confirm that all that port 8080 is allowing all incoming traffic to the server
Code Block sudo lsof -i -P -n | grep LISTEN
...
i. Check that the server is running. Log in to your AWS/Google cloud/Azure/Ali Cloud/Digital Ocean console and confirm that the server is online
More
Determining which server version of code is deployed.
ssh into the server and run the command
less /usr/lib/collectd/plugins/monitored-apps-list.sh
Related articles
Filter by label (Content by label) | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Page Properties | ||
---|---|---|
| ||
|