near / stakewars-iii

Stake Wars: Episode 3 challenges and place to report issues
87 stars 177 forks source link

Blockchain sync has stuck #95

Closed dwrx closed 2 years ago

dwrx commented 2 years ago
INFO stats: # 1438750 Downloading blocks 4.16% (461236 left; at 1438750) 29 peers ⬇ 4.07 MB/s ⬆ 6.81 MB/s 0.00 bps 0 gas/s CPU: 59%, Mem: 7.81 GB
INFO stats: # 1438750 Downloading blocks 4.16% (461239 left; at 1438750) 30 peers ⬇ 4.00 MB/s ⬆ 12.0 MB/s 0.00 bps 0 gas/s CPU: 56%, Mem: 8.32 GB
INFO stats: # 1438750 Downloading blocks 4.16% (461243 left; at 1438750) 30 peers ⬇ 4.29 MB/s ⬆ 11.9 MB/s 0.00 bps 0 gas/s CPU: 45%, Mem: 7.38 GB
INFO stats: # 1438750 Downloading blocks 4.16% (461246 left; at 1438750) 30 peers ⬇ 4.14 MB/s ⬆ 6.58 MB/s 0.00 bps 0 gas/s CPU: 48%, Mem: 7.69 GB
INFO stats: # 1438750 Downloading blocks 4.16% (461251 left; at 1438750) 30 peers ⬇ 4.47 MB/s ⬆ 11.9 MB/s 0.00 bps 0 gas/s CPU: 66%, Mem: 8.31 GB

After the restart of the neard service:

WARN sync: Block sync: 1438750/1900059 No available archival peers to request block
....

HEAD detached at 68bfa84ed Tried to delete blockchain and resync from scratch.

stiavnik commented 2 years ago

I had similar when I purposely tried "archive true" in config.json, but "official" from S3 wget is set like this:

"archive": false

(ignore if this is something else, I think there are just no or not enough archival nodes with complete history running now)

dwrx commented 2 years ago

Thanks @stiavnik i will try to re-sync with non archival config (unfortunately, you need to delete data and re-start sync process). In the past it was required to switch node to archival mode, so I did it as usual during migration from the forked chain.

dwrx commented 2 years ago

I had similar when I purposely tried "archive true" in config.json, but "official" from S3 wget is set like this:

"archive": false

I confirm that resync after setting archive to false worked for me. Looks like there is no more archival nodes. Thanks @stiavnik