Closed quickchase closed 5 months ago
@quickchase Can you retry with --no-downloader=true
flag? erigon checks the --chain
flag to determine it it should start the snapshot downloader. And the default seems to be Ethereum mainnet if the chain flag is not provided.
@ImTei Ah, of course, that makes more sense. That does indeed solve the problem.
Great. I think the behavior was changed from the upstream erigon. Maybe I should open an issue on the upstream repo, or add an explanation in the README. Thanks for the reporting :)
System information
op-erigon version:
erigon version 0.05.0-2.56.2-0.5.0
op-node version:op-node version v1.7.3-a3cc8f27-1712594626
Problem
When following the tutorial to deploy a custom op-stack chain and launching
op-erigon
(as a standalone archive node on the network) it looks like op-erigon is trying to download snapshots even if I have--snapshots=false
in the config (even if I didn't it should default to not downloading snapshots?)Reproduction
After running
op-erigon init --datadir=/home/optimism/op-erigon genesis.json
my folder structure looks like this:All good...
Now I have op-erigon running in systemd:
systemctl daemon-reload && systemctl start op-erigon
After about 30 seconds after erigon has started my folder structure now looks like this:
The strangest part about this is that there are ZERO logs that
op-erigon
is doing anything with snapshots/torrents...these files just kind of appear magically and consume multiple/many gigabytes of space for no apparent reason.