Beacon and geth nodes not syncing as expected about prysm

[nisdas]

@Sreeram1993 This is an issue with your geth node:

time="2024-04-05 06:04:16" level=warning msg="Skip processing batched blocks" error="could not process block in batch: timeout from http.Client: received an undefined execution engine error" prefix=initial-sync

Its constantly timing out when processing payloads

[nisdas]

Its possible your geth node is stressed/under provisioned if it constantly is unable to process payloads. The logs from prysm indicate that geth can't process in time

[Sreeram1993]

@Sreeram1993 This is an issue with your geth node:

time="2024-04-05 06:04:16" level=warning msg="Skip processing batched blocks" error="could not process block in batch: timeout from http.Client: received an undefined execution engine error" prefix=initial-sync

Its constantly timing out when processing payloads

Any idea what could be causing this ? Even geth blames beacon node

INFO [04-05|06:09:50.169] Imported new potential chain segment number=19,582,764 hash=0fd397..960504 blocks=1 txs=254 mgas=29.615 elapsed=39.239s mgasps=0.755 age=16h28m15s triedirty=0.00B
WARN [04-05|06:11:15.469] Beacon client online, but no consensus updates received in a while. Please fix your beacon client to follow the chain!
WARN [04-05|06:16:15.507] Beacon client online, but no consensus updates received in a while. Please fix your beacon client to follow the chain!

[prestonvanloon]

Closing this since it seems like the problem is identified. If you are still having issues, please reply to this issue or open another one.