Skip to content

Latest commit

 

History

History
54 lines (32 loc) · 1.6 KB

trouble_shooting.md

File metadata and controls

54 lines (32 loc) · 1.6 KB

Wika Network ETL trouble shooting

Docker engine memory

If you experience one or more of the processes exiting, you may need to increase you docker resources.

For example, in docker desktop you might see this:

If that is the case, you might not be allocating enough resources to your docker image.

To change this in docker desktop, navigate to the settings icon and the click resrouces. There you will see a menu that looks like below image. Increase the CPU and Memory until your image runs without exiting. The below settings were sufficient in testing on a macbook air m1.

Elastic Search failing

In some linux OS, Elastic Search fails because of the rights on its data folder. (pelias/docker#33)

Running sudo chown -R 1000:1000 .data/es fixes this issue.

graphql-engine and or subquery-node containers won't start

  1. docker-compose down everything
  2. delete the .data/postgres folder
  3. reset the startBlock in the project.yml file to a recent a block number
  4. docker-compose up again

graphql-engine Container is unhealthy

If you encounter this error:

ERROR: for graphql-engine  Container "824d8fc05142" is unhealthy.

You can fix it by:

  1. shutting down the docker infrastructure & clean up
$ docker rm 824d8fc05142 # replace with the correct container id
$ docker-compose down

  1. update the startBlock property to the recent block height

  2. start the docker infrastructure again

$ docker-compose up