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

Missing trie node error from 0x00... account tx's [geth/clique] #1593

Closed
brianmcmichael opened this issue Mar 18, 2019 · 8 comments · Fixed by #1614
Assignees

Comments

@brianmcmichael
Copy link
Contributor

@brianmcmichael brianmcmichael commented Mar 18, 2019

Describe your issue here.

Environment

  • Elixir & Erlang/OTP versions (elixir -version): 1.8.1
  • Operating System: Ubuntu 18.04

Steps to reproduce

Tell us how to reproduce this issue. ❤️ if you can push up a branch to your fork with a regression test we can run to reproduce locally.

Running a Clique POA network on geth. Updated from a previous version and updated dependencies and dropped/created/migrated db. Errors appear to stem from tx's eminating from the 0x000... account.

Expected behaviour

No errors

Actual behaviour

Logs are filled with errors.

2019-03-18T19:11:43.550 application=indexer fetcher=coin_balance count=500 error_count=500 [error] failed to fetch: 0x0000000000000000000000000000000000000000@🋏: (-32000) missing trie node d871c28827dfe1ddeb882ba6ec6b72084e2d148dda287f161b1c4402571f899e (path )
0x0000000000000000000000000000000000000000@𠙳: (-32000) missing trie node d871c28827dfe1ddeb882ba6ec6b72084e2d148dda287f161b1c4402571f899e (path )
0x0000000000000000000000000000000000000000@𚶟: (-32000) missing trie node 802a4a63849b492306e1a62510f3898ec0eddab974adf12cd58011484687db29 (path )
0x0000000000000000000000000000000000000000@𚙆: (-32000) missing trie node 802a4a63849b492306e1a62510f3898ec0eddab974adf12cd58011484687db29 (path )
...
..
.
0x0000000000000000000000000000000 (truncated)
@nrg-jeff

This comment has been minimized.

Copy link

@nrg-jeff nrg-jeff commented Mar 18, 2019

I am also having this error running on geth. Ping me if you found a solution @brianmcmichael ?

@brianmcmichael

This comment has been minimized.

Copy link
Contributor Author

@brianmcmichael brianmcmichael commented Mar 19, 2019

No solution. I filled up a 200GB disk in the past 24 hours with all of the logs though. As of right now I've resorted to cron jobs trimming the log files every hour.

@igorbarinov

This comment has been minimized.

Copy link
Member

@igorbarinov igorbarinov commented Mar 19, 2019

We are looking into the problem

@nrg-jeff

This comment has been minimized.

Copy link

@nrg-jeff nrg-jeff commented Mar 20, 2019

awesome thanks for the update

@ghost ghost removed the in progress label Mar 21, 2019
@nrg-jeff

This comment has been minimized.

Copy link

@nrg-jeff nrg-jeff commented Apr 15, 2019

I am still receiving this error (using a private ethereum network). Any ideas? @igorbarinov

@ayrat555

This comment has been minimized.

Copy link
Member

@ayrat555 ayrat555 commented Apr 16, 2019

@nrg-jeff are you using the latest version of blockscout? is your geth node archive node?

@nrg-jeff

This comment has been minimized.

Copy link

@nrg-jeff nrg-jeff commented Apr 16, 2019

@ayrat555 Yes, I am using the latest version of blockscout. My geth node is default (--gcmode full), not archive. Should I use --gcmode archive? Thanks!

@ayrat555

This comment has been minimized.

Copy link
Member

@ayrat555 ayrat555 commented Apr 17, 2019

@nrg-jeff yes you should resync your node with --gcmode=archive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.