2

I am expereincing problem while syncing testnet with tail of log: 

WARN [01-09|06:53:30] Ancestor below allowance peer=1061607032be098f number=1082429 hash=000000…000000 allowance=1082429 WARN [01-09|06:53:30] Synchronisation failed, dropping peer peer=1061607032be098f err="retrieved ancestor is invalid" WARN [01-09|06:54:46] Ancestor below allowance peer=a6134934cc2d3f31 number=1082429 hash=000000…000000 allowance=1082429 WARN [01-09|06:54:46] Synchronisation failed, dropping peer peer=a6134934cc2d3f31 err="retrieved ancestor is invalid"

Already asked at -
Synchronisation failed, dropping peer
However I do not want to delete whole of data. What can I do?

Improve this question

1 Answer 1

Reset to default
3

It's happen usually when peers are disconnect (reject or whatever), you can ignore it. Your geth is actually syncing with network and you must wait.

Improve this answer
8
  • 1
    Its been like this for a few hours now. Also, eth.syncing gives false. Is all this normal? Commented Jan 9, 2018 at 7:14
  • 1
    if the eth.syncing returns false then your geth node is synced. What the output of eth.blockNumber? Commented Jan 9, 2018 at 7:16
  • 1
    1172429 Also, this(1172429) was shown as highest block when it was syncing Commented Jan 9, 2018 at 7:29
  • 1
    What the network id you're using? Ropsten Kovan? Commented Jan 9, 2018 at 7:33
  • 1
    I used --testnet flag, which I assume uses Ropsten network. And I just came to know the highest block there is 24xxxxx Commented Jan 9, 2018 at 7:40

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.