Receiving 503 from elasticsearch when creating forum

[sean]

Hi,

I am receiving a 503 response from elasticsearch when creating the forum, as follows:

Initialising forum...
docker-compose -f /home/sean/.local/share/tutor/env/local/docker-compose.yml -f /home/sean/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /home/sean/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm forum-job sh -e -c bundle exec rake search:initialize
bundle exec rake search:rebuild_indices
Creating tutor_local_forum-job_run ... done
Waiting for mongodb/elasticsearch...
2022/02/01 02:20:53 Waiting for: tcp://mongodb:27017
2022/02/01 02:20:53 Waiting for: http://elasticsearch:9200
2022/02/01 02:20:53 Connected to tcp://mongodb:27017
2022/02/01 02:20:53 Received 503 from http://elasticsearch:9200. Sleeping 5s
2022/02/01 02:20:58 Received 503 from http://elasticsearch:9200. Sleeping 5s
...
2022/02/01 02:30:43 Received 503 from http://elasticsearch:9200. Sleeping 5s
2022/02/01 02:30:48 Received 503 from http://elasticsearch:9200. Sleeping 5s
2022/02/01 02:30:53 Timeout after 10m0s waiting on dependencies to become available: [tcp://mongodb:27017 http://elasticsearch:9200]
ERROR: 1
Error: Command failed with status 1: docker-compose -f /home/sean/.local/share/tutor/env/local/docker-compose.yml -f /home/sean/.local/share/tutor/env/local/docker-compose.prod.yml --project-name tutor_local -f /home/sean/.local/share/tutor/env/local/docker-compose.jobs.yml run --rm forum-job sh -e -c bundle exec rake search:initialize
bundle exec rake search:rebuild_indices

This problem occurs on a virtual server, running ubuntu 20.04, behind a corporate proxy for both prod and dev installations of tutor 12.2.0. As a test, I was able to successfully install dev on a local ubuntu machine.

Could this be a proxy issue which needs to be set?

Any help would be appreciated.

Thanks,
Sean

[regis]

What are the logs coming out of the elasticsearch container?

tutor local logs --tail=100 -f elasticsearch

This will give you a clue of what is going on.

There is a stackoverflow question pointing to a possible multicast error. That would be pretty serious, because it would mean that the elasticsearch container is arbitrarily connecting with other instances on your network…