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

panic with "wrong Block.Header.AppHash" when a restarted node calling AddLog #674

Closed
KamiD opened this issue Dec 29, 2020 · 0 comments · Fixed by #676
Closed

panic with "wrong Block.Header.AppHash" when a restarted node calling AddLog #674

KamiD opened this issue Dec 29, 2020 · 0 comments · Fixed by #676

Comments

@KamiD
Copy link

KamiD commented Dec 29, 2020

System info: [Include Ethermint commit, operating system name, and other relevant details]

Steps to reproduce:
Reproduce every time

  1. [First Step]
    Deploy 4 node with ethermintd
  2. [Second Step]
    Publish some contract and call it on ethermint
  3. [and so on...]
    Restart one of nodes
    Expected behavior:
    Node runs well
    Actual behavior:
    panic "wrong Block.Header.AppHash" happened
    Additional info:
    here is reference of csdb.logSize, if it not store to db, every new node will set it to zero, but for running node, csdb.logSize may not be zero, that's a difference between keep running node and restart node
    log.Index = csdb.logSize
@KamiD KamiD changed the title csdb.logSize need to store persistently csdb.logSize need to store lasting Dec 29, 2020
@KamiD KamiD changed the title csdb.logSize need to store lasting csdb.logSize need to store to db Dec 29, 2020
@KamiD KamiD changed the title csdb.logSize need to store to db panic with "wrong Block.Header.AppHash" when a restarted node calling AddLog Dec 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant