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

Block returned null response #410

Closed
tobutridaz opened this issue Nov 29, 2018 · 1 comment
Closed

Block returned null response #410

tobutridaz opened this issue Nov 29, 2018 · 1 comment

Comments

@tobutridaz
Copy link

Can't connect to Parity node with the below block returning null. Killing the chain and re-syncing did not help.

Block 6039710 returned null response. This is usually an issue with a partially sync'd parity warp node. See: openethereum/parity-ethereum#7411

@tobutridaz tobutridaz changed the title Block returned nul response Block returned null response Nov 29, 2018
@adrake33
Copy link
Contributor

@tobutridaz This is a known issue with Parity when using warp-sync. Missing blocks and logs should eventually become available, but it will take some time. More info can be found here: https://github.com/AugurProject/augur-app#parity-and-warp-sync.

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

No branches or pull requests

2 participants