unable to start server: edge not found since LND 0.18.5
#9629
Answered
by
yyforyongyu
AaronDewes
asked this question in
Troubleshooting
-
|
Since upgrading to LND 0.18.5, LND is no longer starting with the following error: Is there a way to fix this, ideally without loosing my channels? |
Beta Was this translation helpful? Give feedback.
Answered by
yyforyongyu
Mar 25, 2025
Replies: 2 comments 10 replies
-
|
Hmm, seems to be an issue in the gossip code: |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Hi! I have LND running in Kubernetes and it seems like after 32 automated restarts, it fixed itself. However, after upgrading to |
Beta Was this translation helpful? Give feedback.
-
|
Could you turn |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Although the gossiper logged an error, it didn't shut down the node. Checking the log closely, we've def reached this line, Line 2495 in 3351a17 Since we have the log 2025-03-25 09:11:49.045 [INF] CMGR: Server listening on [::]:9735.
It also def didn't reach this line because we see no log saying Line 2635 in 3351a17 I suspect the error is returned from one of these methods, Lines 2534 to 2554 in 3351a17 Do you think you can patch your node with #9643 so we know where the error is coming from? |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
At the moment, it is working again after a few automated restarts. I'd like to leave it running for a while to check if it crashes by itself, but I'll later restart again (with your patch) to check if the crashes are still happening (I assume they do, because it happened again after the last restart) |
Beta Was this translation helpful? Give feedback.
-
|
Cool thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I restarted LND with your patch, new logs: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the logs! It's weird that the edge cannot be found in the first place, nonetheless the startup process should not be blocked. I updated #9643 to fix the issue, could you apply the patch and confirm it does fix the issue? |
Beta Was this translation helpful? Give feedback.
Answer selected by
AaronDewes
-
|
I can confirm the issue is fixed by this patch. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
It appears the initial root cause was a DNS issue, and I'm not sure if that caused the "edge not found", but it seems likely to me. Still, the patch may be a good idea because after it, I got actually useful error messages. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for the logs! It's weird that the edge cannot be found in the first place, nonetheless the startup process should not be blocked. I updated #9643 to fix the issue, could you apply the patch and confirm it does fix the issue?