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

Parity PoA authorities are not syncing #7441

Closed
fatihATtargens opened this issue Jan 3, 2018 · 7 comments
Closed

Parity PoA authorities are not syncing #7441

fatihATtargens opened this issue Jan 3, 2018 · 7 comments
Assignees
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@fatihATtargens
Copy link

fatihATtargens commented Jan 3, 2018

Authority sync not work correct.

I'm running a private parity poa network with verion 1.7.7 stable.
The following issue I get:

Stage 1 block verification failed for b4e8…ee34: Block(DifficultyOutOfBounds(OutOfBounds { min: None, max: Some(340282366920938463463374607431768211455), found: 340282366920938463463374607431768211456 }))

and after that the two authorities are not able to sync again correct.
In the following screenshot you can see that on of the authorities imports higher blocknumbers and then back again lower blocknumber (the lower numbers are the same like at the other authority and the hash values are correct too). But it never stops to do add first the wrong blocknumber and then the correct one. So my app doesn't work correct!
"wrong authority"
image

"working authority"
image

All other none authority nodes got the same blocknumber as in the second pic.

Thank you in advance for some help!

Best

Fatih

@debris
Copy link
Collaborator

debris commented Jan 3, 2018

@tomusdrw can you confirm that this is fixed in #7434 ?

@fatihATtargens
Copy link
Author

Sorry but i'm not able to change the version of parity.

@5chdn 5chdn added M4-core ⛓ Core client code / Rust. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Jan 3, 2018
@5chdn 5chdn added this to the 1.9 milestone Jan 3, 2018
@tomusdrw tomusdrw added F2-bug 🐞 The client fails to follow expected behavior. and removed Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. labels Jan 4, 2018
@tomusdrw tomusdrw self-assigned this Jan 4, 2018
@tomusdrw
Copy link
Collaborator

tomusdrw commented Jan 4, 2018

@debris It's a similar bug that was fixed in previous release, but the cause is a bit different. We have identified it and working on a fix.

@tomusdrw tomusdrw added B0-patch P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Jan 4, 2018
@fatihATtargens
Copy link
Author

If you know the bug and the causes is there a workaround for it?

@tomusdrw
Copy link
Collaborator

tomusdrw commented Jan 4, 2018

@fatihATtargens Restart both nodes and they should reorganize (you can also use --reserved-peers option to make sure they sync with the correct chain). Also make sure that the time on both authorities are properly synchronized.

@fatihATtargens
Copy link
Author

@tomusdrw thanks a lot! I'll give that a try and let you know if that works!

@fatihATtargens
Copy link
Author

@tomusdrw the workaround doesn't work! The same error occures.

@fatihATtargens fatihATtargens changed the title Parity PoA athoritues are not syncing Parity PoA authorities are not syncing Jan 5, 2018
@5chdn 5chdn mentioned this issue Jan 5, 2018
64 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Development

No branches or pull requests

4 participants