Diagnosing Autoreduction

If, as a developer, you encounter a problem with autoreduction there are some common things to check to identify where the problem may be. Below is the suggested steps in order to work out what may be causing a problem (please add to this list if you find any other common issues/resolutions you encounter):

End of Run Monitor

• Any exceptions?
  • Check the code runs locally
• Does this appear to be collecting runs?
  • Use Ctrl+F to search the log file for the run you believe to be missing
  • If it's not there, you can attempt to restart the End of Run Monitor via the windows Service manager

Queue

• Are the runs being submitted to ActiveMQ
  • Inspect the queues
    • Run ActiveMQ/hawtio with port=8161 and path=api/jolokia
    • Is there lots of run in /DataReady that are just stuck there? If so there might be an issue with the messages being ingested by the QueueProcessor
  • Restart ActiveMQ
• Are the runs being ingested by the QueueProcessor
  • _restart the QueueProcessors QueueProcessors/restart.sh

Mantid

• Is Mantid unable to find files?
  • Ensure that the file mantid is trying to find exists in the ~/.mantid/Mantid.User.Properties file
  • Ensure that the cycle mapping file is up to date - POLARIS and GEM only

WebApp

• Not responding
  • Check Apache is still running
  • Ensure there are no errors in the logs for Apache