Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Block import failed for #9163373 #9803

Closed
teodor-pripoae opened this issue Oct 23, 2018 · 7 comments
Closed

Block import failed for #9163373 #9803

teodor-pripoae opened this issue Oct 23, 2018 · 7 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Milestone

Comments

@teodor-pripoae
Copy link

teodor-pripoae commented Oct 23, 2018

  • Parity Ethereum version: v2.0.8-stable-ef8f95e-2018101
  • Operating system: MacOS
  • Installation: one-line installer
  • Fully synchronized: no
  • Network: kovan
  • Restarted: yes

Hi,

My node was fully synced a few hours ago. It got an error syncing block 9163373 and then even if I restart it, it gets the same error.

Block import failed for #9163373 (0xe1ac…4087)
Error: Error(Trie(InvalidStateRoot(0x554206b64fa84679f4b7e359a0bc14182c4382aa2b5ee45cf50df60517d62594)), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })
truffle(kovan-rpc)> web3.eth.syncing
false
truffle(kovan-rpc)> web3.eth.getBlock('latest').number
9163371
@teodor-pripoae
Copy link
Author

I have enough disk space left (about 7gb).

@jam10o-new jam10o-new added the F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. label Oct 24, 2018
@jam10o-new
Copy link
Contributor

Hey, answered in gitter, solution is to use warp-barrier, no-warp, or kill db and resync.
Please create a new issue regarding the "Your chain specification contains one or more hard forks which are required to be on by default. Please remove these forks and start your chain again: eip155Transition." issue if it is persisting.

@5chdn 5chdn added this to the 2.2 milestone Oct 29, 2018
@5chdn
Copy link
Contributor

5chdn commented Dec 25, 2018

@joshua-mir was this ever created?

@jam10o-new
Copy link
Contributor

I don't believe it was - but wouldn't the issue be addressed by #9972 @5chdn ?

@5chdn
Copy link
Contributor

5chdn commented Dec 25, 2018

No, I get this with the latest master for the Rinkeby chain spec which activates EIP-155 on block 0x3 - not sure what to do with that message.

@jam10o-new
Copy link
Contributor

Poking around, this should only complain if you are trying to seal the genesis block, so shouldn't be a showstopper for connecting to rinkeby itself IIUC?

@5chdn
Copy link
Contributor

5chdn commented Dec 26, 2018

No, it stops once you are synced past block 3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

3 participants