stakesquid / graphprotocol-testnet-docker Goto Github PK

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.

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

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

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?

Hey team,

We've noticed that you're referencing a subgraph deployed on The Graph's hosted service in this repository. Just a heads-up: after June 12th, hosted service subgraph endpoints will no longer be available as the offering is being deprecated.

If you are the subgraph owner or maintainer, it's time to upgrade your subgraph to the network. This ensures everything keeps running smoothly and you get access to all the latest features and improvements. Here is a quick guide with all the upgrade steps.

If you're not the subgraph owner or maintainer, check Graph Explorer to see if the subgraph development team has already upgraded to the network. If you don’t find an upgraded subgraph, a friendly nudge to the subgraph development team would be greatly appreciated—it's a quick process that benefits everyone. Here's the upgrade guide with all the necessary steps for the subgraph development team.

Once the subgraph is upgraded to the network, you can create an API key and updated query URL in Subgraph Studio then update this repository to query from the new endpoint, https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>

Need more support or have more questions? Feel free to reach out to [email protected]. We're here to help!

Cheers,

Paka