You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed the instruction on our Quick Start page to install a graph node on a Ubuntu 18.04 machine.
Here's the issues I encountered and their solutions (thanks for the help @Jannis).
docker, docker-compose, jq were not installed, resolved based on setup.sh output
setup.sh error (ERROR: No containers to start), resolved in this commit
The installation of graph-cli gave some errors. To fix them, I had to first install pkg-config and libsecret-1-dev, then run the command with sudo.
The step with graph init failed due to older Node version, resolved after upgrading it to v10.
The Node upgrade to v10 didn't actually remove the older version, which lead to further complications later (incompatible keytar version, node-gyp not compiling). We need Node.js version 10 (or 11) before installing graph-cli.
After removing both graph-cli versions, it was successfully reinstalled with sudo npm install -g @graphprotocol/graph-cli --unsafe (the unsafe flag is needed to avoid certain permission errors, see this)
Finally, yarn-create failed because the latest graph-node instance did not start up properly. When restarting the graph node, remove the old data with sudo rm -rf data/postgres.
After all this, the local graph node was up with the example subgraphs deployed and I was able to run graphQL queries against my local node.
The text was updated successfully, but these errors were encountered:
I followed the instruction on our Quick Start page to install a graph node on a Ubuntu 18.04 machine.
Here's the issues I encountered and their solutions (thanks for the help @Jannis).
docker, docker-compose, jq
were not installed, resolved based on setup.sh outputsetup.sh
error (ERROR: No containers to start), resolved in this commitgraph-cli
gave some errors. To fix them, I had to first installpkg-config
andlibsecret-1-dev
, then run the command with sudo.sudo npm install -g @graphprotocol/graph-cli --unsafe
(the unsafe flag is needed to avoid certain permission errors, see this)yarn-create
failed because the latestgraph-node
instance did not start up properly. When restarting the graph node, remove the old data withsudo rm -rf data/postgres
.After all this, the local graph node was up with the example subgraphs deployed and I was able to run graphQL queries against my local node.
The text was updated successfully, but these errors were encountered: