Mirror of forum.nim-lang.org

9503 :: Nimbus-eth2 beacon node setup

• Cnerd (orginal) [2022-10-02T13:55:47+02:00] view original

  I am trying to run nimbus as a beacon node consensus client with geth as the execution client. And geth has synchronized with the mainnet to the point of merge and needs a consensus client to guide it through merge synchronization.

   [10-02|11:40:47.999] Post-merge network, but no beacon client seen. Please launch one to follow the chain!
  WARN [10-02|11:41:00.857] Snapshot extension registration failed   peer=e2d00418 err="peer connected on snap without compatible eth support"
  WARN [10-02|11:42:21.797] Snapshot extension registration failed   peer=aab3bbde err="peer connected on snap without compatible eth support"
  WARN [10-02|11:42:47.744] Dropping unsynced node during sync       id=ff9a9ea0f4d50194 conn=inbound addr=173.249.6.189:34618   type=Geth/v1.10.8-stable-..
  Run

  But while running nimbus I keep getting ETH 1 chain monitoring failure, restarting here's the full log

   2022-10-02 11:30:23.144+00:00 Eth1 chain monitoring failure, restarting  topics="eth1" err="getBlockByHash(m.dataProvider,\n               BlockHash(m.depositsChain.finalizedBlockHash.data)) failed 3 times. Last error: Parameter [result] expected JObject but got JNull"
  INF 2022-10-02 11:30:28.467+00:00 Starting Eth1 deposit contract monitoring  topics="eth1" contract=0x00000000219ab540356cbb839cbe05303d7705fa
  INF 2022-10-02 11:30:28.467+00:00 Waiting for new Eth1 block headers         topics="eth1"
  INF 2022-10-02 11:30:35.047+00:00 Slot start                                 topics="beacnde" slot=4823851 epoch=150745 sync="01d19h53m (10.18%) 27.4252slots/s (DDQQDPDQUQ:491169)" peers=46 head=6a110dae:491194 finalized=15347:4a95cbe6 delay=47ms237us621ns
  INF 2022-10-02 11:30:35.122+00:00 Slot end                                   topics="beacnde" slot=4823851 nextActionWait=n/a nextAttestationSlot=-1 nextProposalSlot=-1 head=6a110dae:491194
  INF 2022-10-02 11:30:47.002+00:00 Slot start                                 topics="beacnde" slot=4823852 epoch=150745 sync="01d19h51m (10.19%) 27.4436slots/s (DDUQQDDPUQ:491521)" peers=45 head=d3340ca5:491535 finalized=15358:2ae65f23 delay=2ms794us931ns
  INF 2022-10-02 11:30:47.118+00:00 Slot end                                   topics="beacnde" slot=4823852 nextActionWait=n/a nextAttestationSlot=-1 nextProposalSlot=-1 head=d3340ca5:491535
  INF 2022-10-02 11:30:59.002+00:00 Slot start                                 topics="beacnde" slot=4823853 epoch=150745 sync="01d19h51m (10.20%) 27.4358slots/s (DDDQQDDPUQ:491809)" peers=45 head=96a19b64:491880 finalized=15369:42612b3c delay=2ms736us751ns
  INF 2022-10-02 11:30:59.122+00:00 Slot end                                   topics="beacnde" slot=4823853 nextActionWait=n/a nextAttestationSlot=-1 nextProposalSlot=-1 head=96a19b64:491880
  INF 2022-10-02 11:31:11.006+00:00 Slot start                                 topics="beacnde" slot=4823854 epoch=150745 sync="01d19h49m (10.20%) 27.4537slots/s (DDDPQDQDUD:492161)" peers=45 head=8766a73b:492216 finalized=15379:9ab47ad3 delay=6ms669us821ns
  INF 2022-10-02 11:31:11.099+00:00 Slot end                                   topics="beacnde" slot=4823854 nextActionWait=n/a nextAttestationSlot=-1 nextProposalSlot=-1 head=8766a73b:492216
  WRN 2022-10-02 11:31:17.041+00:00 Eth1 chain monitoring failure, restarting  topics="eth1" err="getBlockByHash(m.dataProvider,\n               BlockHash(m.depositsChain.finalizedBlockHash.data)) failed 3 times. Last error: Parameter [result] expected JObject but got JNull"
  INF 2022-10-02 11:31:22.237+00:00 Starting Eth1 deposit contract monitoring  topics="eth1" contract=0x00000000219ab540356cbb839cbe05303d7705fa
  INF 2022-10-02 11:31:22.237+00:00 Waiting for new Eth1 block headers         topics="eth1"
  INF 2022-10-02 11:31:23.019+00:00 Slot start                                 topics="beacnde" slot=4823855 epoch=150745 sync="01d19h50m (10.21%) 27.4449slots/s (QPDDQQQDUD:492481)" peers=45 head=9f4ce7bc:492558 finalized=15390:4985f0b0 delay=19ms789us416ns
  INF 2022-10-02 11:31:23.138+00:00 Slot end                                   topics="beacnde" slot=4823855 nextActionWait=n/a nextAttestationSlot=-1 nextProposalSlot=-1 head=9f4ce7bc:492558
  Run

  Here's the command used to run geth

   --ws --authrpc.addr localhost --authrpc.port 8551 --authrpc.vhosts localhost --authrpc.jwtsecret /tmp/jwtsecret
  Run

  And here's the command for nimbus

  ./run-prater-beacon-node.sh \
    --web3-url=ws://127.0.0.1:8551 \
    --jwt-secret=/tmp/jwtsecret
  Run

  After search through google i found out that the nimbus error is as a result of nimbus not being able to connect to an execution client. Which means for some reason nimbus is not seeing geth.

  Any help and/or explanation would be appreciated. Thanks.

---

• mratsim (orginal) [2022-10-03T11:49:32+02:00] view original

  The proper support channel for Nimbus is the nimbus discord (https://discord.gg/rqUCEptT temp link 7 days to limit spam bots).

  What are your Geth and Nimbus versions?

  You can use nimbus_beacon_node --version to get it.

  Also can you try connecting via http, for Geth:

  
  --authrpc.addr localhost --authrpc.port 8551 --authrpc.vhosts localhost --authrpc.jwtsecret /tmp/jwtsecret
  Run

  (I removed the --ws)

  and for Nimbus:

  
  ./run-prater-beacon-node.sh \
    --web3-url=http://127.0.0.1:8551 \
    --jwt-secret=/tmp/jwtsecret
  
  Run

---