beacon hangs on start with Medalla

[dangerousfood]

Blocks don't start sync from Eth1 client and deposits aren't run

[mpetrunic]

Our eth1 processing doesn't work very well and blocks everything. You should probably disable eth1 processing (--eth1.enabled false) until we fix that.

[larry0x]

Our eth1 processing doesn't work very well and blocks everything. You should probably disable eth1 processing (--eth1.enabled false) until we fix that.

I'm having exactly the same issue. Disabling eth1 seems to make no difference:

larry@bacon:~/eth2/lodestar$ yarn run cli beacon --testnet medalla --rootDir ~/.lodestar --eth1.enabled false --metrics.enabled false
yarn run v1.22.4
$ node --trace-deprecation ./packages/lodestar-cli/bin/lodestar beacon --testnet medalla --rootDir /home/larry/.lodestar --eth1.enabled false --metrics.enabled false
2020-08-06 00:35:39  [CHAIN]            info: Initializing beacon chain with state root 0xaf6aafa94dcc22a5cf0253c4f5dd886397900034bf7c149c54635b537f34f64e and block root 0xebe49843e96e538592c9e1976e155e9057c251ed9312eba517afce3ca1a0660c, number of validator: 20084 
2020-08-06 00:35:47  [CHAIN]            info: Beacon chain initialized 
2020-08-06 00:35:47  [NODE]             info: Starting eth2 beacon node - LODESTAR! 
2020-08-06 00:35:47  [DB]               info: Connected to LevelDB database at /home/larry/.lodestar/chain-db 
2020-08-06 00:35:56  [CHAIN]            info: Chain started, waiting blocks and attestations 
2020-08-06 00:35:56  [CHAIN]            info: Found last known finalized state at epoch #0 root 0x0000000000000000000000000000000000000000000000000000000000000000 
2020-08-06 00:35:56  [CHAIN]            info: Found 2 nonfinalized blocks in database from slot 0 to 0 
2020-08-06 00:35:56  [CHAIN]            info: Found finalized block at slot 0,
        root=0xebe49843e96e538592c9e1976e155e9057c251ed9312eba517afce3ca1a0660c 
2020-08-06 00:35:56  [CHAIN]            info: No need to reprocess blocks

[dangerousfood]

I use that option to no effect. I performed an rm -rf on the chain-db before starting as well

Params 👇

yarn run cli beacon \
  --testnet medalla \
  --rootDir /Users/dangerousfood/Dev/eth2-medalla/lodestar \
  --eth1.provider.url https://goerli.prylabs.net \
  --metrics.serverPort 8009 \
  --eth1.enabled false

[dapplion]

@dangerousfood Thanks for reporting! Would you mind pasting your CLI logs, doing a rm -rf on the chain-db directory beforehand? Or are they the same as the original message?

[larry0x]

I'd like to report that after pulling the latest commits and recompiling Lodestar, this issue disappeared for me. This is without removing the chain-db directory and with --eth1-enabled being true.

[dapplion]

@Larrypcdotcom Awesome! Thanks for reporting back. What a fire background tho @dangerousfood 🔥