Troubleshooting

Overview

AidView is an application that uses the Application Programming Interface (API) from Kit Wallace's AIDVIEW-DB in order to visualise International Aid Transparency Initiative (IATI) data.

If AidView is down then appropriate people should be notified by the server monitoring script "Is My Site Down?". When this happens the following checks should be made:

Troubleshooting Aidview

Is the API available?

• Check which API is being used by AidView here https://github.com/whiteoctober/IATI/issues/71
• Go to the address shown for the DB/API of the current live version of AidView (eg. data.aidinfolabs.org)
• If the page displays without an error then click on "Query API"
• You should now see the Query interface. Run an example query to check that the API is running. To do this you will need to select at least one of the entries for a facet in the top of the screen and the type of result you want to receive as a minimum
• Submit the query and check the response

If you believe that the issue lies with the AIDVIEW DB then report this to Kit Wallace.

Is http://aidview.net available?

• Go to http://aidview.net and check if it is available. The server monitoring may have picked up a short period of downtime.
• If the homepage is not showing in your browser then try the following

1. Press CTRL+REFRESH (Windows machines) in your browser to force a refresh.
2. Use a different browser and see if you have the same issue
3. Check the site using a service such as http://www.downforeveryoneorjustme.com/
4. Check the Redis cache on heroku.

• Login to Heroku at https://id.heroku.com/login
• Under apps select "aidview"
• Click on "Redis To Go Small"
• On the following page you will see a memory bar that shows you how full the cache is.

5. Consider clearing the cache using http://aidview.net/clear-cache

• If none of the above resolve the issue and if you have completed the checks on the API, then contact White October through their support desk: support@whiteoctober.co.uk