Skip to content

[bug]: Huge number of inactive channels after updating to lnd v0.15.2-beta #7013

Closed

Description

@peername

Background

Most of my channels are still inactive hours after the update to lnd v0.15.2-beta

This is repeated over and over in the logs:

2022-10-10 21:09:40.796 [WRN] HSWC: ChannelLink(3abecbc8d5b5dd84d23c88fe4562e6ba16a9d32b9e4e8cd857f5c5db0c022c7c:0): insufficient bandwidth to route htlc: 12503837 mSAT is larger than 2122 mSAT
2022-10-10 21:09:40.796 [ERR] HSWC: insufficient bandwidth to route htlc
2022-10-10 21:09:40.796 [ERR] HSWC: Unhandled error while reforwarding htlc settle/fail over htlcswitch: insufficient bandwidth to route htlc

Your environment

  • version of lnd: v0.15.2-beta
  • which operating system (uname -a on *Nix): Ubuntu Server 20.04
  • version of btcd, bitcoind, or other backend: bitcoind 23

Activity

  1. sputn1ck commented on Oct 10, 2022

    @sputn1ck
    Collaborator

    I think the number of inactive channnels could in the expected range 12 hours after release of the update, probably not everyone is quick in updating. For me roughly 50% are still inactive.

    I notice the same error messages repeating as you, gonna check back later what the cause may be.

  2. Roasbeef commented on Oct 10, 2022

    @Roasbeef
    Member

    That's a log where someone is trying to route over a channel but it has insufficient balance to carry it. Which is sort of expected if someone is trying to probe.

  3. Roasbeef commented on Oct 10, 2022

    @Roasbeef
    Member

    Also if your node on clearnet, tor, or hybrid?

  4. peername commented on Oct 11, 2022

    @peername
    Author

    hybrid

  5. added
    p2pCode related to the peer-to-peer behaviour
    and removed
    bugUnintended code behaviour
    on Oct 12, 2022
  6. sputn1ck commented on Oct 12, 2022

    @sputn1ck
    Collaborator

    For me about 85% of channels are active again, whats your status?

  7. sputn1ck commented on Oct 14, 2022

    @sputn1ck
    Collaborator

    Moving this issue to a discussion as it does not appear to be a bug

  8. locked and limited conversation to collaborators on Oct 14, 2022
  9. converted this issue into a discussion #7038 on Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    p2pCode related to the peer-to-peer behaviour

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions