Cairn: "relation report_schedule" does not exist

Hi,
I am also having problems with cairn. I use tutor Liliac (12.2.0 to be precise). We are trying to access cairn through data.(our lms host name).org but we keep getting an error 404 nginx and when we look the logs we see that there is a problem with the clickhouse container. I attach an image of the errors.

And I could successfully run tutor local run cairn-clickhouse cairn client

Hi @Andress! I moved this conversation to a different topic because the error is different. It seems like some of the superset migrations were not applied correctly. Are you quite sure that you running the right versions of Cairn and tutor? Please paste here the output of tutor --version and tutor plugins list.

tutor --version:
tutor, version 12.2.0

tutor plugins list:
:warning: You are running Tutor as root. This is strongly not recommended. If you are doing this in order to access the Docker daemon, you should instead add your user to the ’
docker’ group. (see Redirecting…)
cairn==12.0.13
custom_honor_courses==0.1.0
enable_custom_certs==0.1.0
license==12.0.2

Did you run tutor local quickstart? In particular the fact that some tables are missing seems to indicate that migrations did not run properly. Please attempt to run tutor local init --limit=cairn.

I did the tutor local quickstart serveral times and didn’ t work.
As for the tutor local init – limit=cairn:

⚠️  You are running Tutor as root. This is strongly not recommended. If you are doing this in order to access the Docker daemon, you should instead add your user to the '
docker' group. (see https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user)
Initialising all services...
Plugin cairn: running init for service cairn-clickhouse...
docker-compose -f /root/.local/share/tutor/env/local/docker-compose.yml -f /root/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /root/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm cairn-clickhouse-job sh -e -c cairn migrate --path=/etc/clickhouse-server/migrations.d
Creating tutor_local_cairn-clickhouse-job_run ... done
Applying migration 0001_create.sql...  SKIP
Applying migration 0002_grades.sql...  SKIP
Applying migration 0003_course_enrollments.sql...  SKIP
Applying migration 0004_video_views.sql...  SKIP
Applying migration 0005_course_blocks.sql...  SKIP
Applying migration 0006_course_block_completion.sql...  SKIP
Applying migration 0007_fix_video_segments.sql...  SKIP
Applying migration 0008_rename_openedx_tables.sql...  SKIP
Plugin cairn: running init for service cairn-superset...
docker-compose -f /root/.local/share/tutor/env/local/docker-compose.yml -f /root/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /root/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm cairn-superset-job sh -e -c # Apply migrations
superset db upgrade

# Create default roles and permissions
superset init

# Create/Update database with full access
superset set-database-uri --database-name=openedx --uri='clickhouse+native://openedx:******@cairn-clickhouse:9000/openedx'
Creating tutor_local_cairn-superset-job_run ... done
Loaded your LOCAL configuration at [/app/superset_config.py]
logging was configured successfully
2022-02-07 17:14:31,053:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
Loaded your LOCAL configuration at [/app/superset_config.py]
logging was configured successfully
2022-02-07 17:14:36,534:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Syncing role definition
Syncing Admin perms
Syncing Alpha perms
Syncing Gamma perms
Syncing granter perms
Syncing sql_lab perms
Fetching a set of all perms to lookup which ones are missing
Creating missing datasource permissions.
Creating missing database permissions.
Cleaning faulty perms
Loaded your LOCAL configuration at [/app/superset_config.py]
logging was configured successfully
2022-02-07 17:14:43,094:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Plugin cairn: running init for service cairn-openedx...
docker-compose -f /root/.local/share/tutor/env/local/docker-compose.yml -f /root/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /root/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm cairn-openedx-job sh -e -c python /openedx/scripts/importcoursedata.py
Creating tutor_local_cairn-openedx-job_run ... done
====================== course-v1:SEGITTUR+INTURPYR_1_FR+2020_02 Destinations Touristiques Intelligentes (DTI)
Inserting 79 items in course_blocks for course 'course-v1:SEGITTUR+INTURPYR_1_FR+2020_02'...
====================== course-v1:SEGITTUR+INTURPYR_1+2020_01 Destinos TurĂ­sticos Inteligentes (DTI)
Inserting 79 items in course_blocks for course 'course-v1:SEGITTUR+INTURPYR_1+2020_01'...
====================== course-v1:SITCA_SICA_GRINN_SEGITTUR+sm_DTI+202010 Semana de MetodologĂ­a Destinos TurĂ­sticos Inteligentes
Inserting 208 items in course_blocks for course 'course-v1:SITCA_SICA_GRINN_SEGITTUR+sm_DTI+202010'...
====================== course-v1:edX+DemoX+Demo_Course Curso de demostraciĂłn
Inserting 8 items in course_blocks for course 'course-v1:edX+DemoX+Demo_Course'...
====================== course-v1:SEGITTUR+SEG_00+2020_T4 Curso ejemplo David
Inserting 8 items in course_blocks for course 'course-v1:SEGITTUR+SEG_00+2020_T4'...
====================== course-v1:SEGITTUR+sm_DTI+2020-2021 I Curso online de iniciaciĂłn a los Destinos TurĂ­sticos Inteligentes
Inserting 259 items in course_blocks for course 'course-v1:SEGITTUR+sm_DTI+2020-2021'...
====================== course-v1:SEGITTUR+DTI_UNE_1+2021 Normas UNE como herramientas para la gestiĂłn de los DTI
Inserting 192 items in course_blocks for course 'course-v1:SEGITTUR+DTI_UNE_1+2021'...
====================== course-v1:SEGITTUR+ENERO+2022 Prueba
Inserting 8 items in course_blocks for course 'course-v1:SEGITTUR+ENERO+2022'...

And still I got:
Captura

What is the output of tutor local logs --tail=100 -f cairn-superset?

EDIT:

⚠️  You are running Tutor as root. This is strongly not recommended. If you are doing this in order to access the Docker daemon, you should instead add your user to the '
docker' group. (see https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user)
docker-compose -f /root/.local/share/tutor/env/local/docker-compose.yml -f /root/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local logs --follow --tail 100 cairn-superset
Attaching to tutor_local_cairn-superset_1
cairn-superset_1              | [2022-02-02 12:16:51 +0000] [7] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-02 12:16:51 +0000] [7] [INFO] Listening at: http://0.0.0.0:8000 (7)
cairn-superset_1              | [2022-02-02 12:16:51 +0000] [7] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-02 12:16:51 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | [2022-02-02 12:16:51 +0000] [11] [INFO] Booting worker with pid: 11
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-02 12:16:55,887:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-02 12:16:56,092:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 07:57:09 +0000] [6] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 07:57:09 +0000] [6] [INFO] Listening at: http://0.0.0.0:8000 (6)
cairn-superset_1              | [2022-02-04 07:57:09 +0000] [6] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 07:57:09 +0000] [9] [INFO] Booting worker with pid: 9
cairn-superset_1              | [2022-02-04 07:57:09 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 07:57:13,751:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 07:57:14,072:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 08:17:40 +0000] [7] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 08:17:40 +0000] [7] [INFO] Listening at: http://0.0.0.0:8000 (7)
cairn-superset_1              | [2022-02-04 08:17:40 +0000] [7] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 08:17:40 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | [2022-02-04 08:17:40 +0000] [11] [INFO] Booting worker with pid: 11
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:17:45,068:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:17:45,726:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 08:21:10 +0000] [8] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 08:21:10 +0000] [8] [INFO] Listening at: http://0.0.0.0:8000 (8)
cairn-superset_1              | [2022-02-04 08:21:10 +0000] [8] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 08:21:10 +0000] [11] [INFO] Booting worker with pid: 11
cairn-superset_1              | [2022-02-04 08:21:10 +0000] [12] [INFO] Booting worker with pid: 12
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:21:15,531:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:21:15,915:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 08:40:23 +0000] [6] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 08:40:23 +0000] [6] [INFO] Listening at: http://0.0.0.0:8000 (6)
cairn-superset_1              | [2022-02-04 08:40:23 +0000] [6] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 08:40:23 +0000] [9] [INFO] Booting worker with pid: 9
cairn-superset_1              | [2022-02-04 08:40:23 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:40:28,274:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:40:28,326:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 08:55:23 +0000] [7] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 08:55:23 +0000] [7] [INFO] Listening at: http://0.0.0.0:8000 (7)
cairn-superset_1              | [2022-02-04 08:55:23 +0000] [7] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 08:55:23 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | [2022-02-04 08:55:23 +0000] [11] [INFO] Booting worker with pid: 11
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:55:27,721:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 08:55:28,710:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 09:44:57 +0000] [7] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 09:44:57 +0000] [7] [INFO] Listening at: http://0.0.0.0:8000 (7)
cairn-superset_1              | [2022-02-04 09:44:57 +0000] [7] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 09:44:57 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | [2022-02-04 09:44:57 +0000] [11] [INFO] Booting worker with pid: 11
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 09:45:01,633:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 09:45:01,701:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | [2022-02-04 10:10:43 +0000] [7] [INFO] Starting gunicorn 20.0.4
cairn-superset_1              | [2022-02-04 10:10:43 +0000] [7] [INFO] Listening at: http://0.0.0.0:8000 (7)
cairn-superset_1              | [2022-02-04 10:10:43 +0000] [7] [INFO] Using worker: gthread
cairn-superset_1              | [2022-02-04 10:10:43 +0000] [10] [INFO] Booting worker with pid: 10
cairn-superset_1              | [2022-02-04 10:10:43 +0000] [11] [INFO] Booting worker with pid: 11
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 10:10:51,016:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
cairn-superset_1              | logging was configured successfully
cairn-superset_1              | 2022-02-04 10:10:51,063:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>

This issue was solved offline. The DNS records were configured incorrectly.

1 Like