Alex Sharov
Alex Sharov
It’s OOM killer. Maybe we have mem leak.
Check that your processes have different pid: https://github.com/ledgerwatch/erigon/blob/b161c27ac318e5689656929ee032aea5b1c0350d/docker-compose.yml#L19
@mohoff you processes have different PID you are good
> Arent we already verifying after we start erigon? yes, but this issue is not about "some snapshot was broken", this issue is about "by some reason we have wrong/old/buggy...
But! Now I realized next logic is correct: - Erigon must try to download only whitelisted .torrent files - Erigon can seed .torrent files if they are not whitelisted and...
To summarise: - Erigon must not try to download files if they are not whitelisted in https://github.com/ledgerwatch/erigon-snapshot - even if user manually created .torrent file in snapshots dir
`What if someone wants to use their own snapshots?` - just place custom snapshots to snapshots dir. 1. use and seed non-whitelisted snapshots is fine 2. download non-whitelisted snapshots not...
It’s another story. Never seen. But yes, need fix it somehow - if it happening
@enriavil1 maybe this is the reason: https://github.com/ledgerwatch/erigon/issues/4979