ERRO Connection to provider failed when connecting to TEVMOS

[vrde]

Do you want to request a feature or report a bug?

A bug I guess.

What is the current behavior?

I'm having troubles connecting the graph to EVMOS. What's weird is that one week ago I didn't have any issue, now I get a ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: tevmos-rpc-0 (full log below)

I tried to do a manual request with curl to https://eth.bd.evmos.dev:8545 and it works:

$ curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"net_version","params":[],"id":67}' https://eth.bd.evmos.dev:8545
{"jsonrpc":"2.0","id":67,"result":"9000"}

subgraph-graph-node-1  | Jun 30 09:35:54.770 INFO Graph Node version: 0.26.0 (2022-04-05)
subgraph-graph-node-1  | Jun 30 09:35:54.773 WARN GRAPH_POI_ACCESS_TOKEN not set; might leak POIs to the public via GraphQL
subgraph-graph-node-1  | Jun 30 09:35:54.774 INFO Generating configuration from command line arguments
subgraph-graph-node-1  | Jun 30 09:35:54.776 WARN No fork base URL specified, subgraph forking is disabled
subgraph-graph-node-1  | Jun 30 09:35:54.777 INFO Starting up
subgraph-graph-node-1  | Jun 30 09:35:54.777 INFO Trying IPFS node at: http://ipfs:5001/
subgraph-graph-node-1  | Jun 30 09:35:54.785 INFO Creating transport, capabilities: archive, traces, url: https://eth.bd.evmos.dev:8545, provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:35:54.792 INFO Successfully connected to IPFS node at: http://ipfs:5001/
subgraph-graph-node-1  | Jun 30 09:35:55.450 INFO Connecting to Postgres, weight: 1, conn_pool_size: 10, url: postgresql://graph-node:HIDDEN_PASSWORD@postgres:5432/graph-node, pool: main, shard: primary
subgraph-graph-node-1  | Jun 30 09:35:55.454 INFO Pool successfully connected to Postgres, pool: main, shard: primary, component: Store
subgraph-graph-node-1  | Jun 30 09:35:55.480 INFO Setting up fdw, pool: main, shard: primary, component: ConnectionPool
subgraph-graph-node-1  | Jun 30 09:35:55.498 INFO Running migrations, pool: main, shard: primary, component: ConnectionPool
subgraph-graph-node-1  | Jun 30 09:35:56.493 INFO Migrations finished, pool: main, shard: primary, component: ConnectionPool
subgraph-graph-node-1  | Jun 30 09:35:56.498 INFO Mapping primary, pool: main, shard: primary, component: ConnectionPool
subgraph-graph-node-1  | Jun 30 09:35:56.524 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:35:57.945 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #10) with result Err(RPC error: Error { code: ServerError(-32000), message: "height 1 is not available, lowest height is 709050", data: None }
subgraph-graph-node-1  | 
subgraph-graph-node-1  | Caused by:
subgraph-graph-node-1  |     Server error: height 1 is not available, lowest height is 709050), provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:35:58.241 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #11) with result Err(RPC error: Error { code: ServerError(-32000), message: "height 1 is not available, lowest height is 709050", data: None }
subgraph-graph-node-1  | 
subgraph-graph-node-1  | Caused by:
subgraph-graph-node-1  |     Server error: height 1 is not available, lowest height is 709050), provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:35:59.249 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #12) with result Err(RPC error: Error { code: ServerError(-32000), message: "height 1 is not available, lowest height is 709050", data: None }
subgraph-graph-node-1  | 
subgraph-graph-node-1  | Caused by:
subgraph-graph-node-1  |     Server error: height 1 is not available, lowest height is 709050), provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:36:01.768 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #13) with result Err(RPC error: Error { code: ServerError(-32000), message: "height 1 is not available, lowest height is 709050", data: None }
subgraph-graph-node-1  | 
subgraph-graph-node-1  | Caused by:
subgraph-graph-node-1  |     Server error: height 1 is not available, lowest height is 709050), provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:36:07.510 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #14) with result Err(RPC error: Error { code: ServerError(-32000), message: "height 1 is not available, lowest height is 709050", data: None }
subgraph-graph-node-1  | 
subgraph-graph-node-1  | Caused by:
subgraph-graph-node-1  |     Server error: height 1 is not available, lowest height is 709050), provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:36:16.802 WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(RPC error: Error { code: ServerError(-32000), message: "height 1 is not available, lowest height is 709050", data: None }
subgraph-graph-node-1  | 
subgraph-graph-node-1  | Caused by:
subgraph-graph-node-1  |     Server error: height 1 is not available, lowest height is 709050), provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:36:26.524 ERRO Connection to provider failed. Not using this provider, error: deadline has elapsed, provider: tevmos-rpc-0
subgraph-graph-node-1  | Jun 30 09:36:26.537 ERRO No store configured for Ethereum chain tevmos; ignoring this chain
subgraph-graph-node-1  | Jun 30 09:36:26.595 INFO Creating LoadManager in disabled mode, component: LoadManager
subgraph-graph-node-1  | Jun 30 09:36:26.597 INFO Starting firehose block ingestors with 0 chains []
subgraph-graph-node-1  | Jun 30 09:36:26.597 INFO Starting firehose block ingestors with 0 chains []
subgraph-graph-node-1  | Jun 30 09:36:26.598 INFO Starting job runner with 4 jobs, component: JobRunner
subgraph-graph-node-1  | Jun 30 09:36:26.602 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer
subgraph-graph-node-1  | Jun 30 09:36:26.605 INFO Starting GraphQL HTTP server at: http://localhost:8000, component: GraphQLServer
subgraph-graph-node-1  | Jun 30 09:36:26.608 INFO Starting index node server at: http://localhost:8030, component: IndexNodeServer
subgraph-graph-node-1  | Jun 30 09:36:26.608 INFO Starting metrics server at: http://localhost:8040, component: MetricsServer
subgraph-graph-node-1  | Jun 30 09:36:26.608 INFO Started all assigned subgraphs, node_id: default, count: 0, component: SubgraphRegistrar
subgraph-graph-node-1  | Jun 30 09:36:26.609 INFO Starting GraphQL WebSocket server at: ws://localhost:8001, component: SubscriptionServer

I'm running out of ideas, do you know anything I can try?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

I'm using docker compose, full config here https://github.com/TelediskoDAO/subgraph/tree/fix/7/evmos-compatibility

What is the expected behavior?

Connect to the TEVMOS JSONRPC endpoint.

[vrde]

This commit seems to fix the issue TelediskoDAO/subgraph@15a88ae

I'm still quite confused tbh. Don't know much about TEVMOS, but could it be that:

• The network TEVMOS was restarted at block 709050
• A new genesis file was generated. The genesis included a snapshot of the test network at block 709049 (the file is quite big, ~1.1GB https://github.com/evmos/testnets/tree/main/evmos_9000-4)
• I have to tell graph-node to start from that block height.

But this doesn't explain why my graph-node worked one week ago, while today when I restarted it I got the error.

[EdsonAlcala]

how do you tell the graph node to start from that block height?

[EdsonAlcala]

nevermind, I made it work with that image tag, thanks