LND: Syncing to graph takes forever

Services Support
1

Hey

The following is bothering me since at least a day. Restarts and so on do not fix the issue.

Any ideas? It syncs to graph for many many hours.

image
image754Ă—836 28.5 KB

2

Do you have ample resources. Enough space, fast disk, etc.

3

Hi, yeah I have an Asus NUC 13 Pro with 16 GB ram, 4TB M2 SSD and i3 processor.

All other services work well. LND has this message for over one day. That’s not normal, right?

I tried the actions that reset things and even uninstalled and restarted several times. Or should I simply give it more time?

Thanks!

4

Usually giving it more time is the right thing to do.

Is this the first time you are starting LND after the initial block download of Bitcoin Core? If so, then it is normal for it to take some time.

How long has the LND service been in this state?

5

I’m interested in the resolution to this issue as well. Yesterday I noticed that my server had crashed, so I rebooted the machine. I was able to restart Bitcoin Core and Elctrs, but LND is stuck in in a loop of “Starting…; Running; and then Starting…” again. The LND log indicates that there’s an issue with opening the graph database, specifically with a signature size that exceeds the max allowed size. Is it possible that this got corrupted when the server crashed?

1 Like
6

You are having a different issue. That is what we call a “Starting Loop”.

Is this only happening to LND? Any other services having the same symptom?

Check the LND service logs for any specific errors that come up and can give us more information.

The usual solution to this state is to run a “System Rebuild” which won’t delete or change anything. Just rebuilds the containers.

You can find this option under in your server’s UI under System → Power → System Rebuild

Keep in mind that It may take up to 70 minutes to complete. During this time, you will lose all connectivity to your server.

7

Thank you for the reply. LND is the only service with this issue. The relevant part of the LND log states “LTND: unable to open graph DB: ReadVarBytes; sig is larger than the max allowed size [count 179, max 80]”. I will attempt system rebuild now.

8

Unfortunately, the system rebuild did not resolve my issue.

9

For about a day since the last restart. I will let it run, but meanwhile, I installed c-lightning and that one took literally 5 minutes from click on install until fully healthy.

10

Can you start a new topic please. For clarity, let’s not conflate these two issues. I’ll keep an eye out for ya!

11

This sounds like it could be a data corruption issue. Are you running the latest version of LND?

In any case, this definitely appears to be an issue with LND itself rather than StartOS or lnd-startos. The LL team recommended opening an issue on their GH.

Alternatively, this problem with the graph might be resolved with chantools similar to what the user had to do here.

12

Unless the log indicates a problem, you can proceed as you’d like. The spinner does not necessarily indicate a problem. If you suspect a problem with LND you can DM me the log. I’d be happy to take a look.

13

Sorry for any confusion I may have caused. I’ll create a new topic when I get home this evening. @ Tennis, I hope your issue is resolved soon.

1 Like
14

It’s still syncing and let me tell you: This shit will never finish.

Here is the most recent log. Something about initial addresses not found:

2025-01-09T21:20:51+01:00  2025-01-09 20:20:51.543 [INF] UTXN: Attempting to graduate height=878530: num_kids=0, num_babies=0
2025-01-09T21:21:15+01:00  2025-01-09 20:21:15.806 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:21:17+01:00  2025-01-09 20:21:17.911 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:21:17+01:00  2025-01-09 20:21:17.912 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2025-01-09T21:22:17+01:00  2025-01-09 20:22:17.912 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:22:20+01:00  2025-01-09 20:22:20.139 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:22:20+01:00  2025-01-09 20:22:20.140 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2025-01-09T21:23:20+01:00  2025-01-09 20:23:20.140 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:23:20+01:00  2025-01-09 20:23:20.141 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:23:23+01:00  2025-01-09 20:23:23.231 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2025-01-09T21:24:23+01:00  2025-01-09 20:24:23.233 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:24:23+01:00  2025-01-09 20:24:23.233 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:24:26+01:00  2025-01-09 20:24:26.029 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2025-01-09T21:25:26+01:00  2025-01-09 20:25:26.030 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:25:26+01:00  2025-01-09 20:25:26.031 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:25:28+01:00  2025-01-09 20:25:28.198 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2025-01-09T21:26:28+01:00  2025-01-09 20:26:28.199 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:26:28+01:00  2025-01-09 20:26:28.201 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:26:30+01:00  2025-01-09 20:26:30.345 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2025-01-09T21:27:30+01:00  2025-01-09 20:27:30.346 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2025-01-09T21:27:32+01:00  2025-01-09 20:27:32.499 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2025-01-09T21:27:32+01:00  2025-01-09 20:27:32.500 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found```
15

Hi tennis

Have you tried adding a peer manually. You can do that using RTL. service. That should help to bootstarp your LND. Also try to open LND config and click save.

1 Like
16

II just started my “Server Pure” server, and it’s been 2 days already and LND has not finished “Syncing to graph”.
On average, how many days does it take to complete?

I looked at the logs and it’s giving this error:
“ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found”
What could be the problem?

Thanks and happy new year to all,

1 Like
17

Welcome, CryptoHead!

It’s great to have you here. Let’s tackle your issue.

The LND “Syncing to graph” process can vary in time, depending on your server’s specs and internet connection. For most setups, it should take anywhere between a few hours to a couple of days. However, the error you mentioned, “Unable to retrieve initial bootstrap peers: no addresses found”, indicates that LND is having trouble finding peers to sync with.

Here are a few steps to try:

  1. Add a Peer Manually Using RTL Service for LND
    Open the RTL (Ride The Lightning) interface and use it to manually add a well-connected peer.

  2. Check Your Internet Connection
    Ensure your server has a stable internet connection and no firewall is blocking LND’s ports.

  3. Reboot LND or Restart the Server
    Sometimes, restarting LND can help resolve sync issues. If that doesn’t work, reboot the entire server.

  4. Monitor Logs Closely
    Keep an eye on the logs for new errors or progress indicators.

If the problem persists after trying these steps, let us know, and we’ll dig deeper. You’re on the right path! :rocket:

1 Like
18

Um, I think the solution that actually helped, got deleted?? Pretty sure I read it here yesterday and followed.

A guy said “save config and restart node”. I did that, didn’t seem to work. Then I enabled “all traffic over TOR” in the config of LND, restart, put the setting back. And somehow it synced some minutes after.

This is probably not a solution… But anyways, it works now. Maybe that helps someone, but it’s so random, I kinda doubt it.

19

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.