block sync problem.

[ilyeong-ai]

gents, I am trying to sync and it stoped '69167627'.

Loading state in fast sync mode. Imported 69167627 of 69473822 known state nodes.

Systems logs are as follow.

2018-08-04 01:22:38,287 WARN [EDT] blockchain - EDT task executed in more than 1 sec: 3244ms, Executor queue size: 152

2018-08-04 01:22:41,742 INFO [FastSyncLoop] sync - FastSync: received: 69167627, known: 306195, pending: 0, nodes/sec: 0.00

2018-08-04 01:22:41,835 INFO [EthJClientWorker-1] sync - Peer 93ea77c4: disconnected

2018-08-04 01:22:45,172 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:45,173 INFO [pool-11-thread-1] net - New peers processed: [f536efbe | /54.227.200.14:30303], active peers added: 1, total active peers: 1

2018-08-04 01:22:48,593 INFO [WireTrafficStats-0] net - TCP: Speed in/out 0b / 298b(sec), packets in/out 0/8, total in/out: 10Gb / 2Gb

2018-08-04 01:22:48,593 INFO [WireTrafficStats-0] net - UDP: Speed in/out 381b / 1778b(sec), packets in/out 20/69, total in/out: 125Mb / 347Mb

2018-08-04 01:22:48,594 WARN [P2pPingTimer] net - 93ea77c4 | /34.203.229.182:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:48,594 INFO [FastSyncLoop] sync - FastSync: received: 69167627, known: 306195, pending: 0, nodes/sec: 0.00

2018-08-04 01:22:48,594 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:48,674 INFO [pool-6-thread-1] sync - Sync state: StateNodes (69167627 of 69473822), last block #0, best known #6083971

2018-08-04 01:22:52,007 WARN [P2pPingTimer] net - 93ea77c4 | /34.203.229.182:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:55,422 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:55,427 INFO [FastSyncLoop] sync - FastSync: received: 69167627, known: 305811, pending: 384, nodes/sec: 0.00

2018-08-04 01:22:55,508 WARN [P2pPingTimer] net - 93ea77c4 | /34.203.229.182:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:59,684 INFO [WireTrafficStats-0] net - TCP: Speed in/out 94b / 219b(sec), packets in/out 2/8, total in/out: 10Gb / 2Gb

2018-08-04 01:22:59,684 INFO [WireTrafficStats-0] net - UDP: Speed in/out 187b / 1016b(sec), packets in/out 8/74, total in/out: 125Mb / 347Mb

2018-08-04 01:22:59,685 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:22:59,686 WARN [EDT] blockchain - EDT task executed in more than 1 sec: 4060ms, Executor queue size: 91

2018-08-04 01:22:59,709 INFO [pool-6-thread-1] sync - Sync state: StateNodes (69167627 of 69473822), last block #0, best known #6083971

2018-08-04 01:23:03,191 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:23:03,198 INFO [FastSyncLoop] sync - FastSync: received: 69167627, known: 306195, pending: 0, nodes/sec: 0.00

2018-08-04 01:23:10,021 INFO [pool-8-thread-1] sync - Peer stats: Active peers

Peer V63: [ f536efbe, NODE_RETRIEVING, ping 17242 ms, rep: 6000, difficulty 5776904216858993224672, best block 6083971, wait 21s]: (idle 1m6s of 1m6s) Geth/v1.8.7-stable/linux-amd64/go1.9.2 Nodes/sec: NaN, miss: NaN Other connected peers

2018-08-04 01:23:10,021 INFO [pool-8-thread-1] sync -

2018-08-04 01:23:10,021 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:23:10,023 INFO [WireTrafficStats-0] net - TCP: Speed in/out 67b / 468b(sec), packets in/out 2/13, total in/out: 10Gb / 2Gb

2018-08-04 01:23:10,023 INFO [WireTrafficStats-0] net - UDP: Speed in/out 513b / 1944b(sec), packets in/out 21/84, total in/out: 125Mb / 348Mb

2018-08-04 01:23:10,024 INFO [pool-6-thread-1] sync - Sync state: StateNodes (69167627 of 69473822), last block #0, best known #6083971

2018-08-04 01:23:10,028 INFO [FastSyncLoop] sync - FastSync: received: 69167627, known: 306195, pending: 0, nodes/sec: 0.00

2018-08-04 01:23:13,513 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:23:16,995 INFO [EthJClientWorker-1] sync - Peer fcef7a05: invalid response to initial [GET_BLOCK_HEADERS blockNumber=0 blockHash=6882655a8e9874d482f0f81b7148950d04456e594757e91dd151813d44f6c1df maxHeaders=1 skipBlocks=0 reverse=false], empty

2018-08-04 01:23:16,995 INFO [EthJClientWorker-1] sync - Peer fcef7a05: is a bad one, drop

2018-08-04 01:23:16,979 INFO [FastSyncLoop] sync - FastSync: received: 69167627, known: 306195, pending: 0, nodes/sec: 0.00

2018-08-04 01:23:16,996 WARN [EthJClientWorker-1] net - fcef7a05 | /40.115.33.57:30305: attempt to send [BLOCK_HEADERS] message after disconnect

2018-08-04 01:23:20,428 WARN [P2pPingTimer] net - f536efbe | ec2-54-227-200-14.compute-1.amazonaws.com/54.227.200.14:30303: attempt to send [PING] message after disconnect

2018-08-04 01:23:20,429 INFO [pool-6-thread-1] sync - Sync state: StateNodes (69167627 of 69473822), last block #0, best known #6083971

2018-08-04 01:23:20,429 INFO [WireTrafficStats-0] net - TCP: Speed in/out 73Kb / 226b(sec), packets in/out 8/11, total in/out: 10Gb / 2Gb

2018-08-04 01:23:20,429 INFO [WireTrafficStats-0] net - UDP: Speed in/out 528b / 1136b(sec), packets in/out 23/70, total in/out: 125Mb / 348Mb

[mkalinin]

What is the network you're connected to?

[ilyeong-ai]

I am trying to connect ETH main network.

[ilyeong-ai]

2018-08-04 14:00:48,190 WARN [nioEventLoopGroup-3-3] net - Can't decrypt AuthInitiateMessage from /116.52.3.66:56478. Most likely the remote peer used wrong public key (NodeID) to encrypt message.

[mkalinin]

This message starts to occur when you removes database with nodeId.properties. Then id of your node is updated but other peers try to use an old one. The best option for you would be to change port, e.g. use 30304 instead of default one.

[ilyeong-ai]

thank you.

[mkalinin]

did that help anyhow?

[ilyeong-ai]

yes!! thank you so much!

[mkalinin]

cool! you're welcome ;)