stakesquid/graphprotocol-testnet-docker

Graph Protocol Testnet Docker Guide by StakeSquid. Easy to use, one-stop gateway into the Web3 universe via The Graph.

graphprotocol-testnet-docker's Issues

typo in INDEXER_AGENT_REBATE_CLAIM_THRESHOLD

It is set to INDEXER_AGENT_REBATE_CLAIM_TRESHOLD with 'H' missing:
That's the reason for ignoring it from .env file

https://github.com/StakeSquid/graphprotocol-testnet-docker/blob/master/compose-all-services.yml#L225

Grafana not working

Hi there,
I am having the following issue. In a fresh set-up Grafana is not working, the container starts-up but when I try to open Grafana, it does not load up at all with an error 'connection refused'. Here are my grafana container logs:

I tried to re-download grafana image and then re-deploy it but still having the same issue. Any ideas how to fix it?

docker-compose.yml / start file - variable mismatch

Incorrect variable called for mainnet eth node in compose yaml

start file calls ETHEREUM_RPC whereas MAINNET_RPC is being called e.g. for configuring the graph nodes. Replace MAINNET_RPC for ETHEREUM_RPC in compose fixes the issue

graph indexer status - Error fetching status

I've followed the steps outlined in the readme and the video tutorial https://www.youtube.com/watch?v=bSr8L1GPk54

Everything seems to be okay but when I run graph indexer status I'm getting the message
Error fetching status information: [Network] request to http://indexer-agent:8000/ failed, reason: getaddrinfo EAI_AGAIN indexer-agent

When running docker ps I've noticed there are a few containers that aren't starting up.

CONTAINER ID   IMAGE                                           COMMAND                  CREATED          STATUS                          PORTS                                                                      NAMES
4522fe3eb6d9   ghcr.io/graphprotocol/indexer-service:v0.18.1   "docker-entrypoint.s…"   17 minutes ago   Restarting (1) 47 seconds ago                                                                              indexer-service
1fa4666a00ce   ghcr.io/graphprotocol/indexer-agent:v0.18.1     "node dist/index.js …"   17 minutes ago   Restarting (1) 34 seconds ago                                                                              indexer-agent
44cee8f9efd2   graphprotocol/graph-node:v0.24.2                "/bin/sh -c start"       17 minutes ago   Up 17 minutes                   8000-8001/tcp, 8020/tcp, 8030/tcp, 8040/tcp                                query-node-0
ca7b6bc43ae3   graphprotocol/graph-node:v0.24.2                "/bin/sh -c start"       17 minutes ago   Up 17 minutes                   8000-8001/tcp, 8020/tcp, 8030/tcp, 8040/tcp                                index-node-2
4422a3f0a40f   graphprotocol-testnet-docker_cli                "cat"                    17 minutes ago   Up 17 minutes                                                                                              cli
2890ee5b7655   graphprotocol/graph-node:v0.24.2                "/bin/sh -c start"       17 minutes ago   Restarting (1) 26 seconds ago                                                                              index-node-0
fcb3847517ad   graphprotocol/graph-node:v0.24.2                "/bin/sh -c start"       17 minutes ago   Restarting (1) 25 seconds ago                                                                              index-node-1

The indexer-service and graph-node both don't seem to be starting up, and issuing no ports as a result (which is why I assume the indexer status is failing.