20

Whenever I attempt to run geth on the command line, it seems to have trouble syncing with the blockchain. I am absolutely a novice so I could be completely overlooking. I am getting these warnings continuously(This is run on testnet):

WARN [04-21|17:40:40] Ancestor below allowance                 peer=20c9ad97c081d633 number=647267 hash=000000…000000 allowance=647267
WARN [04-21|17:40:40] Synchronisation failed, dropping peer    peer=20c9ad97c081d633 err="retrieved ancestor is invalid"

Please let me know if there is a solution for this. Thank you!

Ajay
  • 499
  • 3
  • 13
user3376899
  • 301
  • 1
  • 2
  • 3

4 Answers4

7

I received this error as well.

I deleted everything in the folder /Users/name/Library/Ethereum/testnet/geth/chaindata and then restarted with the command geth --testnet --fast and it started working

Ben B
  • 71
  • 1
  • 3
2

Ethereum testnet has different versions, now the main testnet is called Ropsten. you can see all of the ongoing Ethereum testnets here: testnet.etherscan.io

It should be noted that Ropsten testnet was attacked in Feb/March 2017, which lead to a fork on the testnet to revive the network. More to read here: Ropsten Revival

To use the revived version, you need to remove the database and start resyncing using the revived nodes: Ropsten testnet PoW chain

Shayan
  • 895
  • 2
  • 8
  • 24
2

I did the following:

➜ ~ rm -rf ~/Library/Ethereum/testnet/geth/chaindata

Then:

➜ ~ geth --testnet --syncmode "fast" --rpc --rpcapi db,eth,net,web3,personal --cache=1024 --rpcport 8545 --rpcaddr 127.0.0.1 --rpccorsdomain "*"

And it should works

0xgoku
  • 471
  • 3
  • 5
  • 16
1

I had this problem, where my chain was just perpetually ~90 blocks away from current. Restarting geth fixed it for me, luckily.

Nick
  • 141
  • 3