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" & "required historical state unavailable" in logs #2219

Closed
jmozah opened this issue Jun 22, 2019 · 4 comments
Closed

"Missing trie node" & "required historical state unavailable" in logs #2219

jmozah opened this issue Jun 22, 2019 · 4 comments
Labels
question Further information is requested waiting on feedback Waiting for original opener to respond if bug is fixed

Comments

@jmozah
Copy link

jmozah commented Jun 22, 2019

Describe your issue here.

I am getting the following logs in my blockscout log

1)  0x0000000000000000000000000000000000000000@�: (-32000) missing trie node 8b1604e0d19d9be9a94cab027e74134e674bccdbf8d6a3f09a23abe52fd356fa (path )

2) 2019-06-22T05:39:04.900 application=indexer fetcher=internal_transaction count=10 error_count=10 [error] failed to fetch internal transactions for transactions: [%{code: -32000, data: %{block_number: 7674025, transaction_hash: "0x4a5f7b470ace011dd3800c3519adf3d3d58816f1b31c96bcbd76dc809dec80ac", transaction_index: 4}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7674028, transaction_hash: "0xcb89e8312469976780f556929afb21f408b38f648ffef5f6e04f8500aabab8d3", transaction_index: 0}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7674025, transaction_hash: "0xe0fbd34ed56f25935d48ea4da269c6509184b5aaedb4c385c9e317a7f23625f3", transaction_index: 1}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7674025, transaction_hash: "0xe2be90e6b21c6e54d137ca6dc1a135b0d429a1778dab2a46fbab6bbb83b1df52", transaction_index: 0}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7674025, transaction_hash: "0xf72853a088c50ff75412d1b3e1ace80f5314505f0de092d535ca3415e2c4d0b6", transaction_index: 2}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7673871, transaction_hash: "0xeacad111c0341de78ece611de756f596e2c0db00939a530d0282aa0b9ecd5b32", transaction_index: 0}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7669300, transaction_hash: "0x225359069f70f360dcaad52660f87f924a3a11403777ecc5ec45872d9f66eaba", transaction_index: 0}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7673711, transaction_hash: "0x096f23eab9ffa476678188539f17d06c143f21d283f37b5a8a1b5d2a66846097", transaction_index: 0}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7673679, transaction_hash: "0x267db3f84c462902bfd26be508fcb2663edf68232f15f72e05e6a7e253bd091f", transaction_index: 2}, message: "required historical state unavailable (reexec=128)"}, %{code: -32000, data: %{block_number: 7673679, transaction_hash: "0x65db74f474b70370c6fe0c401b40f8e0f64a91d922c069f624e76c12be2c2bbb", transaction_index: 1}, message: "required historical state unavailable (reexec=128)"}]

Environment

  • Elixir & Erlang/OTP versions (elixir -version):
    Erlang/OTP 20 [erts-9.2] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:10] [kernel-poll:false]
  • Operating System:
    Ubuntu 18

My geth start command looks like

geth --networkid "235813" --verbosity=4 --rpc --rpcaddr "0.0.0.0" --rpcapi "admin,db,eth,miner,web3,net,personal,txpool,clique,debug" --rpccorsdomain "*" --ws --wsaddr 0.0.0.0 --wsport 8546 --wsorigins "*" --wsapi "admin,debug,db,eth,miner,web3,net,personal,txpool" --syncmode="full" --nodiscover --gcmode "archive"
@igorbarinov
Copy link
Sponsor Member

Hi,
is your node fully synced?

@jmozah
Copy link
Author

jmozah commented Jun 22, 2019 via email

@ayrat555
Copy link
Contributor

@jmozah It's a known issue. Your node should be an archive node

@vbaranov
Copy link
Member

vbaranov commented Jul 5, 2019

@jmozah was your issue resolved after resyncing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested waiting on feedback Waiting for original opener to respond if bug is fixed
Projects
None yet
Development

No branches or pull requests

4 participants