Closed dwrx closed 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)
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.
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
After the restart of the
neard
service:HEAD detached at 68bfa84ed Tried to delete blockchain and resync from scratch.