Block synchronization never ends.

[blockchen-admin]

CPU : AMD 3500X
RAM : 24GB
SSD : 970 EVO PLUS

Synchronization was not finished even with the ssd I was using before.
I tried upgrading the ssd but still the sync doesn't finish. what's the problem??

{"jsonrpc":"2.0","id":1,"result":{"currentBlock":"0x7e7956","highestBlock":"0x7e79ce","knownStates":"0x2478203b","pulledStates":"0x2477d318","startingBlock":"0x7e7930"}}

[koen84]

1. Snapshots have been reported syncing problems, better start blank.
2. Use NVMe only. There network got a lot more intensive. NVMe requirement has been sourced into official docs.

[nfnvsc]

eth.syncing
{
currentBlock: 8535295,
highestBlock: 8535391,
knownStates: 402887415,
pulledStates: 402805636,
startingBlock: 8533190
}

It's been like 24h, is this normal? I'm using an nvme with high IOPS (400k), 32gb ram

[aaadipopt]

same here, the node is syncing with 1-7blk/8s or smtg like that for aws ssd io2/32k iops. even if the node will catch the network will can't keep up with

geth version: Version: 1.1.0-beta

[khelle]

It would be helpful if any actual developers of this node tried to solve issues with sync. There are tons of issues being posted on those forums everyday regarding the sync and the answer is always "use NVMe". What about people that already uses NVMe and still have problems? Could you at least update specs on the BSC pages, because the current recommended requirements do not allow syncing?

The question I have - do I need supercomputer to sync it? Because even higher tiers dedicated machines from dedicated datacentres are not enough.

[nfnvsc]

@khelle I ended up beeing able to sync the node. What I recommend you to do is: download the latest snapshot avaliable (took me around 1 day to download) and just use that to sync, it took me an extra 4h to sync from the snapshot to the latest block.

[yg0x01]

Hi, @nfnvsc , thanks for your recommend. I'm suffering the node syncing problem these days and I want confirm if the latest snapshot is here and if I should use geth v1.1.0 for it as the official doc mentioned?

I use AWS i3.xlarge with NVMe in Seoul region from blank but after 22 hours the syncing is not finished.

{
  currentBlock: 9165633,
  highestBlock: 9165718,
  knownStates: 419142115,
  pulledStates: 419043043,
  startingBlock: 0
}

The database reach 292G now.

Not sure if I need start over with snapshot.

Thx.

[nfnvsc]

Hi, @nfnvsc , thanks for your recommend. I'm suffering the node syncing problem these days and I want confirm if the latest snapshot is here and if I should use geth v1.1.0 for it as the official doc mentioned?

I use AWS i3.xlarge with NVMe in Seoul region from blank but after 22 hours the syncing is not finished.

{

  currentBlock: 9165633,

  highestBlock: 9165718,

  knownStates: 419142115,

  pulledStates: 419043043,

  startingBlock: 0

}

The database reach 292G now.

Not sure if I need start over with snapshot.

Thx.

Hey, yes that is the same link i did my download. Yes I'm using geth v1.1.0-beta. Followed all the steps from the oficial binance full node. From what I've been through, I also got mine stuck on the last 100 blocks or so and I had to redo all to solve that.

[n8twj]

Get faster hardware

…

On Sat, Jul 17, 2021 at 5:25 PM nfnvsc ***@***.***> wrote: Hi, @nfnvsc <https://github.com/nfnvsc> , thanks for your recommend. I'm suffering the node syncing problem these days and I want confirm if the latest snapshot is here <https://github.com/binance-chain/bsc-snapshots> and if I should use geth v1.1.0 for it as the official doc mentioned? I use AWS i3.xlarge with NVMe in Seoul region from blank but after 22 hours the syncing is not finished. { currentBlock: 9165633, highestBlock: 9165718, knownStates: 419142115, pulledStates: 419043043, startingBlock: 0 } The database reach 292G now. Not sure if I need start over with snapshot. Thx. Hey, yes that is the same link i did my download. Yes I'm using geth v1.1.0-beta. Followed all the steps from the oficial binance full node. From what I've been through, I also got mine stuck on the last 100 blocks or so and I had to redo all to solve that. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#288 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGIZ4KBJ3ODC7OCTCWUIA3TYHYMBANCNFSM46VBTNRQ> .

[stenleegunz]

Get faster hardware
…
On Sat, Jul 17, 2021 at 5:25 PM nfnvsc @.***> wrote: Hi, @nfnvsc https://github.com/nfnvsc , thanks for your recommend. I'm suffering the node syncing problem these days and I want confirm if the latest snapshot is here https://github.com/binance-chain/bsc-snapshots and if I should use geth v1.1.0 for it as the official doc mentioned? I use AWS i3.xlarge with NVMe in Seoul region from blank but after 22 hours the syncing is not finished. { currentBlock: 9165633, highestBlock: 9165718, knownStates: 419142115, pulledStates: 419043043, startingBlock: 0 } The database reach 292G now. Not sure if I need start over with snapshot. Thx. Hey, yes that is the same link i did my download. Yes I'm using geth v1.1.0-beta. Followed all the steps from the oficial binance full node. From what I've been through, I also got mine stuck on the last 100 blocks or so and I had to redo all to solve that. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#288 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGIZ4KBJ3ODC7OCTCWUIA3TYHYMBANCNFSM46VBTNRQ .

this is not an answer, with such an opinion it is better not to write anything

[j75689]

Hi all.
Thank you for your report.
We have received many report of a sync issue.
You can try the latest version. If you have any probleums, please feedback #338.
We will pay attention to the issue #338 for a long time, and if there are any updates, we will explain it on this issue.

Thanks.