fail to start bsc archive with new snapshot

[leowkong]

I have download the ""s3://public-blockchain-snapshots/bsc/erigon-16k-db-latest.mdbx.zstd" this week and start a bsc erigon archve node . Then I started it with newest erigon code. I have not use "https://github.com/allada/bsc-archive-snapshot. " and the node started and download snapshot automaticly. After finished indexing , I meeted this error blow and got struck , the error is "No block headers to write in this log period":

then I unwind 1000 blocks and restart it :

but it has still meeted the same error and even got a fatal error with memory

[allada]

It is missing the parlia database and when it attempts to rebuild it, it runs out of memory.

Try the latest code in this repo... I changed a bunch of stuff a few days ago they will likely help.

[leowkong]

try the latest code of erigon or the bsc-archive-snapshot script? I just used aws cp to download it , without running the script @allada Can I just download the latest "s3://public-blockchain-snapshots/bsc/erigon-16k-db-latest.mdbx.zstd" ?

[allada]

It is no longer stored there. Check the latest shell script. There is a new location.

[MacMemezie]

Im getting 404 key does not exist with the current endpoint in the shell script. Im not using zfs so I just need the files but the endpoint "aws s3 cp --request-payer=requester s3://public-blockchain-snapshots/bsc/erigon/archive/latest/v1/snapshots/" is giving key error.

Are we just waiting on a new update to the script? aws s3 ls shows all the folders without the bucket so I am a little confused as to why it is giving the error

[allada]

Use aws S3 sync