Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove warning sync_committe lighthouse logs #7

Open
ferranbt opened this issue Jul 30, 2024 · 1 comment
Open

Remove warning sync_committe lighthouse logs #7

ferranbt opened this issue Jul 30, 2024 · 1 comment
Labels
good first issue Good for newcomers

Comments

@ferranbt
Copy link
Collaborator

Remove and silence the insufficient peers error from Lighthouse. We do not care about them because we are running a single beacon node.

Jul 30 15:01:11.026 WARN Could not publish message               kind: beacon_attestation_3, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.030 WARN Could not publish message               kind: sync_committee_2, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.033 WARN Could not publish message               kind: sync_committee_1, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.035 WARN Could not publish message               kind: sync_committee_3, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.037 WARN Could not publish message               kind: sync_committee_0, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.039 WARN Could not publish message               kind: sync_committee_0, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.040 WARN Could not publish message               kind: sync_committee_3, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.042 WARN Could not publish message               kind: sync_committee_1, error: InsufficientPeers, service: libp2p
Jul 30 15:01:11.044 WARN Could not publish message               kind: sync_committee_2, error: InsufficientPeers, service: libp2p
@ferranbt ferranbt added the good first issue Good for newcomers label Jul 30, 2024
@meldsun0
Copy link

meldsun0 commented Aug 26, 2024

After taking a look to this issue and double checking it on Lighthouse's discord; At the moment, to stop seeing these logs, a few nodes should be run.
"At the moment the logs will be there when the connected peers are low, even with the flag --target-peers 0 set. See: sigp/lighthouse#2094 (comment)"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants