Skip to content

Commit 54b58fd

Browse files
committed
Log out response status when we hit PayloadIdUnavailable (#3190)
## Issue Addressed @z3n-chada is currently getting a `PayloadIdUnavailable` error when connecting lighthouse to Erigon and it's difficult to discern why so this just logs out the response status from the EE when we hit an `PayloadIdUnavailable` error Co-authored-by: realbigsean <[email protected]>
1 parent 695f415 commit 54b58fd

File tree

1 file changed

+10
-7
lines changed
  • beacon_node/execution_layer/src

1 file changed

+10
-7
lines changed

beacon_node/execution_layer/src/lib.rs

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -660,25 +660,28 @@ impl ExecutionLayer {
660660
suggested_fee_recipient,
661661
};
662662

663-
engine
663+
let response = engine
664664
.notify_forkchoice_updated(
665665
fork_choice_state,
666666
Some(payload_attributes),
667667
self.log(),
668668
)
669-
.await
670-
.map(|response| response.payload_id)?
671-
.ok_or_else(|| {
669+
.await?;
670+
671+
match response.payload_id {
672+
Some(payload_id) => payload_id,
673+
None => {
672674
error!(
673675
self.log(),
674676
"Exec engine unable to produce payload";
675677
"msg" => "No payload ID, the engine is likely syncing. \
676678
This has the potential to cause a missed block \
677679
proposal.",
680+
"status" => ?response.payload_status
678681
);
679-
680-
ApiError::PayloadIdUnavailable
681-
})?
682+
return Err(ApiError::PayloadIdUnavailable);
683+
}
684+
}
682685
};
683686

684687
engine

0 commit comments

Comments
 (0)