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

Sync stalls #4367

Closed
gavofyork opened this issue Dec 11, 2019 · 6 comments
Closed

Sync stalls #4367

gavofyork opened this issue Dec 11, 2019 · 6 comments
Assignees
Labels
U1-asap No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@gavofyork
Copy link
Member

This happens quite often for me. One peer; sync stalls after a while. Target keeps increasing as expected.

2019-12-12 04:12:27 Syncing  0.0 bps, target=#183034 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 19.3kiB/s ⬆ 12.9kiB/s
2019-12-12 04:12:32 Syncing  0.0 bps, target=#183035 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 23.5kiB/s ⬆ 11.7kiB/s
2019-12-12 04:12:37 Syncing  0.0 bps, target=#183035 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 13.7kiB/s ⬆ 12.2kiB/s
2019-12-12 04:12:42 Syncing  0.0 bps, target=#183036 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 21.1kiB/s ⬆ 12.0kiB/s
2019-12-12 04:12:47 Syncing  0.0 bps, target=#183037 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 13.0kiB/s ⬆ 11.9kiB/s
2019-12-12 04:12:52 Syncing  0.0 bps, target=#183038 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 15.2kiB/s ⬆ 11.3kiB/s
2019-12-12 04:12:57 Syncing  0.0 bps, target=#183039 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 20.9kiB/s ⬆ 9.0kiB/s
2019-12-12 04:13:02 Syncing  0.0 bps, target=#183040 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 14.4kiB/s ⬆ 12.9kiB/s
2019-12-12 04:13:07 Syncing  0.0 bps, target=#183040 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 17.2kiB/s ⬆ 10.5kiB/s
2019-12-12 04:13:12 Syncing  0.0 bps, target=#183041 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 12.8kiB/s ⬆ 11.7kiB/s
2019-12-12 04:13:17 Syncing  0.0 bps, target=#183042 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 11.2kiB/s ⬆ 11.6kiB/s
2019-12-12 04:13:22 Syncing  0.0 bps, target=#183043 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 12.8kiB/s ⬆ 11.0kiB/s
2019-12-12 04:13:26 Discovered new external address for our node: /ip4/10.0.0.212/tcp/30333/p2p/QmbpAg35kF82nmyH93keRtUofdRrguzGvkDd9yr28b19Bq
2019-12-12 04:13:27 Syncing  0.0 bps, target=#183044 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 18.1kiB/s ⬆ 11.3kiB/s
2019-12-12 04:13:32 Syncing  0.0 bps, target=#183045 (1 peers), best: #182916 (0x6848…2034), finalized #182916 (0x6848…2034), ⬇ 17.4kiB/s ⬆ 10.5kiB/s
@gavofyork gavofyork added F0-consensus ☠️ U1-asap No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Dec 11, 2019
@gavofyork gavofyork added this to the 2.0 milestone Dec 11, 2019
@marcio-diaz
Copy link
Contributor

Maybe useful. I wonder if the problem is some ancestor query on import.

2019-12-11 22:43:27 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 36041989
2019-12-11 22:43:27 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 34663915
2019-12-11 22:43:27 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 37290108
2019-12-11 22:43:27 New epoch 262 launching at block 0x9b8b…7410 (block slot 262650881 >= start slot 262650879).
2019-12-11 22:43:27 Next epoch starts at slot 262651479
2019-12-11 22:43:29 Syncing  7.1 bps, target=#184496 (21 peers), best: #152702 (0x212a…1f97), finalized #152576 (0x1f7d…086e), ⬇ 35.3kiB/s ⬆ 5.4kiB/s
2019-12-11 22:43:34 Syncing  0.0 bps, target=#184497 (22 peers), best: #152702 (0x212a…1f97), finalized #152576 (0x1f7d…086e), ⬇ 14.4kiB/s ⬆ 4.7kiB/s
2019-12-11 22:43:39 Syncing  0.0 bps, target=#184497 (23 peers), best: #152702 (0x212a…1f97), finalized #152576 (0x1f7d…086e), ⬇ 29.6kiB/s ⬆ 5.3kiB/s
2019-12-11 22:43:44 Syncing  0.0 bps, target=#184498 (22 peers), best: #152702 (0x212a…1f97), finalized #152576 (0x1f7d…086e), ⬇ 17.1kiB/s ⬆ 3.9kiB/s
2019-12-11 22:43:49 Syncing  0.0 bps, target=#184499 (22 peers), best: #152702 (0x212a…1f97), finalized #152576 (0x1f7d…086e), ⬇ 8.2kiB/s ⬆ 4.5kiB/s
2019-12-11 22:43:52 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 25017717384
2019-12-11 22:43:52 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 32950516
2019-12-11 22:43:52 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 48264110

@gavofyork
Copy link
Member Author

@arkpar one to look into.

@gavofyork gavofyork modified the milestones: 2.0, 2.1 Dec 16, 2019
@arkpar
Copy link
Member

arkpar commented Dec 16, 2019

Are there any sync logs? Also it looks like there's only one peer connection. Was that peer behaving normally?

2019-12-11 22:43:52 TRACING: DEBUG sc_consensus_babe: import_block, line: 886, time: 25017717384

Is that 25 seconds?

@marcio-diaz
Copy link
Contributor

Is that 25 seconds?

I think so, sorry I didn't have more traces at that point.

@philipstanislaus
Copy link
Contributor

@gavofyork is this still an issue? Trying to determine if there are any red flags to launching Centrifuge's mainnet shortly. Thanks!

@arkpar
Copy link
Member

arkpar commented Feb 26, 2020

Pretty sure this has been fixed a while ago

@arkpar arkpar closed this as completed Feb 26, 2020
@gnunicorn gnunicorn modified the milestones: 2.1, Polkadot Mar 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
U1-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

5 participants