Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node synchronization problem, always keep a distance of about 100 from the latest height #22372

Closed
lyon0712 opened this issue Feb 24, 2021 · 2 comments

Comments

@lyon0712
Copy link

Node synchronization problem, always keep a distance of about 100 from the latest height

The node has been running normally, and there is no error message logs.
When querying in the console, the currentBlock and highestBlock always have a difference of more than 100 block heights. This situation has been maintained for more than a week.
I tried restarting geth, but it didn't solve the problem.

geth version

Geth
Version: 1.9.25-stable
Git Commit: e7872729012a4871397307b12cc3f4772ffcbec6
Architecture: amd64
Protocol Versions: [65 64 63]
Go Version: go1.14.13
Operating System: linux
GOPATH=/home/ec2-user/go
GOROOT=/usr/local/go

latest log

INFO [02-24|02:42:40.509] Imported new state entries               count=384  elapsed="648.175µs" processed=733862267 pending=56131 trieretry=0   coderetry=0 duplicate=0 unexpected=768
INFO [02-24|02:42:41.065] Imported new block headers               count=1    elapsed=86.211ms    number=11917207 hash="3eabed…f1c018"
INFO [02-24|02:42:49.497] Imported new state entries               count=384  elapsed="488.864µs" processed=733862651 pending=56554 trieretry=2   coderetry=0 duplicate=0 unexpected=768
INFO [02-24|02:42:50.147] Imported new block headers               count=1    elapsed=20.647ms    number=11917208 hash="c5c3c1…a266a0"
INFO [02-24|02:42:55.331] Imported new state entries               count=313  elapsed=1.212ms     processed=733862964 pending=56880 trieretry=4   coderetry=0 duplicate=0 unexpected=768
INFO [02-24|02:43:04.420] Imported new state entries               count=384  elapsed="523.437µs" processed=733863348 pending=57376 trieretry=0   coderetry=0 duplicate=0 unexpected=768
INFO [02-24|02:43:05.358] Imported new block headers               count=1    elapsed=10.462ms    number=11917209 hash="0c1eb7…28d24f"
INFO [02-24|02:43:11.513] Imported new block headers               count=1    elapsed=53.987ms    number=11917210 hash="1f8875…93788a"
INFO [02-24|02:43:14.120] Imported new state entries               count=384  elapsed="558.113µs" processed=733863732 pending=57759 trieretry=0   coderetry=0 duplicate=0 unexpected=768

console information

> eth.syncing
{
  currentBlock: 11917111,
  highestBlock: 11917213,
  knownStates: 733924498,
  pulledStates: 733865222,
  startingBlock: 11880232
}
> eth.blockNumber
0
@ppershing
Copy link

I have similar problem. I am trying to re-sync node since last week. The process few time crashed and few time got stuck about 100 blocks from the head.

> eth.syncing

{
  currentBlock: 11920443,
  highestBlock: 11920560,
  knownStates: 571082961,
  pulledStates: 570992471,
  startingBlock: 11918187
}

The states keep advancing as well as currentBlock but it always seem to keep about 80-100 blocks behind the tip

@ligi
Copy link
Member

ligi commented Feb 25, 2021

Please read: #16218 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants