lnd: [bug]: Unable to retrieve initial bootstrap peers: no addresses found

Background

Unable to sync to graph

Your environment

0.15.2
Alpine 3.12 (Docker container)
Bitcoin 23.0.0
embassyOS

Steps to reproduce

Install LND and start the service. LND syncs to chain and then us unable to sync to graph, complaining about bootstrap peers being unavailable. It is possible to ping the bootstrap nodes directly from the LND container when this is happening.

[INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
[INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
[ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found

nslookup from the container:

# nslookup lseed.bitcoinstats.com

Server:    127.0.0.11
Address:  127.0.0.11:53

Non-authoritative answer:
Name:  lseed.bitcoinstats.com
Address: 2001:41d0:701:1100::1eb

Non-authoritative answer:
Name:  lseed.bitcoinstats.com
Address: 178.128.199.185
Name:  lseed.bitcoinstats.com
Address: 18.234.160.51
Name:  lseed.bitcoinstats.com
Address: 68.96.103.79
Name:  lseed.bitcoinstats.com
Address: 93.241.53.3
Name:  lseed.bitcoinstats.com
Address: 34.254.183.158
Name:  lseed.bitcoinstats.com
Address: 185.45.113.201
Name:  lseed.bitcoinstats.com
Address: 98.127.88.124
Name:  lseed.bitcoinstats.com
Address: 3.236.75.212
Name:  lseed.bitcoinstats.com
Address: 84.83.38.49
Name:  lseed.bitcoinstats.com
Address: 100.99.8.64
Name:  lseed.bitcoinstats.com
Address: 166.70.145.151
Name:  lseed.bitcoinstats.com
Address: 109.117.184.99
Name:  lseed.bitcoinstats.com
Address: 172.81.182.165
Name:  lseed.bitcoinstats.com
Address: 24.17.22.37
Name:  lseed.bitcoinstats.com
Address: 81.170.132.97
Name:  lseed.bitcoinstats.com
Address: 98.210.161.137
Name:  lseed.bitcoinstats.com
Address: 86.88.77.5
Name:  lseed.bitcoinstats.com
Address: 35.238.153.25
Name:  lseed.bitcoinstats.com
Address: 89.142.136.179
Name:  lseed.bitcoinstats.com
Address: 18.184.210.20
Name:  lseed.bitcoinstats.com
Address: 192.168.1.150
Name:  lseed.bitcoinstats.com
Address: 90.224.117.204
Name:  lseed.bitcoinstats.com
Address: 188.251.251.232
Name:  lseed.bitcoinstats.com
Address: 170.75.163.38
Name:  lseed.bitcoinstats.com
Address: 197.237.170.19

Adding a node manually does not solve

Expected behaviour

Sync to graph

Actual behaviour

Fails to bootstrap / sync to graph indefinitely (after days of testing)

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 31 (2 by maintainers)

Most upvoted comments

nodes.lightning.directory does not exist at all, on any dns server i can find.

Yeah, that was a problem with the LSEED installation. It’s fixed now and I get results for both A and SRV records.

it appears that the nodes I tried have all been very low-quality

Because of the first DNS (nodes.lightning.directory, run by LL) failing, lnd used the second DNS (lseed.bitcoinstats.com run by @cdecker IIRC). So I can’t speak to the quality of the nodes returned there. Maybe that service needs to be restarted as well to refresh its list of nodes?

This seems like a centralization issue,

I agree. It would be good for more people to run their own instance of LSEED. You can configure custom LSEED servers by setting --bitcoin.dnsseed=. Maybe that’s something you want to consider for embassy-os?

I can’t really speak to the other points, but hope this helps to resolve your issue for now.

guggero on Nov 1, 2022

@guggero haha well, whatever you did, nslookup nodes.lightning.directory returns results successfully now, and our fresh nodes are no longer having problems syncing the graph 😃

chrisguida on Nov 2, 2022

it works fine when I use bitcoind directly, and works fine when I use Neutrino

islandbitcoin on Nov 1, 2022

Seems like with the 15.4 update, we uncovered another, related issue… maybe?

2022-11-01T13:24:39-04:00  2022-11-01 17:24:39.782 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2022-11-01T13:24:39-04:00  2022-11-01 17:24:39.805 [INF] INVC: New invoice subscription client: id=1
2022-11-01T13:24:39-04:00  2022-11-01 17:24:39.826 [INF] LTND: Waiting for chain backend to finish sync, start_height=761293
2022-11-01T13:24:40-04:00  2022-11-01 17:24:40.634 [INF] LNWL: Started rescan from block 0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f (height 761248) for 7 addresses
2022-11-01T13:24:41-04:00  2022-11-01 17:24:41.083 [ERR] LNWL: Unable to complete chain rescan: -1: allocation of oversized vector: requested 12000072, maximum 4000000
2022-11-01T13:24:44-04:00  2022-11-01 17:24:44.719 [INF] INVC: New invoice subscription client: id=2

islandbitcoin on Nov 1, 2022

About the quality of the bitcoinstats.com results, I’ll look into it. But ideally you’d use SRV requests to get addresses for specific nodes.

cdecker on Nov 1, 2022

@kn0wmad any updates on this?

Hitting onions is no problem, and the node is able to sync to graph when adding peers manually. We don’t see any reason that the bootstrap peers would be unable to connect - they are fully reachable by the network. Could there be issues with the boostrap nodes?

kn0wmad on Oct 27, 2022