I am running a private network and one node seems to have stopped updating its chain. It is stuck at block 264 while the others are hundreds past it. It is still connected to the network, but it has stopped logging altogether. I can still interact with it from the console.

  • Check the connected peers from geth's console admin.peers. Check the log message, if there's any error it should there. Check for hardware errors, like not enough RAM memory, disk space or data corruption. – Ismael May 17 '19 at 20:37
  • The node still lists the peers it should be connected to. The only log message out of the ordinary I see is WARN: Synchronisation failed, dropping peer with the associated error "no peers available or all tried for download" – user51707 May 20 '19 at 14:02

Your Answer

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

Browse other questions tagged or ask your own question.