Tobi Akerele

Seems like issue was fixed in develop here - https://github.com/ethereum-optimism/optimism/pull/10210

I'm assuming you want to see the non-memory stats info but just in case ``` + polygon-0 › erigon polygon-0 erigon [INFO] [06-23|17:18:00.149] [5/15 Bodies] Downloading block bodies block_num=56299999 delivery/sec=108.6MB...

Here's a different pod ``` polygon-2 erigon [INFO] [06-25|15:37:10.858] [3/15 BorHeimdall] Processing spans... from=8783 to=9094 polygon-2 erigon [INFO] [06-25|15:37:12.451] [3/15 BorHeimdall] Processing sync events... from=56209000 to=58197424 polygon-2 erigon [EROR] [06-25|15:37:12.452]...

Other pods ``` + polygon-1 › erigon polygon-1 erigon meta_checktxnid:11415 catch invalid root_page_txnid 4676552 for maindb.mod_txnid 4676547 (workaround for incoherent flaw of unified page/buffer cache) polygon-1 erigon [INFO] [06-24|14:14:00.389] [5/15...

@AskAlexSharov thoughts on the potential issue?

Hi this is what I got after running the `integration stage_headers --reset` command. ``` + polygon-3 › erigon-integration polygon-3 erigon-integration + /app/integration --help polygon-3 erigon-integration time="2024-07-09T06:08:47Z" level=error msg="unable to parse...

@AskAlexSharov The command didn't work, it's still stuck

Hi @taratorio Can you provide both solutions? The bandaid solution and the patch branch? I will use 2 separate pods to deploy both strategies and take a snapshot of the...

@taratorio Ah gotcha can I get the bandaid solution in that case? It's urgent as we want to start using erigon a lot more as we move away from bor

Ok I took a different approach so that I can at least skip all the way to block `53843475` which is the current block of the snapshot here - https://snapshots.polygon.technology/....