Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't sync testnet #15482

Closed
sgehrman opened this issue Nov 14, 2017 · 4 comments
Closed

Can't sync testnet #15482

sgehrman opened this issue Nov 14, 2017 · 4 comments

Comments

@sgehrman
Copy link

geth version:
Geth
Version: 1.7.3-unstable
Git Commit: ba62215
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.9.1
Operating System: linux
GOPATH=
GOROOT=/usr/lib/go-1.9

$ geth --testnet --rpc --cache=2048 console 2>> geth.log

Things seem to halt, I see this in the log:

Header broke chain ancestry peer=1061607032be098f number=1063864 hash=783f97…e1d196
WARN [11-14|14:34:24] Rolled back headers count=64 header=1063808->1063744 fast=1063587->1063587 block=0->0
WARN [11-14|14:36:29] Node data write error err="state node 342816…8bd7ba failed with all peers (2 tries, 2 peers)"
WARN [11-14|14:36:29] Synchronisation failed, dropping peer peer=1061607032be098f err="retrieved hash chain is invalid"
WARN [11-14|14:36:40] Ancestor below allowance peer=1e250be627644c2f number=973587 hash=000000…000000 allowance=973587
WARN [11-14|14:36:40] Synchronisation failed, dropping peer peer=1e250be627644c2f err="retrieved ancestor is invalid"
WARN [11-14|14:37:51] Ancestor below allowance peer=39c1806768d61f01 number=973587 hash=000000…000000 allowance=973587
WARN [11-14|14:37:51] Synchronisation failed, dropping peer peer=39c1806768d61f01 err="retrieved ancestor is invalid"

Stuck here:

eth.syncing
{
currentBlock: 1063587,
highestBlock: 1063863,
knownStates: 2923,
pulledStates: 2922,
startingBlock: 1061696
}

System information

Ubuntu 7.10

Expected behaviour

sync

Actual behaviour

stuck

Steps to reproduce the behaviour

installed everything fresh, new ubuntu install, nothing else

I've been trying for two weeks to start Eth dev, but I can't get a testnet. Are their correct instructions posted somewhere?

@mnkhbmb
Copy link

mnkhbmb commented Nov 18, 2017

i have same issue . Any solution?

WARN [11-18|09:52:46] Rolled back headers count=169 header=1819559->1819559 fast=2039565->2039565 block=0->0
WARN [11-18|09:52:46] Synchronisation failed, dropping peer peer=6ce05930c72abc63 err="retrieved hash chain is invalid"

@vladimirk-dev
Copy link

vladimirk-dev commented Nov 28, 2017

Hello,
Having identical issue here with Geth 1.7.3. for Windows x64
Running command with peers as it is described on: https://github.com/ethereum/ropsten
Command
geth --testnet --cache=2048 --rpc --bootnodes "enode://20c9ad97c081d63397d7b685a412227a40e23c8bdc6688c6f37e97cfbc22d2b4d1db1510d8f61e6a8866ad7f0e17c02b14182d37ea7c3c8b9c2683aeb6b733a1@52.169.14.227:30303,enode://6ce05930c72abc632c58e2e4324f7c7ea478cec0ed4fa2528982cf34483094e9cbc9216e7aa349691242576d552a2a56aaeae426c5303ded677ce455ba1acd9d@13.84.180.240:30303" console 2>> geth.log

Please note peculiar behaviour, is that ancestor allowance number ends with the same digits as current block. With the gap in between.

In case of OP
WARN [11-14|14:36:40] Ancestor below allowance peer=1e250be627644c2f number=973587 hash=000000…000000 allowance=973587
...
currentBlock: 1063587,

In my case:
eth.blockNumber
WARN [11-28|14:01:26] Ancestor below allowance peer=aa5ee49c3a44f337 number=298654 hash=000000…000000 allowance=298654
currentBlock: 388654

I've tried several times, it gets stuck with the same issue (a gap between ancestor allowance and current block, yet both ending equally).

@stale
Copy link

stale bot commented Nov 29, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot closed this as completed Jan 20, 2019
@kunalpblockarmour
Copy link

getting same issue "retrieved ancestor is invalid" any suggestions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants