Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

502 Error when syncing new graph #17

Open
Corfucinas opened this issue Mar 31, 2021 · 5 comments
Open

502 Error when syncing new graph #17

Corfucinas opened this issue Mar 31, 2021 · 5 comments
Assignees
Labels

Comments

@Corfucinas
Copy link

Corfucinas commented Mar 31, 2021

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/

@betachen
Copy link
Member

betachen commented Mar 31, 2021

Related on EVM calls. Pls describe the details here @inodelisia

@Corfucinas
Copy link
Author

@inodelisia @betachen

Here's an old log that I took a while ago, the error is similar on the mainnet

image

@inodelisia
Copy link
Contributor

inodelisia commented Apr 1, 2021

@Corfucinas Please send me a list of RPC eth_ calls that are used most often on the graph node.

@Corfucinas
Copy link
Author

@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

image

@Corfucinas
Copy link
Author

Let me know exactly what you need and the node/graph commands to provide you a more detailed explanation if required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants