Parity-ethereum: parity not syncing

Created on 17 Dec 2017  ·  5Comments  ·  Source: openethereum/parity-ethereum

_Before filing a new issue, please provide the following information._

I'm running:

  • Which Parity version?: 1.7
  • Which operating system?: MacOS /
  • How installed?: via installer
  • Are you fully synchronized?: no
  • Did you try to restart the node?: yes

_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

M2-installer 📲 Z1-question 🙋‍♀️

Most helpful comment

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)...
I tried to clean up the cache, empty the db folder, and tried this with the stable 1.7.10 and with the beta 1.8.4 with the same result.

All 5 comments

i tried to run parity -- wrap

Fidaas-MacBook-Pro:~ Fidaa$ parity --warp
Loading config file from /Users/Fidaa/Library/Application Support/io.parity.ethereum/config.toml
2017-12-17 11:00:01 main INFO parity::run Starting Parity/v1.7.2-beta-9f47909-20170918/x86_64-macos/rustc1.19.0
2017-12-17 11:00:01 main INFO parity::run Keys path /Users/Fidaa/Library/Application Support/io.parity.ethereum/keys/Foundation
2017-12-17 11:00:01 main INFO parity::run DB path /Users/Fidaa/Library/Application Support/io.parity.ethereum/chains/ethereum/db/906a34e69aec8c0d
2017-12-17 11:00:01 main INFO parity::run Path to dapps /Users/Fidaa/Library/Application Support/io.parity.ethereum/dapps
2017-12-17 11:00:01 main INFO parity::run State DB configuration: fast
2017-12-17 11:00:01 main INFO parity::run Operating mode: active
2017-12-17 11:00:01 main INFO ethcore::service Configured for Foundation using Ethash engine
2017-12-17 11:00:02 hyper-client INFO miner Updated conversion rate to Ξ1 = US$718.52 (165684480 wei/gas)
2017-12-17 11:00:03 WARN jsonrpc_ipc_server::server Removed existing file '/Users/Fidaa/Library/Application Support/io.parity.ethereum/jsonrpc.ipc'.
2017-12-17 11:00:05 IO Worker #0 TRACE sync == Connected 0: Geth/v1.6.7-stable-ab5646c5/linux-amd64/go1.8.3
2017-12-17 11:00:05 IO Worker #0 TRACE sync Sending status to 0, protocol version 63
2017-12-17 11:00:05 IO Worker #3 TRACE sync == Connected 2: Geth/v1.6.0-stable-facc47cb/linux-amd64/go1.7.3
2017-12-17 11:00:05 IO Worker #3 TRACE sync Sending status to 2, protocol version 63
2017-12-17 11:00:05 IO Worker #3 TRACE sync New peer 0 (protocol: 63, network: 15, difficulty: Some(154377518), latest:4a5a…4bb7, genesis:f849…1065, snapshot:None)
2017-12-17 11:00:05 IO Worker #3 TRACE sync Peer 0 genesis hash mismatch (ours: d4e5…8fa3, theirs: f849…1065)
2017-12-17 11:00:05 IO Worker #1 TRACE sync == Disconnecting 0: Geth/v1.6.7-stable-ab5646c5/linux-amd64/go1.8.3
2017-12-17 11:00:05 IO Worker #3 TRACE sync == Connected 1: Geth/geth-node-public-0/v1.7.0-stable-6c6c7b2a/linux-amd64/go1.9
2017-12-17 11:00:05 IO Worker #3 TRACE sync Sending status to 1, protocol version 63
2017-12-17 11:00:05 IO Worker #0 TRACE sync == Connected 4: Geth/v1.6.7-stable-ab5646c5/linux-amd64/go1.8.1
2017-12-17 11:00:05 IO Worker #0 TRACE sync Sending status to 4, protocol version 63
2017-12-17 11:00:05 IO Worker #3 TRACE sync == Connected 3: Geth/v1.5.9-stable/linux/go1.6.2
2017-12-17 11:00:05 IO Worker #3 TRACE sync Sending status to 3, protocol version 63
2017-12-17 11:00:05 IO Worker #3 TRACE sync New peer 2 (protocol: 63, network: 4, difficulty: Some(843969), latest:a954…2e71, genesis:6341…e177, snapshot:None)
2017-12-17 11:00:05 IO Worker #3 TRACE sync Peer 2 genesis hash mismatch (ours: d4e5…8fa3, theirs: 6341…e177)
2017-12-17 11:00:05 IO Worker #3 TRACE sync == Disconnecting 2: Geth/v1.6.0-stable-facc47cb/linux-amd64/go1.7.3
2017-12-17 11:00:05 IO Worker #1 TRACE sync == Connected 6: Geth/v1.7.0-unstable-3e0dbe0e/linux-amd64/go1.7.3
2017-12-17 11:00:05 IO Worker #1 TRACE sync Sending status to 6, protocol version 63
2017-12-17 11:00:05 IO Worker #0 TRACE sync New peer 1 (protocol: 63, network: 1060032, difficulty: Some(322378951831), latest:8e3f…80cb, genesis:f8e7…f1d0, snapshot:None)
2017-12-17 11:00:05 IO Worker #0 TRACE sync Peer 1 genesis hash mismatch (ours: d4e5…8fa3, theirs: f8e7…f1d0)
2017-12-17 11:00:05 IO Worker #0 TRACE sync == Disconnecting 1: Geth/geth-node-public-0/v1.7.0-stable-6c6c7b2a/linux-amd64/go1.9
2017-12-17 11:00:05 IO Worker #0 TRACE sync == Connected 5: Parity/v1.8.4-beta-c74c8c1-20171211/x86_64-linux-gnu/rustc1.22.1
2017-12-17 11:00:05 IO Worker #0 TRACE sync Sending status to 5, protocol version 2
2017-12-17 11:00:05 IO Worker #0 TRACE sync New peer 4 (protocol: 63, network: 2934, difficulty: Some(17179869184), latest:d4e5…8fa3, genesis:d4e5…8fa3, snapshot:None)
2017-12-17 11:00:05 IO Worker #0 TRACE sync Peer 4 network id mismatch (ours: 1, theirs: 2934)
2017-12-17 11:00:05 IO Worker #0 TRACE sync == Disconnecting 4: Geth/v1.6.7-stable-ab5646c5/linux-amd64/go1.8.1
2017-12-17 11:00:05 IO Worker #0 TRACE sync New peer 3 (protocol: 63, network: 1100, difficulty: Some(3033556547445), latest:28de…997c, genesis:6650…c158, snapshot:None)
2017-12-17 11:00:05 IO Worker #0 TRACE sync Peer 3 genesis hash mismatch (ours: d4e5…8fa3, theirs: 6650…c158)
2017-12-17 11:00:05 IO Worker #3 TRACE sync == Disconnecting 3: Geth/v1.5.9-stable/linux/go1.6.2
2017-12-17 11:00:05 IO Worker #3 TRACE sync New peer 6 (protocol: 63, network: 40734, difficulty: Some(990332028966), latest:983b…fc7b, genesis:8efc…fe3e, snapshot:None)
2017-12-17 11:00:05 IO Worker #3 TRACE sync Peer 6 genesis hash mismatch (ours: d4e5…8fa3, theirs: 8efc…fe3e)
2017-12-17 11:00:05 IO Worker #1 TRACE sync == Disconnecting 6: Geth/v1.7.0-unstable-3e0dbe0e/linux-amd64/go1.7.3
2017-12-17 11:00:05 IO Worker #0 TRACE sync New peer 5 (protocol: 2, network: 42, difficulty: Some(1683672574534736874278063855498815568067930370), latest:7194…d08d, genesis:a3c5…2cb9, snapshot:Some(5095000))
2017-12-17 11:00:05 IO Worker #0 TRACE sync Status packet from expired session 5:Parity/v1.8.4-beta-c74c8c1-20171211/x86_64-linux-gnu/rustc1.22.1
2017-12-17 11:00:05 IO Worker #1 TRACE sync == Disconnecting 5: Parity/v1.8.4-beta-c74c8c1-20171211/x86_64-linux-gnu/rustc1.22.1
2017-12-17 11:00:08 IO Worker #3 INFO network Public node URL: enode://e23a6b5438a9600e904a6878e1bc759cdb5f9699c282419fbf18d2406a1f32b9af54240bb430817611afaf4d5f1d0d2047e13b114c4cb2c382f77832e1f0a427@192.168.0.2:30303

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)...
I tried to clean up the cache, empty the db folder, and tried this with the stable 1.7.10 and with the beta 1.8.4 with the same result.

The original issue is a node being stuck after Byzantium hardfork at 4.7M, please upgrade your node if it's stuck on the same block.

@guigzz slow syncing is a separate issue, please follow #6372

Was this page helpful?
0 / 5 - 0 ratings

Related issues

uluhonolulu picture uluhonolulu  ·  3Comments

mr-older picture mr-older  ·  3Comments

barakman picture barakman  ·  3Comments

dukei picture dukei  ·  3Comments

m-thomson picture m-thomson  ·  3Comments