mohoff

I'm also not sure, never worked with POA/xDai before. My guess is just the chain id.

Will test this using a newer Erigon version once the node is synced

Another data point: Alpha Erigon seems lagging behind Beta Erigon as well. Seeing up to 11 block difference, few times 5-7 blocks difference over the last 24h while collecting metrics...

Tested this over night but not helping @AskAlexSharov Generally, do you recommend adding `--snap.stop` to Alpha nodes that finished the initial sync?

It means we still see the same block lag as described in OP

@AskAlexSharov Digged out some graphs, there are definitely spikes but it's not capping out Regarding "it's still making progress": Looks stuck, it's jumping around in block numbers and on each...

Now seeing after restart: ``` [INFO] [07-11|17:20:22.571] Opening Database label=chaindata path=/home/erigon/erigon-goerli-data/chaindata mdbx_ipclock_failed:30764 wlock owner died, recovering ``` Any ideas to repair this? Otherwise I purge and start from the beginning

@AskAlexSharov Your example points at a multi-container setup but I have Erigon and RPC daemon running as separate processes in the same container. Does the PID tweak still apply?

Seeing the same on v2.28.1 ``` [EROR] [10-18|11:10:42.663] Staged Sync err="runtime error: slice bounds out of range [650:41], snapshot: 7000000-7500000, trace: [block_reader.go:509 panic.go:838 panic.go:117 decompress.go:541 block_reader.go:524 block_reader.go:281 block_snapshots.go:268 block_reader.go:275 stage_headers.go:481...