Problem in testnet node installation

Questions & Feedback Questions
1

Hi there, I tried to install a test node in my local pc, I have completed test GRT approve and stake on staking contract. Then I followed the instruction here to install indexer agent, service and node with docker:
https://github.com/StakeSquid/graphprotocol-testnet-docker

I went to this step : bash start
All look good:

Successfully built 09b43e8017fa
Successfully tagged graphprotocol-testnet-docker_cli:latest
Recreating cli … done
Recreating alertmanager … done
Recreating index-node-1 … done
Recreating pushgateway … done
Recreating nodeexporter … done
Recreating cadvisor … done
Recreating postgres2 … done
Recreating query-node-0 … done
Recreating index-node-0 … done
Recreating prometheus … done
Recreating nginx-ssl … done
Recreating postgres … done
Recreating nginx-proxy … done
Recreating grafana … done
Recreating vector-node … done
Recreating indexer-agent … done
Recreating indexer-service … done

However, after I tried this:

/shell cli
graph indexer rules get all

It complains：
[Network] request to http://indexer-agent:8000/ failed, reason: getaddrinfo ENOTFOUND indexer-agent

Any idea how to trouble shot this? and what’s going on?

Thanks.

2

Check the containers are all running and not restarting on a crash with docker container list
Check the logs for the indexer-agent container docker logs --follow --tail 100 indexer-agent

1 Like
3

Thanks so much. Now it is working.

BTW, how to make my test node visible in explorer?

4

In addition, now the graph command is working.
But I still have lots of questions. e.g.
Grafana (visualize metrics) http://<host-ip>:3000
But the link doesn’t work for me. So how to check metrics UI?

I found graph doc is still limited. E.g. how to set cost model, if there are some examples ?

5

I have the same issue that it seems everything has come up but the :9090, :9091, :9093, and :3000 ports aren’t serving anything up on either the host IP or through the domain that was set up for the dashboard.mydomain.tld.

6

The way I was able to overcome this issue was to change the version of the indexer-agent that was running.

To do this you need to run

nano docker-compose.yml

and then update the following line to which ever indexer agent version you want to run (below I’ve updated this from v0.18.1 to v0.18.2

image: ghcr.io/graphprotocol/indexer-agent:v0.18.2

Afterwards you need to rebuild the indexer-agent containter by running

bash start --force-recreate indexer-agent

With that run, I’m now seeing everything running perfectly on docker ps and the right response when running the .shell/cli + graph indexer rules get all

1 Like