-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Open
Labels
bugUnintended code behaviourUnintended code behaviourp2pCode related to the peer-to-peer behaviourCode related to the peer-to-peer behaviour
Description
Pre-Submission Checklist
- I have searched the existing issues and believe this is a new bug.
- I am not asking a question about how to use lnd, but reporting a bug (otherwise open a discussion).
LND Version
v0.19.3
LND Configuration
tbd if relevant
Backend Version
v29.0.0
Backend Configuration
tbd if relevant
OS/Distribution
debian
Bug Details & Steps to Reproduce
I restarted my lnd node. It was pretty fast (appr. 2 minutes until SERVER_ACTIVE). The channels were therefore still enabled on my peer's side, which was never the case during longer restarts. In the meantime, there were even incoming forwards on one channel. But suddenly, about 15 minutes later, almost all channels were disabled for about 3 minutes. On a peer using eclair, the channel was not disabled, so I suspect an lnd issue on the part of my peers.
Since I see no reason for channels to be disabled with a 15-minute gap, I classify this behavior as a bug.
Expected Behavior
Channels should stay online in such a case.
Debug Information
tbd if relevant
Environment
tbd if relevant
Metadata
Metadata
Assignees
Labels
bugUnintended code behaviourUnintended code behaviourp2pCode related to the peer-to-peer behaviourCode related to the peer-to-peer behaviour
Type
Projects
Status
In review