fforbeck
commented
2 years ago Use the release-v1.0.6 branch. That's the branch that works with Tribute UI, and contains all the instructions for you to run the graph node under the docker/ folder.
https://discord.com/channels/854328535929192498/854808091165196318/923196992363053086
Hello! I'd love to clone and build my own idea with on this framework. I've tried to follow the documentation. When I've tried to docker-compose up(Starting the services) I've got this error.
Starting docker_ipfs_1 ... done Starting docker_postgres_1 ... done Starting docker_graph-node_1 ... done Attaching to docker_postgres_1, docker_ipfs_1, docker_graph-node_1 postgres_1 | postgres_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization postgres_1 | postgres_1 | 2021-12-22 01:26:10.428 UTC [1] LOG: starting PostgreSQL 14.1 (Debian 14.1-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit ipfs_1 | Changing user to ipfs ipfs_1 | ipfs version 0.4.23 postgres_1 | 2021-12-22 01:26:10.429 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 ipfs_1 | Found IPFS fs-repo at /data/ipfs ipfs_1 | Initializing daemon... ipfs_1 | go-ipfs version: 0.4.23-6ce9a35 ipfs_1 | Repo version: 7 ipfs_1 | System version: amd64/linux ipfs_1 | Golang version: go1.12.16 postgres_1 | 2021-12-22 01:26:10.429 UTC [1] LOG: listening on IPv6 address "::", port 5432 postgres_1 | 2021-12-22 01:26:10.434 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" postgres_1 | 2021-12-22 01:26:10.438 UTC [24] LOG: database system was interrupted; last known up at 2021-12-22 01:04:07 UTC postgres_1 | 2021-12-22 01:26:10.449 UTC [24] LOG: database system was not properly shut down; automatic recovery in progress postgres_1 | 2021-12-22 01:26:10.452 UTC [24] LOG: redo starts at 0/1AE1540 postgres_1 | 2021-12-22 01:26:10.452 UTC [24] LOG: invalid record length at 0/1AE1628: wanted 24, got 0 postgres_1 | 2021-12-22 01:26:10.452 UTC [24] LOG: redo done at 0/1AE15F0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s postgres_1 | 2021-12-22 01:26:10.460 UTC [1] LOG: database system is ready to accept connections ipfs_1 | Swarm listening on /ip4/127.0.0.1/tcp/4001 ipfs_1 | Swarm listening on /ip4/172.18.0.2/tcp/4001 ipfs_1 | Swarm listening on /p2p-circuit ipfs_1 | Swarm announcing /ip4/127.0.0.1/tcp/4001 ipfs_1 | Swarm announcing /ip4/172.18.0.2/tcp/4001 ipfs_1 | API server listening on /ip4/0.0.0.0/tcp/5001 ipfs_1 | WebUI: http://0.0.0.0:5001/webui ipfs_1 | Gateway (readonly) server listening on /ip4/0.0.0.0/tcp/8080 ipfs_1 | Daemon is ready graph-node_1 | Dec 22 01:26:27.125 INFO Graph Node version: 0.25.0 (2021-12-01) graph-node_1 | Dec 22 01:26:27.135 INFO Generating configuration from command line arguments graph-node_1 | Dec 22 01:26:27.135 INFO Starting up graph-node_1 | Dec 22 01:26:27.136 INFO Trying IPFS node at: http://ipfs:5001/ graph-node_1 | Dec 22 01:26:27.143 INFO Creating transport, capabilities: archive, traces, url: http://host.docker.internal:7545, provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:27.148 INFO Successfully connected to IPFS node at: http://ipfs:5001/ graph-node_1 | Dec 22 01:26:29.175 INFO Connecting to Postgres, weight: 1, conn_pool_size: 10, url: postgresql://graph-node:HIDDEN_PASSWORD@postgres:5432/graph-node, pool: main, shard: primary graph-node_1 | Dec 22 01:26:29.178 INFO Pool successfully connected to Postgres, pool: main, shard: primary, component: Store graph-node_1 | Dec 22 01:26:29.194 INFO Setting up fdw, pool: main, shard: primary, component: ConnectionPool graph-node_1 | Dec 22 01:26:29.200 INFO Running migrations, pool: main, shard: primary, component: ConnectionPool graph-node_1 | Dec 22 01:26:29.202 INFO Migrations finished, pool: main, shard: primary, component: ConnectionPool graph-node_1 | Dec 22 01:26:29.203 INFO Mapping primary, pool: main, shard: primary, component: ConnectionPool graph-node_1 | Dec 22 01:26:29.254 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:49.730 WARN Trying again after net_version RPC call failed (attempt #10) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:50.229 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:52.050 WARN Trying again after net_version RPC call failed (attempt #11) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:52.621 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:54.540 WARN Trying again after net_version RPC call failed (attempt #12) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:55.622 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:58.187 WARN Trying again after net_version RPC call failed (attempt #13) with result Err(Transport error: Error(Connect, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })), provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:59.256 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: mainnet-rpc-0 graph-node_1 | Dec 22 01:26:59.259 ERRO No store configured for Ethereum chain mainnet; ignoring this chain graph-node_1 | Dec 22 01:26:59.340 INFO Creating LoadManager in disabled mode, component: LoadManager graph-node_1 | Dec 22 01:26:59.340 INFO Starting job runner with 3 jobs, component: JobRunner graph-node_1 | Dec 22 01:26:59.345 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer graph-node_1 | Dec 22 01:26:59.346 INFO Started all assigned subgraphs, node_id: default, count: 0, component: SubgraphRegistrar graph-node_1 | Dec 22 01:26:59.370 INFO Starting GraphQL HTTP server at: http://localhost:8000, component: GraphQLServer graph-node_1 | Dec 22 01:26:59.374 INFO Starting index node server at: http://localhost:8030, component: IndexNodeServer graph-node_1 | Dec 22 01:26:59.375 INFO Starting metrics server at: http://localhost:8040, component: MetricsServer graph-node_1 | Dec 22 01:26:59.375 INFO Starting GraphQL WebSocket server at: ws://localhost:8001, component: SubscriptionServer graph-node_1 | [2021-12-22T01:26:59Z WARN web3::transports::http] Error resuming asynchronous request: Err(Transport("Error(Connect, Os { code: 111, kind: ConnectionRefused, message: \"Connection refused\" })"))Please help me how can i resolve this issue. Please attention that I'm new on graph node. thanks