Upgrading to Juniper fails with 'User matching query does not exist'

[shashi.kiran]

I tried to migrate to Juniper on my local machine using the steps mentioned at:

V10.0.0: Juniper is here!

Juniper, the 10th release of Open edX, is out! See the announcement here: https://discuss.openedx.org/t/juniper-is-here/ We’ve been hard at work upgrading Tutor to make sure that you can smoothly upgrade your Open edX platforms from Ironwood to Juniper. Today, I’m pleased to announce that we’ve managed to streamline the upgrade process to the point that it should be transparent for most users. Upgrading Tutor Download the latest (v10.0.0) release of Tutor: https://docs.tutor.overhang.io/insta…

[Issued stop, backup and quickstart commands]
It seems look up for a user account is failing. Below is the stack trace.

  File "./manage.py", line 123, in <module>
    execute_from_command_line([sys.argv[0]] + django_args)
  File "/openedx/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/openedx/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/openedx/venv/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/openedx/venv/lib/python3.5/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/openedx/edx-platform/openedx/core/djangoapps/oauth_dispatch/management/commands/create_dot_application.py", line 137, in handle
    user = User.objects.get(username=username)
  File "/openedx/venv/lib/python3.5/site-packages/django/db/models/manager.py", line 82, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/openedx/venv/lib/python3.5/site-packages/django/db/models/query.py", line 408, in get
    self.model._meta.object_name
django.contrib.auth.models.DoesNotExist: User matching query does not exist.
Error: Command failed with status 1: docker-compose -f /home/rf/.local/share/tutor/env/local/docker-compose.yml -f /home/rf/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /home/rf/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm lms-job sh -e -c dockerize -wait tcp://mysql:3306 -timeout 20s

export DJANGO_SETTINGS_MODULE=$SERVICE_VARIANT.envs.$SETTINGS
echo "Loading settings $DJANGO_SETTINGS_MODULE"

./manage.py lms migrate

# Create oauth credentials for Android application
./manage.py lms create_dot_application \
    --client-id android \
    --client-secret lKMMMN5g9sEYhlLa4kfZ39qj \
    --grant-type password \
    android \
    login_service_user

# 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

Update: Looks like it’s failing here

Create oauth credentials for Android application

./manage.py lms create_dot_application
–client-id android
–client-secret lKMMMN5g9sEYhlLa4kfZ39qj
–grant-type password
android
login_service_user

I probably do not have this user account login_service_user in my previous database. I have created this user and now running quickstart command again. Will revert with the result.

[shashi.kiran]

I was able to move forward after adding login_service_user account to Users table.
Now getting a different error.

> Initialising forum...
> docker-compose -f /home/rf/.local/share/tutor/env/local/docker-compose.yml -f /home/rf/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /home/rf/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm forum-job sh -e -c export MONGOHQ_URL="mongodb://$MONGODB_AUTH$MONGODB_HOST:$MONGODB_PORT/cs_comments_service"
> 
> bundle exec rake search:initialize
> bundle exec rake search:rebuild_index
> Waiting for mongodb/elasticsearch...
> 2020/06/16 14:29:33 Waiting for: tcp://mongodb:27017
> 2020/06/16 14:29:33 Waiting for: http://elasticsearch:9200
> 2020/06/16 14:29:33 Problem with dial: dial tcp 172.20.0.16:27017: connect: connection refused. Sleeping 5s
> 2020/06/16 14:29:34 Received 200 from http://elasticsearch:9200
> 2020/06/16 14:29:38 Problem with dial: dial tcp: lookup mongodb on 127.0.0.11:53: no such host. Sleeping 5s
> 2020/06/16 14:29:43 Problem with dial: dial tcp 172.20.0.16:27017: connect: connection refused. Sleeping 5s
> 2020/06/16 14:29:50 Problem with dial: dial tcp: lookup mongodb on 127.0.0.11:53: no such host. Sleeping 5s
> 2020/06/16 14:29:56 Problem with dial: dial tcp 172.20.0.16:27017: connect: connection refused. Sleeping 5s
> 2020/06/16 14:30:01 Problem with dial: dial tcp 172.20.0.16:27017: connect: connection refused. Sleeping 5s
> 2020/06/16 14:30:06 Problem with dial: dial tcp: lookup mongodb on 127.0.0.11:53: no such host. Sleeping 5s
> 2020/06/16 14:30:11 Problem with dial: dial tcp 172.20.0.16:27017: connect: connection refused. Sleeping 5s
> 2020/06/16 14:30:16 Problem with dial: dial tcp: lookup mongodb on 127.0.0.11:53: no such host. Sleeping 5s
> 2020/06/16 14:30:21 Problem with dial: dial tcp: lookup mongodb on 127.0.0.11:53: no such host. Sleeping 5s
> Error: Command failed with status 1: docker-compose -f /home/rf/.local/share/tutor/env/local/docker-compose.yml -f /home/rf/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /home/rf/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm forum-job sh -e -c export MONGOHQ_URL="mongodb://$MONGODB_AUTH$MONGODB_HOST:$MONGODB_PORT/cs_comments_service"
> bundle exec rake search:initialize
> bundle exec rake search:rebuild_index

[shashi.kiran]

One Possibility could be that docker containers are not linked[forum-job seems to be waiting for mongodb to be available]. Trying various options as of now.

[ejklock]

I have same issues. @regis any clue for this ?

[regis]

The missing login_service_user is strange.

The problem with connecting to Mongodb probably comes from the fact that the platform was not correctly upgraded. Please run:

tutor local upgrade --from=ironwood

[CherieCAF]

Hi Regis,

I also have the same issue.

And on running “tutor local upgrade --from=ironwood”, I get the following error:

 "Error: Command failed with status 137: docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })"

[shashi.kiran]

@regis Thanks for the answer.

The missing login_service_user is because probably I had deleted it earlier. I created the user account and moved ahead of that error. Now I am facing a different issue[forum-job waits for mongodb availability]. Please look at my subsequent replies.

I shall try tutor local upgrade --from=ironwood command and revert with the result.

[shashi.kiran]

@regis and @CherieCAF Below are the results of using tutor local upgrade --from=ironwood

1. I see courses previously i had in ironwood. I am yet to checkout the courseware, I shall check and revert if anything is missing.

2. The user accounts have also been retained. However I am unable to login to in the LMS. I get the following error

   We couldn’t sign you in.
   OAuth Client for the Login service, ‘login-service-client-id’, is not configured.

I am not able to login even with a new user. It looks like I am not being redirected to Dashboard[if I refresh local.overhang.io page then I am taken to the Dashboard]. I am able to login to the Django Admin portal as well.

Please let me know if I have to configure anything else to ensure this error goes away. I shall also look up some oauth related stuff in the meanwhile and revert if i find a fix.

@CherieCAF I faced the issue you had reported. This is what was my observation and the fix that I applied.

The mongodb upgradation happens in the following order 3.2 -> 3.4 -> 3.6. I had already a version of 3.6. I removed the 3.6 image and ran the command time. So mongodb eventually updated from 3.2 to 3.4 to 3.6.

Please note that I did not run the tutor local quickstart command while running any of the above commands.

[shashi.kiran]

@shashi.kiran

OAuth Client for the Login service, ‘login-service-client-id’, is not configured.

@regis I also was able to fix the login issue. I had to create the application “Login Service for JWT Cookies” under Django Auth Toolkit in the Admin Panel. This application is linked to login_service_user. The client Id should be ‘login-service-client-id’

Because this user was not available or may not have been created[Refer https://github.com/edx/edx-platform/blob/master/openedx/core/djangoapps/user_authn/migrations/0001_data__add_login_service.py], the application was probably not created during migration. Hence login was failing.
After adding this application from Django Admin portal. Login is working.

[regis]

@CherieCAF

“tutor local upgrade --from=ironwood”

@CherieCAF Can you please paste here the full log of running that command?

[CherieCAF]

@regis Please find below the full log:

~$ tutor local logs --tail=100 -f
docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local logs --follow --tail 100
Attaching to tutor_local_mongodb_1
mongodb_1         | 2020-06-18T08:33:23.094+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false),
mongodb_1         | 2020-06-18T08:33:23.164+0000 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredTiger
mongodb_1         | 2020-06-18T08:33:23.164+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:33:23.164+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongodb_1         | 2020-06-18T08:33:23.164+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongodb_1         | 2020-06-18T08:33:23.164+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:33:23.166+0000 F STORAGE  [initandlisten] BadValue: Invalid value for version, found 3.6, expected '3.4' or '3.2'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "3.6" }. See http://dochub.mongodb.org/core/3.4-feature-compatibility.
mongodb_1         | 2020-06-18T08:33:23.166+0000 I -        [initandlisten] Fatal Assertion 40283 at src/mongo/db/db.cpp 458
mongodb_1         | 2020-06-18T08:33:23.166+0000 I -        [initandlisten]
mongodb_1         |
mongodb_1         | ***aborting after fassert() failure
mongodb_1         |
mongodb_1         |
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=0c739dfdb2e0
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] db version v3.4.24
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] git version: 865b4f6a96d0f5425e39a18337105f33e8db504d
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] modules: none
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] build environment:
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongodb_1         | 2020-06-18T08:34:24.110+0000 I CONTROL  [initandlisten] options: { storage: { engine: "wiredTiger", journal: { enabled: false }, mmapv1: { smallFiles: true } } }
mongodb_1         | 2020-06-18T08:34:24.110+0000 W -        [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
mongodb_1         | 2020-06-18T08:34:24.114+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
mongodb_1         | 2020-06-18T08:34:24.114+0000 I STORAGE  [initandlisten]
mongodb_1         | 2020-06-18T08:34:24.114+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongodb_1         | 2020-06-18T08:34:24.114+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongodb_1         | 2020-06-18T08:34:24.114+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false),
mongodb_1         | 2020-06-18T08:34:24.185+0000 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredTiger
mongodb_1         | 2020-06-18T08:34:24.185+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:34:24.185+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongodb_1         | 2020-06-18T08:34:24.185+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongodb_1         | 2020-06-18T08:34:24.185+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:34:24.186+0000 F STORAGE  [initandlisten] BadValue: Invalid value for version, found 3.6, expected '3.4' or '3.2'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "3.6" }. See http://dochub.mongodb.org/core/3.4-feature-compatibility.
mongodb_1         | 2020-06-18T08:34:24.186+0000 I -        [initandlisten] Fatal Assertion 40283 at src/mongo/db/db.cpp 458
mongodb_1         | 2020-06-18T08:34:24.186+0000 I -        [initandlisten]
mongodb_1         |
mongodb_1         | ***aborting after fassert() failure
mongodb_1         |
mongodb_1         |
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=0c739dfdb2e0
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] db version v3.4.24
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] git version: 865b4f6a96d0f5425e39a18337105f33e8db504d
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] modules: none
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] build environment:
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongodb_1         | 2020-06-18T08:35:25.130+0000 I CONTROL  [initandlisten] options: { storage: { engine: "wiredTiger", journal: { enabled: false }, mmapv1: { smallFiles: true } } }
mongodb_1         | 2020-06-18T08:35:25.130+0000 W -        [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
mongodb_1         | 2020-06-18T08:35:25.134+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
mongodb_1         | 2020-06-18T08:35:25.134+0000 I STORAGE  [initandlisten]
mongodb_1         | 2020-06-18T08:35:25.134+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongodb_1         | 2020-06-18T08:35:25.134+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongodb_1         | 2020-06-18T08:35:25.134+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false),
mongodb_1         | 2020-06-18T08:35:25.213+0000 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredTiger
mongodb_1         | 2020-06-18T08:35:25.213+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:35:25.213+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongodb_1         | 2020-06-18T08:35:25.213+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongodb_1         | 2020-06-18T08:35:25.213+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:35:25.215+0000 F STORAGE  [initandlisten] BadValue: Invalid value for version, found 3.6, expected '3.4' or '3.2'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "3.6" }. See http://dochub.mongodb.org/core/3.4-feature-compatibility.
mongodb_1         | 2020-06-18T08:35:25.215+0000 I -        [initandlisten] Fatal Assertion 40283 at src/mongo/db/db.cpp 458
mongodb_1         | 2020-06-18T08:35:25.215+0000 I -        [initandlisten]
mongodb_1         |
mongodb_1         | ***aborting after fassert() failure
mongodb_1         |
mongodb_1         |
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=0c739dfdb2e0
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] db version v3.4.24
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] git version: 865b4f6a96d0f5425e39a18337105f33e8db504d
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] allocator: tcmalloc
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] modules: none
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] build environment:
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten]     distarch: x86_64
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten]     target_arch: x86_64
mongodb_1         | 2020-06-18T08:36:26.191+0000 I CONTROL  [initandlisten] options: { storage: { engine: "wiredTiger", journal: { enabled: false }, mmapv1: { smallFiles: true } } }
mongodb_1         | 2020-06-18T08:36:26.191+0000 W -        [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
mongodb_1         | 2020-06-18T08:36:26.195+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
mongodb_1         | 2020-06-18T08:36:26.195+0000 I STORAGE  [initandlisten]
mongodb_1         | 2020-06-18T08:36:26.195+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
mongodb_1         | 2020-06-18T08:36:26.195+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
mongodb_1         | 2020-06-18T08:36:26.195+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=3475M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),,log=(enabled=false),
mongodb_1         | 2020-06-18T08:36:26.264+0000 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredTiger
mongodb_1         | 2020-06-18T08:36:26.264+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:36:26.264+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
mongodb_1         | 2020-06-18T08:36:26.264+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
mongodb_1         | 2020-06-18T08:36:26.264+0000 I CONTROL  [initandlisten]
mongodb_1         | 2020-06-18T08:36:26.266+0000 F STORAGE  [initandlisten] BadValue: Invalid value for version, found 3.6, expected '3.4' or '3.2'. Contents of featureCompatibilityVersion document in admin.system.version: { _id: "featureCompatibilityVersion", version: "3.6" }. See http://dochub.mongodb.org/core/3.4-feature-compatibility.
mongodb_1         | 2020-06-18T08:36:26.266+0000 I -        [initandlisten] Fatal Assertion 40283 at src/mongo/db/db.cpp 458
mongodb_1         | 2020-06-18T08:36:26.266+0000 I -        [initandlisten]
mongodb_1         |
mongodb_1         | ***aborting after fassert() failure
mongodb_1         |
mongodb_1         |

[regis]

@CherieCAF What I need to debug this further is the output of the following command:

tutor local upgrade --from=ironwood

[CherieCAF]

@regis Sorry I thought I sent you that:

~$ tutor local upgrade --from=ironwood
You are about to upgrade your Open edX platform. It is strongly recommended to make a backup before upgrading. To do so, run:

    tutor local stop
    sudo rsync -avr "$(tutor config printroot)"/ /tmp/tutor-backup/

In case of problem, to restore your backup you will then have to run: sudo rsync -avr /tmp/tutor-backup/ "$(tutor config printroot)"/

Are you sure you want to continue? [Y/n]
=======================================
        Upgrading from Ironwood
=======================================
Environment generated in /home/ubuntu/.local/share/tutor/env
==============================================
        Stopping any existing platform
==============================================
docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local rm --stop --force
Stopping tutor_local_mongodb_1 ... done
Going to remove tutor_local_mongodb_1
Removing tutor_local_mongodb_1 ... done
===================================================
        Upgrading MongoDb from v3.2 to v3.4
===================================================
Environment generated in /home/ubuntu/.local/share/tutor/env
docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local up --remove-orphans -d mongodb
Creating tutor_local_mongodb_1 ... done
docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })
Error: Command failed with status 137: docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })

[regis]

It is quite strange that there are no more logs. Right after failing to run this command, please attempt to run:

docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval 'db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })'

Paste here the full output of this command.

[CherieCAF]

@regis The result is below:

~$ docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval 'db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })'
MongoDB shell version v3.6.18
connecting to: mongodb://127.0.0.1:27017/?gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("0ab8c7e6-67e0-4f77-be9d-ef5ec473b6e1") }
MongoDB server version: 3.6.18
{ "ok" : 1 }

[regis]

Ok. Then run:

docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval 'db.adminCommand({ setFeatureCompatibilityVersion: "3.6" })'

Then the upgrade will be done.

[NewFrontier]

@regis Thanks for guidance above. From a new install of Tutor 10.1.0 on AWS (Ubuntu 16.04, t2.large with 8 GB RAM and 100 GB storage), Ironwood ran correctly, but upgrading to Juniper seems to have failed after “Creating tutor_local_mongodb_1 … done”. Here is the output:

Error: Command failed with status 137: docker-compose -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.yml -f /home/ubuntu/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local exec mongodb mongo --eval db.adminCommand({ setFeatureCompatibilityVersion: "3.4" })

When I run FeatureCompatibilityVersion: “3.4”, as you recommended to @CherieCAF, this seems to have worked, but when running 3.6, I can’t get past this:

Error response from daemon: Container d5ee891031841a369bf21a3fc12720b0c9c3493879c2fc9b4d3b922a3b31208d is restarting, wait until the container is running

Thanks for any guidance you can provide.

[regis]

There seems to be some kind of misunderstanding. If you are running Tutor 10.1.0, then you are already running Juniper – not Ironwood. Thus, you do not need to run tutor local upgrade.

To summarize:

• v0 to v3 is Ironwood
• v10+ is Juniper
• v11+ (not yet released) will be Koa
  etc.

[ghofran24]

Hello , @shashi.kiran , Could you please guide me through this i cannot access Django Auth toolkit in the admin panel through my server , Any idea how to navigate to the exact path and create the same file , because i have the same issue , looking forward your reply