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.

Sign up for GitHub

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

Jump to bottom

Geth crashes, “missing trie node”, rlp: expected List #19070

Closed
pawelsome opened this issue Feb 14, 2019 · 2 comments
Closed

Geth crashes, “missing trie node”, rlp: expected List #19070

pawelsome opened this issue Feb 14, 2019 · 2 comments

Comments

@pawelsome
Copy link

pawelsome commented Feb 14, 2019 •
edited
Loading

Hi,
I am struggling with failing geth with my Dapp. I got an error like this:

Web3

UnhandledPromiseRejectionWarning: Error: Returned error: missing trie node 3b78b9f0a935d03af6f70ac4173f718e46b62573d4363ff5839f41a6df4f2429 (path 020f06020608)
Geth:

INFO [02-07|06:51:18.668] Imported new chain segment               blocks=1 txs=247 mgas=7.993  elapsed=145.425ms mgasps=54.961  number=7186894 hash=bfbcdc…0a5b69 age=1m12s cache=268.00mB
panic: node 93e9e8033c6f4bdc391443e9d3446e41e41c175e0e2e353924b40b74d41d2933: decode error: rlp: expected List 
goroutine 56011323 [running]:
github.com/ethereum/go-ethereum/trie.mustDecodeNode(0xc66da87ba0, 0x20, 0x20, 0xc4bd8300e0, 0x68, 0x68, 0x3ed6, 0x0, 0x0)
/build/ethereum-fSsX30/ethereum-

It happens randomly at least once a month, and i have to do resync every time.

What may cause this problem?

I need a stable solution.

I use Geth 1.8.22.
@pawelsome pawelsome changed the title Geth crashes, “missing trie node”, weird hashes Geth crashes, “missing trie node” Feb 15, 2019
@pawelsome pawelsome changed the title Geth crashes, “missing trie node” Geth crashes, “missing trie node”, rlp: expected List Feb 15, 2019
@karalabe
Copy link
Member

We've found and fixed a data race in our trie node read cache. We're not sure whether that was the culprit or not, but it's definitely a possible source of error. It's not yet on master, but will hopefully be soon.

@karalabe karalabe mentioned this issue Feb 18, 2019
Merged
@karalabe
Copy link
Member

Closing this as potentially fixed. Please reopen if you still see it with v1.8.23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@karalabe @pawelsome