Skip to content

Increased 'WARN' rate due to 'Single block lookup failed' #2446

@gotzl

Description

@gotzl

Description

My two lighthouse beacon nodes frequently report a warning in the logs:

Jul 10 23:21:40.821 WARN Single block lookup failed              outcome: Err(WouldRevertFinalizedSlot { block_slot: Slot(1594432), finalized_slot: Slot(1594528) }), service: sync

I am not sure what it means and what I can/should do to get rid of it.

Version

v1.4.0-3b600ac

Present Behaviour

I run two lighthouse beacon nodes on two separate devices. I monitor the warn rate of these instances, which is usually ~1/h. However, since approx 10.07., both instances report a significantly higher warn rate (~20/h). Most (or all) of the warnings are messages as quoted above.
I cannot classify this warning nor do I know how to counteract. A google search didn't help, so I would like to ask here for enlightenment.

The nodes are on mainnet, I use openethereum for eth1.

Expected Behaviour

No warnings should be logged.

Steps to resolve

Unknown.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions