You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, my node works very well after a new reinstallation without the chan.backup file(Lost), just with the seed phrase and I was able to recover my on-chain funds.
For the off-chain, I lost 3 channels, so they are zombie channels?
I reconnected to a node with which I had opened a channel but i noted some suspicious lines:
[ERR] PEER: Peer (xxxxx): resend failed: unable to fetch channel sync messages for peer xxxx@xxx:xxxx: unable to find closed channel summary
[INF] PEER: Peer (xxxxx): negociated chan series queries
[INF] PEER: Peer(xxxxx): unable to read message from peer: read next header: EOF
This is probably related to #8077 (and lightninglabs/chantools#89), let's keep the discussion there to keep information in one place (I will answer on #8077). Feel free to reopen otherwise.
I also forgot to specify that I can't delete this peer (lncli disconnnect) it looks like a bug, maybe because of the old channel (now 🧟♀️🧟♂️chan) open with it? Now I wonder if LND keeps traces? It's the same node on the same local network. I had Clean All my hard drive and I reinstalled without off-chain backup
Hi, my node works very well after a new reinstallation without the chan.backup file(Lost), just with the seed phrase and I was able to recover my on-chain funds.
For the off-chain, I lost 3 channels, so they are zombie channels?
I reconnected to a node with which I had opened a channel but i noted some suspicious lines:
[ERR] PEER: Peer (xxxxx): resend failed: unable to fetch channel sync messages for peer xxxx@xxx:xxxx: unable to find closed channel summary
[INF] PEER: Peer (xxxxx): negociated chan series queries
[INF] PEER: Peer(xxxxx): unable to read message from peer: read next header: EOF
Thank you.
Sincerely,
Your environment
LND V0.17.0-beta tor/clearnet
Btc core v25.1
Rasp 4 8go
The text was updated successfully, but these errors were encountered: