Error indexing subgraph QmYtkrAwgNZSc5jwMSRiR29eCSPXXhf9jfqpCgr8NvBhq6

[vmatskiv]

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Syncing of the subgraph QmYtkrAwgNZSc5jwMSRiR29eCSPXXhf9jfqpCgr8NvBhq6 delivers the following error:

Possible reorg detected, retrying, id: QmYtkrAwgNZSc5jwMSRiR29eCSPXXhf9jfqpCgr8NvBhq6, error: Failed to process trigger in block #6810753 (1e9e467b6cbd8405a77b6daaf4c41f72e2fec3030fdd2ec5095149d8cbffddd3), transaction 77bb84773d7752a289da78a90a7c7348ac3d619a3d87c89dd9ead83dba34fdeb: Ethereum node returned an error when calling function "totalSupply" of contract "BEP20": RPC error: Error { code: ServerError(-32000), message: "missing trie node 269781a60357b29d4f9d347fc218d75a969d58ff255086a4dd5dabb7a528ae3c (path )", data: None } wasm backtrace: 0: 0x14ae - !<wasm function 64> 1: 0x16bb - !<wasm function 79> 2: 0x16da - !<wasm function 80> 3: 0x1b3b - !<wasm function 95>

network: bsc
Deployed to hosted service

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

What is the expected behavior?
Index the subgraph to chain head

[schmidsi]

We are currently experiencing issues with the BSC archive nodes that leads to problems with indexing subgraphs. You can subscribe to updates here: https://status.thegraph.com. We are working to find a solution.

[vmatskiv]

I am still experiencing the issue above. Do you know any time estimation when it might be fixed?

[schmidsi]

Not at the moment.

[vmatskiv]

Maybe there are other solutions? Some workarounds to suggest?

[schmidsi]

If the contract that you try to index is deployed after block 7796111 or you just start to index events after this block, it should work.

[vmatskiv]

In my case contract was deployed in 6808737 block :(

[schmidsi]

Try to set startBlock in your subgraph.yml to 7796111 anyways. Sometimes, not all historical data is needed. You can still change to 6808737 as soon as we fixed this.

[longhoangwkm]

we also got this error on Testnet

[schmidsi]

@longhoangwkm Is this on chapel? Would you mind sharing the URL of your subgraph with us?

[longhoangwkm]

@schmidsi Morning, yes that is chapel network. Here are my project URL https://api.thegraph.com/subgraphs/id/QmSkoQriAAToUoW4quYGMBa8EdypaDbepxfuhi4WqD4hq6, many thanks

[schmidsi]

Hey, we have a better endpoint now for Binance that should support also blocks before 7796111. Can you please deploy a version of your subgraph that starts before that block and see, if that error is still around?

[songhobby]

same error for goerli testnet
schema QmaJz4Sd7TRHZ3Vim5fbAwF6HPLcZseY28GhY2t8h6mM11
handler QmesWEoniL4kKe3nDUbfKNCMnTobVSxffrxTigBvdD6ro7

error message

Possible reorg detected, retrying, error: failed to process trigger: block #7845583 (0xa2ed…c38f), transaction e6a6875da83204b62e65ac85eb4ec876d112aa87190183e345848312614a1507: Ethereum node returned an error when calling function "GOVERNANCE_TOKEN_ID" of contract "Governance": RPC error: Error { code: ServerError(-32000), message: "missing trie node 9e91ab6633cf595451f1042ac2a4111fc3c1291bdfd01823bbe9215f4ef78c84 (path ) <nil>", data: None }

Some hint as to how this happened.
My old indexer which has been running since block #7836808 (before #7845583) has no such error, but when I start a new indexer (after ##7845583) the error shows.