Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Latest version (13.0.2) fails to local quickstart

  • By Sad and frustrated
  • on 01/05/2022

This seems to be brand new, so I feel bad giving a first review about a failed launch. But then again, you would think the developer would test it. The point of this image is to get you up and started with an open edX instance on AWS quickly. I've done this before, a long time ago with an older version, and the scripts are always a bit of a pain. So this sounded like a great idea.

There is even a video that you can follow step by step (though it appears to use an older version). Aside from configuring the security group, you should basically be able to choose a supported instance type and default settings. You then access the web-based configurator and type "local quickstart". The problem is it takes a long time and then fails. There is nothing you can do, since the whole thing is intended to be self-contained. I tried twice from scratch. Will try the older version, but I hope it's not another waste of time.


  • By Régis Behmo
  • on 11/17/2022

I'm sorry the image is not working for you. I attempted to reach out at the time you posted your comment but it seems that my reply did not get through. For any problem related to this AMI, please post your questions on the official community forum: https://discuss.openedx.org/

  • By Sad trombone.
  • on 04/10/2022

For what it's worth, I tried both t3a.large and t2.large instances back in January when this failed. So maybe 8gb is not enough.

  • By Régis Behmo
  • on 03/09/2022

"Command failed with status 137" indicates that the process was killed due to a lack of memory. It is documented here: https://docs.tutor.overhang.io/troubleshooting.html#running-migrations-killed-command-failed-with-status-137-docker-compose Which EC2 instance size did you pick? It should be at least t3a.large.

  • By Sad trombone
  • on 03/02/2022

Here is where it fails (tried again March 2) Applying discussions.0002_add_provider_filter...Killed ERROR: 137 Error: Command failed with status 137: docker-compose -f /home/tutor/.local/share/tutor/env/local/docker-compose.yml -f /home/tutor/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /home/tutor/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm lms-job sh -e -c dockerize -wait tcp://mysql:3306 -timeout 20s echo "Loading settings $DJANGO_SETTINGS_MODULE" ./manage.py lms migrate # Create oauth2 apps for CMS SSO # https://github.com/edx/edx-platform/blob/master/docs/guides/studio_oauth.rst ./manage.py lms manage_user cms cms@openedx --unusable-password ./manage.py lms create_dot_application \ --grant-type authorization-code \ --redirect-uris "http://studio.apsta2358.xyz/complete/edx-oauth2/" \ --client-id cms-sso \ --client-secret czBYaJ0dy80ZwvxDadP9GHya \ --scopes user_id \ --skip-authorization \ --update cms-sso cms ./manage.py lms create_dot_application \ --grant-type authorization-code \ --redirect-uris "http://studio.apsta2358.xyz:8001/complete/edx-oauth2/" \ --client-id cms-sso-dev \ --client-secret czBYaJ0dy80ZwvxDadP9GHya \ --scopes user_id \ --skip-authorization \ --update cms-sso-dev cms # Fix incorrect uploaded file path if [ -d /openedx/data/uploads/ ]; then if [ -n "$(ls -A /openedx/data/uploads/)" ]; then echo "Migrating LMS uploaded files to shared directory" mv /openedx/data/uploads/* /openedx/media/ rm -rf /openedx/data/uploads/ fi fi # Create waffle switches to enable some features, if they have not been explicitly defined before # Completion tracking: add green ticks to every completed unit (./manage.py lms waffle_switch --list | grep completion.enable_completion_tracking) || ./manage.py lms waffle_switch --create completion.enable_completion_tracking on >

  • By Sad trombone.
  • on 01/17/2022

13.1 just came out. Still doesn't work.

  • By Régis Behmo
  • on 01/17/2022

Hi! Can you please report the issues you faced on the Tutor forum? https://discuss.overhang.io It's difficult for me to understand what happened and to help you troubleshoot the problem without a thorough description. At the very least, I need the error message that was displayed when the installation crashed. This commercial AMI was designed to help financially support the open source project, so bad reviews hit me where it hurts most. The AMI submission process is not very convenient, so it's not possible for me to test each and every version. I hope we can work towards a solution together.