-
Notifications
You must be signed in to change notification settings - Fork 1.7k
UnknownUncleParent while syncing #6761
Comments
The consensus is broken. Picture of our disaster 😄 http://testnet.oracles.org:3000/ |
Nodes resynced by a magic way. The consensus is not broken. Thanks to @rstormsf to resolve issues on his node (no disk space). |
Cool! |
Please reopen this issue as the same error reproduces on v1.8.1.
I've attached a log with Could this be a possible scenario: one of validators starts a second node and sends transactions to it. If current block is his to seal but transaction didn't have time to propagate to the rest of the network, will this cause the network to split? Anyway please review the logs, this is just my guess. |
UPD: Now the error does not reproduce on 165001 block, but rather on 175001 block. One more UPD on the following morning: Now it's 180001 block:
|
@5chdn Afri, could we reopen the issue? |
I see a pattern here. Are you changing your chain config? |
No, each time I just completely delete parity data folder on my local machine and start If you'd like to try yourself, here's my node.toml, my peers.txt, our network's spec.json This time it's 185002 block. |
The same problem happened on Kovan? #6947 |
have you got this problem on Kovan guys? |
We are not using Uncles in AuRa, right? |
#7006 should address this |
@5chdn Afri, any estimates when it'll be merged? |
Should be fixed in 1.7.10 and 1.8.4 |
Hello
We have a private PoA network with validation via a contract. Yesterday we had a network issue and some nodes ran out of sync for a period of time. Later that day they all synced and network seemed to be working fine. However, today clients can't sync with it, the following error appears in logs:
More logs here
Could someone help figure out what might be the origin of this error? Using web3 I can find block 880003, its uncles, their parent blocks... so why are they unknown? what does it mean?
The text was updated successfully, but these errors were encountered: