The search index CardSearch does not exist... about mpc-autofill

[fklemme]

Haven't seen this one before. When you are using the Docker setup, all cards are searched and updated before the web server becomes available. Do you see any error messages there? Check docker-compose logs django if you started detached. Usually, a manual python3 manage.py update_database should not be required.

[patrickschwehm]

those are the only logs for docker-compose logs django:

Attaching to docker_django_1
django_1         | Waiting for Postgres...
django_1         | Waiting for Elasticsearch...
django_1         | Operations to perform:
django_1         |   Apply all migrations: admin, auth, blog, cardpicker, contenttypes, sessions
django_1         | Running migrations:
django_1         |   No migrations to apply.
django_1         | Starting cron daemon for background updates...
django_1         | [2021-10-01 08:14:40 +0000] [1] [INFO] Starting gunicorn 20.1.0
django_1         | [2021-10-01 08:14:40 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
django_1         | [2021-10-01 08:14:40 +0000] [1] [INFO] Using worker: sync
django_1         | [2021-10-01 08:14:40 +0000] [23] [INFO] Booting worker with pid: 23
django_1         | /usr/local/lib/python3.8/dist-packages/elasticsearch/connection/base.py:208: ElasticsearchWarning: Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.14/security-minimal-setup.html to enable security.
django_1         |   warnings.warn(message, category=ElasticsearchWarning)
django_1         | [2021-10-01 10:29:56 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:23)
django_1         | [2021-10-01 10:29:56 +0000] [23] [INFO] Worker exiting (pid: 23)
django_1         | [2021-10-01 10:29:56 +0000] [29] [INFO] Booting worker with pid: 29
django_1         | [2021-10-01 10:54:17 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:29)
django_1         | [2021-10-01 10:54:17 +0000] [29] [INFO] Worker exiting (pid: 29)
django_1         | [2021-10-01 10:54:18 +0000] [35] [INFO] Booting worker with pid: 35

[fklemme]

Looks like the first setup was already done here... Can you show the output of a fresh start with docker-compose up --build --force-recreate?

[patrickschwehm]

This is the output from docker-compose logs django after running docker-compose up --build -force-recreate:

django_1         | Waiting for Postgres...
django_1         | Waiting for Elasticsearch...
django_1         | Still waiting for Elasticsearch...
django_1         | Operations to perform:
django_1         |   Apply all migrations: admin, auth, blog, cardpicker, contenttypes, sessions
django_1         | Running migrations:
django_1         |   No migrations to apply.
django_1         | Starting cron daemon for background updates...
django_1         | [2021-10-01 12:21:40 +0000] [1] [INFO] Starting gunicorn 20.1.0
django_1         | [2021-10-01 12:21:40 +0000] [1] [INFO] Listening at: http://0.0.0.0:8000 (1)
django_1         | [2021-10-01 12:21:40 +0000] [1] [INFO] Using worker: sync
django_1         | [2021-10-01 12:21:40 +0000] [25] [INFO] Booting worker with pid: 25

[fklemme]

My bad, I though that --force-recreate will also implicitly make sure that volumes are recreated. But seems they are persistent (have to fix this in the Readme).
If you are not using Docker for anything else, please use one of the docker_clean_all scripts to purge your setup and force a clean start. Then docker-compose up should rebuild everything and the logs should also contain more information.