JB273

Upgraded binary to v0.32.1, started a clean sync (Archival) and is stalls on the same block number. (1131146)

``` ExecStart=/home/pops/moonbase/moonbase \ --port 30335 \ --ws-port 9946 \ --ws-max-connections 10000 \ --execution wasm \ --wasm-execution compiled \ --state-pruning=archive \ --prometheus-external \ --prometheus-port 9617 \ --trie-cache-size 4 \ --db-cache 32000...

Resynced from scratch... still not passing block 1131146, not sure why this is... It's also odd as on the same machine Moonbeam synced flawless!

Did test no. 3 on testnet, this was successful.

@LeoHChen How can we test the stream syncing on mainnet?

@LeoHChen @sophoah How will we address the needed space issue for the future for this nodes, especially the ones for Shard 0!? 7.5TB is really a lot, it's almost the...

I did the following: * restarting the indexer it's on ? * subgraph_reassign ? * clearing postgres eth cache ? Nothing helps... after adding it to the indexer rules again...

> Are you sure that's not a ETH node issue? That one is still syncing for me. We are running this on an ETH Archive node (OpenEthereum 3.0.1) any options...

> The two above are still in sync for me also. Using Open Eth 3.0.0 though. What option have you on you ETH node enabled? We have this now: ExecStart=/home/node-admin/oe/openethereum...

Same is for ONE --> ETH