Node can't find peers

[rampall]

Describe the bug

I have a lodestar gnosis client running on Dappnode that seems to never find peers!

Mar-13 21:41:37.521[]                 info: Searching peers - peers: 0 - slot: 14274551 - head: 14271456 0x0338…ec0b - exec-block: syncing(32912908 0xc11f…) - finalized: 0x7a32…13b7:891964
Mar-13 21:41:38.375[chain]           debug: Skipping PrepareNextSlotScheduler - head slot is too behind current slot nextEpoch=892160, headSlot=14271456, clockSlot=14274551
Mar-13 21:41:40.021[chain]         verbose: Clock slot slot=14274552
Mar-13 21:41:41.981[rest]            debug: Req req-4ez 172.33.1.7 getSyncingStatus
Mar-13 21:41:41.981[rest]            debug: Exec req-4ez 172.33.1.7 getSyncingStatus
Mar-13 21:41:41.982[rest]            debug: Res req-4ez getSyncingStatus - 200
Mar-13 21:41:41.982[rest]            debug: Req req-4f0 172.33.1.7 getPeerCount
Mar-13 21:41:41.982[rest]            debug: Exec req-4f0 172.33.1.7 getPeerCount
Mar-13 21:41:42.090[rest]            debug: Req req-4f1 172.33.1.7 getSyncingStatus
Mar-13 21:41:42.090[rest]            debug: Exec req-4f1 172.33.1.7 getSyncingStatus
Mar-13 21:41:42.090[rest]            debug: Res req-4f1 getSyncingStatus - 200
Mar-13 21:41:42.097[rest]            debug: Req req-4f2 172.33.1.7 getPeerCount
Mar-13 21:41:42.099[rest]            debug: Exec req-4f2 172.33.1.7 getPeerCount
Mar-13 21:41:42.110[rest]            debug: Res req-4f0 getPeerCount - 200
Mar-13 21:41:42.136[rest]            debug: Res req-4f2 getPeerCount - 200
Mar-13 21:41:42.504[]                 info: Searching peers - peers: 0 - slot: 14274552 - head: 14271456 0x0338…ec0b - exec-block: syncing(32912908 0xc11f…) - finalized: 0x7a32…13b7:891964
Mar-13 21:41:43.355[chain]           debug: Skipping PrepareNextSlotScheduler - head slot is too behind current slot nextEpoch=892160, headSlot=14271456, clockSlot=14274552

Expected behavior

lodestar should find and connect to peers

Steps to reproduce

No response

Additional context

Dappnode Lodestar Gnosis version 0.1.11 Upstream Lodestar v1.17.0

uname -a
Linux cc444ac1f3a7 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:55:07 UTC 2024 x86_64 Linux

Operating system

Linux

Lodestar version or commit hash

1.17.0

[rampall]

somewhat similar to this issue that has been closed

• https://github.com/ChainSafe/lodestar/issues/4657

[nflaig]

I tested the latest Lodestar version locally and it syncs fine for me

./lodestar beacon --network gnosis --eth1 false --execution.engineMock --checkpointSyncUrl https://checkpoint.gnosischain.com/
...
Mar-14 15:43:27.500[]                 info: Synced - slot: 14286813 - head: (slot -1) 0xa0b4…a079 - exec-block: syncing(32927515 0x825c…) - finalized: 0xb7e8…e7d2:892923 - peers: 20
Mar-14 15:43:32.500[]                 info: Synced - slot: 14286814 - head: 0x916e…4e20 - exec-block: syncing(32927517 0x8ac1…) - finalized: 0xb7e8…e7d2:892923 - peers: 20
Mar-14 15:43:37.501[]                 info: Synced - slot: 14286815 - head: 0x31d5…4987 - exec-block: syncing(32927518 0xbe47…) - finalized: 0xb7e8…e7d2:892923 - peers: 21
...

I don't see what could be the issue on your end based on the logs but there are problems here and there where people report that their client is not able to find peers, and a lot of times it's related to some specifics with their setup.

Might be best to investigate this further on our discord in the #lodestar-help channel.

There are two things you could try out

• delete the data of the Lodestar package and restart it, this cleans up the peer store (based on some older issues this might help)
• or try another client and see if you get it to work on your machine, since you are on dappnode, switching clients should be really easy

Feel free to ping me on discord, if you have any follow up questions or more data to look at