metaverse-vm
metaverse-vm copied to clipboard
502 Error when syncing new graph
Currently, the mainnet endpoint has an availability issue when we deploy a new graph, it takes a long amount of time to sync since getting new blocks often results in ~# 13 attempts per block range due to 502 error.
The endpoint used is: https://vm.mvs.org/mainnet_rpc/
Related on EVM calls. Pls describe the details here @inodelisia
@inodelisia @betachen
Here's an old log that I took a while ago, the error is similar on the mainnet
@Corfucinas Please send me a list of RPC eth_ calls that are used most often on the graph node.
@betachen @inodelisia
While doing some debugging I found out the graph node crashed about 7k blocks ago, I've restarted it but got the following log messages
Let me know exactly what you need and the node/graph commands to provide you a more detailed explanation if required.