-
Notifications
You must be signed in to change notification settings - Fork 1.7k
parity not syncing #7308
Comments
i tried to run parity -- wrap Fidaas-MacBook-Pro:~ Fidaa$ parity --warp |
I'm having the same problem with version 1.8. Been looking for syncing problems here and fixes but haven't found any. Been almost 2 days now. |
I can confirm I had the same issue, my node was not syncing at after updating to latest stable (1.7.10), I upgraded to beta (1.8.4) and it syncs .. |
Same problem here, I'm around block 4,230,000, it says it is syncing, but it is very very slow and it seems like it would need an eternity to catch up the latest block (currently 4,765,000)... |
Before filing a new issue, please provide the following information.
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
i am getting stuck with sync on block #4,370,001 which is 2 month old.... getting only 1 peer, and it's showing fully synchronized while it's not....below some logs
here is some logs
12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Skipping peer 28, force=false, td=Some(607677241438600), our td=1196950396094581414946, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Skipping peer 12, force=false, td=Some(388872301937210927397), our td=1196950396094581414946, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Skipping busy peer 5
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Syncing with peers: 3 active, 3 confirmed, 3 total
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync 5 <- GetBlockBodies: 1 entries starting from Some(acc61682d268b0df9b243849fd6c7aaa1dae8dedac0666aea73212607840d292), set = NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Syncing with peer 5, force=false, td=None, our td=1196950396094581414946, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Considering peer 5, force=false, td=None, our td=1196950396094581414946, latest=acc6…d292, have_latest=false, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Imported 0 of 0
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Drained 0 blocks, new head :Some(174e01a245f7db9b350a14afc149ec19f66067248299d624e7e73e9731e4b5de)
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync Inserted 1 headers
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync New header: acc61682d268b0df9b243849fd6c7aaa1dae8dedac0666aea73212607840d292
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync New head acc6…d292
[12/17/2017, 10:40:19 AM] IO Worker #0 TRACE sync 5 -> BlockHeaders (1 entries), state = NewBlocks, set = NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Skipping peer 28, force=false, td=Some(607677241438600), our td=1196950396094581414946, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Skipping peer 12, force=false, td=Some(388872301937210927397), our td=1196950396094581414946, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Skipping busy peer 5
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Syncing with peers: 3 active, 3 confirmed, 3 total
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync 5 <- GetBlockHeaders: 128 entries starting from acc6…d292, set = NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Syncing with peer 5, force=true, td=None, our td=1196950396094581414946, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Considering peer 5, force=true, td=None, our td=1196950396094581414946, latest=acc6…d292, have_latest=false, state=NewBlocks
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync Downloading blocks for new hashes
[12/17/2017, 10:40:19 AM] IO Worker #1 TRACE sync New unknown block hash acc61682
The text was updated successfully, but these errors were encountered: