Closed a455bcd9 closed 2 years ago
You're trying to connect to peers that seem to no longer exist. Looks like you're even trying to connect to a testnet node (from the DNS name) using your mainnet (?) lnd
instance. You should use neutrino.connect
instead of neutrino.addpeer
to allow it to properly seek out other peers.
Hi, Thanks for your answer.
I have bitcoin.mainnet=1
in my lnd.conf file
and I'm running on mainnet according to lncli getinfo
) so I don't understand why my node is trying to connect to a testnet node. What could be the reason?
Also: why should I use neutrino.connect
instead of neutrino.addpeer
as recommended there: https://github.com/alexbosworth/run-lnd ?
Thanks for any help you can provide.
FYI: I've been told by another experienced neutrino user that it is normal for neutrino to try to connect to a testnet node using the mainnet instance.
Background
I was running v0.13.3-beta with neutrino using the using ThunderCloud on AWS ( https://github.com/a5an0/ThunderCloud/blob/master/lib/configure-node.sh but with AMD instead of ARM). I did not update lnd to fix the Taproot-related bug in time. Some of my channels got closed. I checked and realized I didn't have enough space on my disk. I doubled the disk size yesterday. This morning I updated lnd to v0.14.0-beta. My node cannot sync.
Your environment
lnd
: "0.14.0-beta"uname -a
on *Nix): Operating System: Amazon Linux 2 // Kernel: Linux 4.14.248-189.473.amzn2.x86_64btcd
,bitcoind
, or other backend: neutrinoSteps to reproduce
I don't know.
Expected behaviour
lncli getinfo
should show "synced_to_chain" and "synced_to_graph" at "true".Actual behaviour
"synced_to_chain" and "synced_to_graph" are both are "false".
"block_height": 709784
Some of channels are shown as closed on 1ml but still open when I do
lncli listchannels
.When I launch
lnd
manually I keep getting the following message: