No attestations, Geth stuck at 99.99% synced & unable to communicate with Consensus client

It’s been over a week now.

I’ve tried everything I can think of and still cannot get my validators attesting again. I’ve made sure all the packages are updated.

In the Geth logs I see (redundant logs omitted)

INFO [08-20|18:44:37.904] Syncing: chain download in progress      synced=100.00% chain=541.67GiB headers=17,930,072@8.20GiB bodies=17,929,975@377.54GiB receipts=17,929,975@155.92GiB eta=59m53.264s
WARN [08-20|18:44:44.842] Beacon client online, but no consensus updates received in a while. Please fix your beacon client to follow the chain! 
...
INFO [08-20|18:46:39.636] Writing clean trie cache to disk         path=/root/.ethereum/geth/triecache threads=1
INFO [08-20|18:46:39.637] Regenerated local transaction journal    transactions=0 accounts=0
INFO [08-20|18:46:39.657] Persisted the clean trie cache           path=/root/.ethereum/geth/triecache elapsed=20.155ms
INFO [08-20|18:46:45.986] Syncing: chain download in progress      synced=100.00% chain=541.67GiB headers=17,930,072@8.20GiB bodies=17,929,975@377.54GiB receipts=17,929,975@155.92GiB eta=59m54.572s
WARN [08-20|18:46:46.353] System clock seems off by -57m17.242692587s, which can prevent network connectivity 
WARN [08-20|18:46:46.353] Please enable network time synchronisation in system settings. 

Prysm is fully synced. In the Prysm logs I see (redundant logs omitted)

time="2023-08-20 18:43:23" level=info msg="Previous epoch voting summary" correctlyVotedHead=false correctlyVotedSource=false correctlyVotedTarget=false epoch=223261 inactivityScore=3480 newBalance=31.287536619 oldBalance=31.289152311 percentChange="-0.00516%" percentChangeSinceStart="-2.23451%" prefix=validator pubKey=0xa03b7ee28c86 startBalance=32.002639275
...
time="2023-08-20 18:43:38" level=info msg="Attestation schedule" attesterDutiesAtSlot=1 prefix=validator pubKeys=[0xb837c064da51] slot=7144416 slotInEpoch=0 totalAttestersInEpoch=5
...
time="2023-08-20 18:43:43" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = the node is currently optimistic and cannot serve validators" prefix=validator pubKey=0xb837c064da51 slot=7144416
...
time="2023-08-20 18:46:47" level=info msg="Submitted builder validator registration settings for custom builders" prefix=validator
time="2023-08-20 18:47:07" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = the node is currently optimistic and cannot serve validators" prefix=validator pubKey=0xb4a147fbea40 slot=7144433
time="2023-08-20 18:48:19" level=error msg="Could not request attestation to sign at slot" error="rpc error: code = Unavailable desc = the node is currently optimistic and cannot serve validators" prefix=validator pubKey=0xa03b7ee28c86 slot=7144439

I haven’t done any advanced customizations. I tried rebooting. I also tried dropping the Geth and Prysm DBs and resyncing from scratch (with checkpoint for Prysm).

Help would be greatly appreciated.

Core DAppNode Packages versions

  • bind.dnp.dappnode.eth: 0.2.6
  • core.dnp.dappnode.eth: 0.2.76
  • dappmanager.dnp.dappnode.eth: 0.2.71, commit: 05d52e40
  • https.dnp.dappnode.eth: 0.2.1
  • ipfs.dnp.dappnode.eth: 0.2.19
  • wifi.dnp.dappnode.eth: 0.2.8
  • wireguard.dnp.dappnode.eth: 0.1.2

System info

  • dockerComposeVersion: 1.25.0
  • dockerServerVersion: 20.10.5+dfsg1
  • dockerCliVersion: 20.10.5+dfsg1
  • os: debian
  • versionCodename: bullseye
  • architecture: amd64
  • kernel: 5.10.0-18-amd64
  • Disk usage: 22%

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.