Docker-compose up fails with Elastic Search error

Camunda 8 Topics Discussion & Questions
1

Hi,
I have been using the OOTB Zeebe operate with “docker-compose up” for over a week successfully, restarting it now and then. (mac environment)
This afternoon, I shut it down, did some other stuff and tried restarting it. I get this error:
elasticsearch_1 | org.elasticsearch.action.search.SearchPhaseExecutionException: all shards failed
and a 503 after that.
I tried:

  • emptying out docker of all containers and images
  • downloading zeebe operate again
  • rerunning docker-compose up
    But still the same error. My docker environment looks like this:
    docker images
    REPOSITORY TAG IMAGE ID CREATED SIZE
    camunda/zeebe 0.25.1 52ea7df34fc1 2 months ago 331MB
    camunda/operate 0.25.0 e4bb5fb1d939 2 months ago 371MB
    docker.elastic.co/elasticsearch/elasticsearch-oss 6.7.1 c91b419ac445 21 months ago 682MB

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a5183e52372b camunda/zeebe:0.25.1 “tini – /usr/local/…” 2 minutes ago Up About a minute 0.0.0.0:9600->9600/tcp, 0.0.0.0:26500->26500/tcp, 26501-26502/tcp operate_zeebe_1
3fe4855b1e71 docker.elastic.co/elasticsearch/elasticsearch-oss:6.7.1 “/usr/local/bin/dock…” 12 days ago Up About a minute 0.0.0.0:9200->9200/tcp, 9300/tcp operate_elasticsearch_1

Can anyone comment on what might be wrong?
Regards,
Ken

2

This from the docker-compose README helped. Apparently something was corrupted in the data.

“In case you want to clean also the persistent data use the following command instead:
docker-compose down -v”

3

How do you shut it down?

4

Ctrl C. I have it running in the foreground.

5

Maybe this might corrupt the data? You could start it with:

docker-compose up -d && docker-compose logs -f

To stop it, you’d hit Ctrl-C and then run:

docker-compose down
6

Ok. I will try that.

7