1

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?

1

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.

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

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.