Common Issues and How to Fix Them
- Feanil Patel (Deactivated)
- Andy Armstrong (Deactivated)
Table of Contents
Common Issues
LMS shows a message "There has been a 500 error"
This error means that an internal exception was raised in the LMS's Python code. In this situation, LMS writes out a stack trace to its log file:
/edx/var/log/lms/edx.log
You can find this stack trace by opening the log file and scrolling to the bottom.
If the stack trace isn't enough to diagnose the problem, post it in the #ops Slack channel and someone should be able to help you
Studio shows the message "An error occurred in Studio and the page could not be loaded."
This error means that an internal exception was raised in Studio's Python code. In this situation, Studio writes out a stack trace to its log file:
/edx/var/log/cms/edx.log
You can find this stack trace by opening the log file and scrolling to the bottom.
If the stack trace isn't enough to diagnose the problem, post it in the #ops Slack channel and someone should be able to help you
Migrations Have Not Been Run
If you ever see errors along the lines of the one below saying some table doesn't exist, it means that there are migrations that haven't been run that you need to run.
Table '<name_of_some_table>' does not exist
The error should go away once migrations have been run.
Other Resources
If your issue is not listed on this page, there are many other resources that might help you:
- http://docs.edx.org/ - in particular, read the guides for the version of Open edX that you are using
- If you are still stuck, reach out to the community through email or Slack