search

graphprotocol / support

Community support for the Hosted Service of The Graph
https://thegraph.com/
10 stars 3 forks source link

Problems with subgraph indexing on BSC #82

Closed oikos1 closed 3 years ago

oikos1 commented 3 years ago

Hello guys,

One of our most critical subgraphs has been consistently failing for the past 48 hours. Here's the error message I am seeing:

Possible reorg detected, retrying, id: QmS12QfxjxE1fG6KTomwLCuk9Doq1n4XMw9twLXidzqT7Z, error: failed to process trigger: block #9853252 (0x38c0…282a), transaction d3c45b624cdb0d8f51fbf8cd2cd08d774fde380a8c6a5250ec0e3ef40ccb8691: Ethereum node returned an error when calling function "rateForCurrency" of contract "ExchangeRates": Transport error: Unexpected response status code: 503 Service Unavailable wasm backtrace: 0: 0x22fe - <unknown>!~lib/@graphprotocol/graph-ts/chain/ethereum/ethereum.SmartContract#call 1: 0x234b - <unknown>!generated/ExchangeRates/ExchangeRates/ExchangeRates#rateForCurrency 2: 0x2533 - <unknown>!src/rates-mapping/handleAnswerUpdated. Trying again after eth_call RPC call failed (attempt graphprotocol/graph-node#10) with result Err(Web3Error(Transport("Unexpected response status code: 503 Service Unavailable"))), block_hash: 0x38c0f5e22103b2366d16608d41d07280794cddd3146216d50578061727fa282a, block_number: 9853252

This subgraph was working fine and suddenly started presenting this issue. Any idea what is causing this and is there any ETA for resolution? Thank you so much in advance.

Albert

azf20 commented 3 years ago

Hi @oikos1, thanks for reporting. This was related to an issue with our BSC node provider - @pranavdaa is this issue still open?

oikos1 commented 3 years ago

This issue was resolved. Closing. Thank you guys!