0

This question already has an answer here:

Geth is refusing to sync the last 100 blocks on the ropsten testnet, is there a way to force geth to continue syncing from the console?

marked as duplicate by Ismael, TC8, Achala Dissanayake, mirg, Malone Mar 22 '18 at 11:11

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • You will have to wait, it appears to be stuck but it is processing new 'states'. – Ismael Mar 21 '18 at 5:23
0

Can you run in the geth console

admin.peers.length

And

net.peerCount

To check if you are connected to any nodes?

Also you can check if you are currently synching to the network

eth.syncing

You can find out the current block number with

eth.getBlockNumber(console.log)

To make sure you are connecting to a ropsten node you can try adding the bootstrap node directly

admin.addPeer("enode://158f8aab45f6d19c6cbf4a089c2670541a8da11978a2f90dbf6a502a4a3bab80d288afdbeb7ec0ef6d92de563767f3b1ea9e8e334ca711e9f8e2df5a0385e8e6@13.75.154.138:30303")    
  • I am connected to 2 other nodes according to those commands – arshbot Mar 20 '18 at 22:38
  • I've added a few more checks to do – cleanunicorn Mar 20 '18 at 22:56
  • eth.syncing returns the currentBlock, highestBlock etc.. which are off by about ~60 blocks but it seems the currentBlock is not updating while the highestBlock is. eth.getBlockNumber(console.log) returns null 0 \n undefined. Adding the boostrap node returned true but admin.peers.length and net.peerCount still return 2. – arshbot Mar 20 '18 at 23:05

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