stakesquid / graphprotocol-mainnet-docker Goto Github PK

Hello,

I'm a newbie to this environment and technology. Pls help on the below issue.

When I am trying to follow this setup procedure, I've encountered some set of issues..

Resolving one by one, And currently I'm blocked at this error..

When I am running ./runagora --help (or) ./runqlog --help below is the error output.

error: could not find Cargo.toml in /code or any parent directory
./runagora: line 10: /home/ubuntu/graphprotocol-mainnet-docker/agora/target/release/agora: No such file or directory

Is Cargo.toml missing?? How do we get it? It seems some manifest file.

Note:- Pls check the 7th line in runagora file, Check if bash -c '(cd /code/agora; cargo build --release)' need to be changed to bash -c '(cd /code; cargo build --release)'

~/graphprotocol-mainnet-docker$ bash start

Step 15/20 : RUN npm i -g @graphprotocol/[email protected] --registry https://registry.npmjs.org/ --unsafe-perm=true
 ---> Running in fcb844d20863
npm WARN deprecated [email protected]: No longer supported. Use the multi-stream support in the latest core Pino
npm WARN deprecated [email protected]: This module renamed to process-warning
/home/graph/.npm-global/bin/graph-indexer -> /home/graph/.npm-global/lib/node_modules/@graphprotocol/indexer-cli/bin/graph-indexer

> @graphprotocol/[email protected] install /home/graph/.npm-global/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model
> node-pre-gyp install --fallback-to-build=false --update-binary || yarn build-release

node-pre-gyp ERR! install response status 502 Bad Gateway on https://github.com/graphprotocol/agora/releases/download/v0.1.14/graphprotocol-agora-plugin-v0.1.14-node-v83-linux-x64.tar.gz
node-pre-gyp ERR! install error
node-pre-gyp ERR! stack Error: response status 502 Bad Gateway on https://github.com/graphprotocol/agora/releases/download/v0.1.14/graphprotocol-agora-plugin-v0.1.14-node-v83-linux-x64.tar.gz
node-pre-gyp ERR! stack     at /home/graph/.npm-global/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@mapbox/node-pre-gyp/lib/install.js:67:15
node-pre-gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:95:5)
node-pre-gyp ERR! System Linux 5.4.0-99-generic
node-pre-gyp ERR! command "/usr/bin/node" "/home/graph/.npm-global/lib/node_modules/@graphprotocol/indexer-cli/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build=false" "--update-binary"
node-pre-gyp ERR! cwd /home/graph/.npm-global/lib/node_modules/@graphprotocol/indexer-cli/node_modules/@graphprotocol/cost-model
node-pre-gyp ERR! node -v v14.20.0
node-pre-gyp ERR! node-pre-gyp -v v1.0.9
node-pre-gyp ERR! not ok
response status 502 Bad Gateway on https://github.com/graphprotocol/agora/releases/download/v0.1.14/graphprotocol-agora-plugin-v0.1.14-node-v83-linux-x64.tar.gz
sh: 1: yarn: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @graphprotocol/[email protected] install: `node-pre-gyp install --fallback-to-build=false --update-binary || yarn build-release`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @graphprotocol/[email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/graph/.npm/_logs/2022-09-06T22_56_56_430Z-debug.log
ERROR: Service 'cli' failed to build: The command '/bin/sh -c npm i -g @graphprotocol/[email protected] --registry https://registry.npmjs.org/ --unsafe-perm=true' returned a non-zero code: 1

While this has already been reported through the discord I thought I'd capture it here as well.

When deploying the latest version of the graphprotocol-mainnet-docker the indexer-agent and indexer-service continued to restart.

To fix this I changed the image: ghcr.io/graphprotocol/indexer-service:v0.19.2 to be image: ghcr.io/graphprotocol/indexer-service:v0.19.1 which came up fine.

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

1. Duplicate "GRAPH_LOG_QUERY_TIMING: gql' in compose-graphnode.yml (Line 93)
   

   graphprotocol-mainnet-docker/compose-graphnode.yml

   Line 93 in de34035

   GRAPH_LOG_QUERY_TIMING: gql

2. Duplicate "labels" in compose-monitoring.yml (Line 161)
   

   graphprotocol-mainnet-docker/compose-monitoring.yml

   Line 161 in de34035

   org.label-schema.group: "monitoring"

Currently, there is a single point of failure with https://ipfs.network.thegraph.com/ipfs/. Indexers should run their own node and peer to https://ipfs.network.thegraph.com/ipfs/ to increase resilience.