eth_exe_sync_is_syncing is being set to 1 while there's no indication of it in logs

[concentricspheres]

eth_exe_sync_is_syncing is intermittently changing to 1 in one of our instances, but Execution client logs show no issues or falling behind.

Software:

• Lighthouse v4.2.0
• Erigon 2.44.0-stable

Both clients have been running for ~9 days and the intermittent issue surfaced recently.

Can you please provide details on how the eth_exe_sync_is_syncing metric is calculated so we can check the data on the client and figure out if it's actually an issue with the client or with ethereum-metrics-exporter?

[samcm]

Thanks for the issue :)

That metric is derived here: https://github.com/ethpandaops/ethereum-metrics-exporter/blob/main/pkg/exporter/execution/jobs/syncstatus.go#L127-L165

The calculation is pretty straight forward:

• Call eth_syncing
• If the response returned an error -> Do nothing
• If the response didn't error and the body is empty -> assume the client isn't syncing
• If the response didn't error and the body isn't empty -> assume the client is syncing and set metrics accordingly

Do you have the values for eth_exe_sync_starting_block, eth_exe_sync_current_block and eth_exe_sync_highest_block from around those times? Might help with diagnosing with one 🙏