0

Geth seems to be always near reaching the highest block but never actually reaching the same number, so it never starts syncing states. knownStates is always 0.

Using geth attach there is always a small difference between currentBlock and highestBlock:

> eth.syncing
{
  currentBlock: 12903364,
  highestBlock: 12903434,
  knownStates: 0,
  pulledStates: 0,
  startingBlock: 12900170
}

BTW I am running an SSD, so no need to suggest that.

8
  • because geth has not synced yet. when you sync you will see false as output and not the counters
    – Nulik
    Commented Jul 14, 2021 at 15:31
  • you didn't even download the first account of the state yet
    – Nulik
    Commented Jul 14, 2021 at 15:32
  • How come "I" didn't download the first state, when it says currentBlock 12M? What should I do to have it download states? Commented Jul 15, 2021 at 16:09
  • because when you download the state you will have knownState set to something larger than 0, but apparently you are downloading via state snapshots, anyway this node hasn't synced yet
    – Nulik
    Commented Jul 15, 2021 at 19:02
  • Aynthing I can do to change this? Current block always seems 100 blocks behind no matter when I look Commented Jul 16, 2021 at 14:30

0

Browse other questions tagged or ask your own question.