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

Some sync nodes can't get latest finalize. #2187

Closed
gguoss opened this issue Apr 3, 2019 · 5 comments
Closed

Some sync nodes can't get latest finalize. #2187

gguoss opened this issue Apr 3, 2019 · 5 comments
Labels
I3-bug The node fails to follow expected behavior. J2-unconfirmed Issue might be valid, but it’s not yet known.
Milestone

Comments

@gguoss
Copy link
Contributor

gguoss commented Apr 3, 2019

110661554274466_ pic_hd

https://telemetry.polkadot.io/#/ChainX%20V0.9.7
Some sync nodes cannot go to the latest finalize height, and the restart node can be restored to normal.

@gguoss
Copy link
Contributor Author

gguoss commented Apr 3, 2019

2019-04-03 17:07:40.140.140 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)
2019-04-03 17:07:40.140.140 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)
2019-04-03 17:07:40.140.140 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)
2019-04-03 17:07:40.140.140 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)
2019-04-03 17:07:40.243.243 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)
2019-04-03 17:07:40.335.335 tokio-runtime-worker-5 TRACE afg Polling round 39, state = State { prevote_ghost: None, finalized: None, estimate: None, completable: false }, step = Some(Prevoted)
2019-04-03 17:07:40.485.486 libp2p-11 INFO sync Dropping PeerId("QmUNmpe6UoSpE3LhkL9knqTogbPDn7Lsg1EQErPDkUJzgL") because it timed out
2019-04-03 17:07:40.485.486 libp2p-11 INFO sync Dropping PeerId("QmSdAB3UGwEDuaL3QvTW4BCCAV7b5oL72TyTCxe35sU917") because it timed out
2019-04-03 17:07:40.485.486 libp2p-11 INFO sync Dropping PeerId("QmQ7vca7aum3q1toVPUf8T6SiUPdhFuMPpyJgYAxeoUXtf") because it timed out
2019-04-03 17:07:40.485.486 libp2p-11 INFO sync Dropping PeerId("QmRZ2URFsxZ2uCjr4cdrP9QvHr8qQg5gXMBhLsVchgNi4S") because it timed out
2019-04-03 17:07:40.485.486 libp2p-11 INFO sync Dropping PeerId("QmeCNS75ZRHAUsAUtH6DjcaxVFWwkBaT5KQtx91WvAh9i5") because it timed out
2019-04-03 17:07:40.567.568 ImportQueue DEBUG afg Bad signature on message from 88b30de22179ee81ddde0c042872b4003e7bbd30b32f2abd9caa4c07354d0a10 (5F9wZR5K...)
2019-04-03 17:07:40.567.568 libp2p-4 INFO sync Banning PeerId("QmPhjiJ8uGKWcM17TSiZnSDYQCynEGW7XiNbh51UP5UhT8") because "Invalid justification provided for #0x6eaf…a286"
2019-04-03 17:07:40.567.568 libp2p-4 WARN sync Banning a node is a deprecated mechanism that should be removed
2019-04-03 17:07:40.600.600 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)
2019-04-03 17:07:40.704.705 Protocol TRACE afg Expired: Message in invalid future set 158 (ours 133)

@andresilva
Copy link
Contributor

What commit of substrate is the ChainX client targeting?

@rphmeier rphmeier added I3-bug The node fails to follow expected behavior. J2-unconfirmed Issue might be valid, but it’s not yet known. labels Apr 3, 2019
@rphmeier rphmeier modified the milestones: 1.x series, 1.1 Apr 3, 2019
@gguoss
Copy link
Contributor Author

gguoss commented Apr 4, 2019

What commit of substrate is the ChainX client targeting?

5a463bb

@gguoss
Copy link
Contributor Author

gguoss commented Apr 17, 2019

Some authority nodes also can't get latest finalize.
image

@gavofyork
Copy link
Member

I presume this is sorted now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
I3-bug The node fails to follow expected behavior. J2-unconfirmed Issue might be valid, but it’s not yet known.
Projects
None yet
Development

No branches or pull requests

4 participants