lnd: [bug]: Unknown desc = edge not found

Background

Seems like my LND will randomly not be able to find active channels it has. I do lncli listchannels and the channel shows up as active, but then when I do lncli getchaninfo with the id, it says edge not found.

This has happened a lot, especially when the other node is a Tor node with only 1 total channel.

lncli version 0.15.1-beta commit=v0.15.1-beta

Your environment

lncli version 0.15.1-beta commit=v0.15.1-beta
Linux Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
bitcoind backend Bitcoin Core version v22.0.0

Steps to reproduce

I don’t know how to reproduce, it’s flaky.

Example:

lncli listchannels and i see the following entry (among my 800+ other channels)

{
            "active": true,
            "remote_pubkey": "027d92cde72c29ce5a5ae11d91c7ba84245e7917dfd20f1f96ad7f3ea54836a3ad",
            "channel_point": "f7debbfd729a234f4e37235a495e2103d9c1636cabb9e960223b450bd9359954:1",
            "chan_id": "832475437786923009",
            "capacity": "25750000",
            "local_balance": "25011680",
            "remote_balance": "736777",
            "commit_fee": "883",
            "commit_weight": "1116",
            "fee_per_kw": "785",
            "unsettled_balance": "0",
            "total_satoshis_sent": "0",
            "total_satoshis_received": "25011680",
            "num_updates": "373",
            "pending_htlcs": [
            ],
            "csv_delay": 2016,
            "private": false,
            "initiator": false,
            "chan_status_flags": "ChanStatusDefault",
            "local_chan_reserve_sat": "257500",
            "remote_chan_reserve_sat": "257500",
            "static_remote_key": false,
            "commitment_type": "ANCHORS",
            "lifetime": "43603",
            "uptime": "43048",
            "close_address": "",
            "push_amount_sat": "0",
            "thaw_height": 0,
            "local_constraints": {
                "csv_delay": 2016,
                "chan_reserve_sat": "257500",
                "dust_limit_sat": "354",
                "max_pending_amt_msat": "25492500000",
                "min_htlc_msat": "1",
                "max_accepted_htlcs": 483
            },
            "remote_constraints": {
                "csv_delay": 2016,
                "chan_reserve_sat": "257500",
                "dust_limit_sat": "354",
                "max_pending_amt_msat": "25492500000",
                "min_htlc_msat": "1",
                "max_accepted_htlcs": 483
            },
            "alias_scids": [
            ],
            "zero_conf": false,
            "zero_conf_confirmed_scid": "0"
        },

but then doing lncli getchaninfo 832475437786923009 immediately alfter, i get:

[lncli] rpc error: code = Unknown desc = edge not found

logs from lnd:

[ERR] RPCS: [/lnrpc.Lightning/GetChanInfo]: edge not found

If i restart the node, it fixes it. But I can’t be restarting the node all the time.

About this issue

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

Most upvoted comments

Still happens on most recent release.

2023-11-02 14:13:24.024 [ERR] RPCS: [/lnrpc.Lightning/GetChanInfo]: edge not found

dskvr on Nov 2, 2023

The remote peer will forget the channel after 2 weeks (2016 blocks). So yes, unfortunately force closing is the only option. We’ll try to make this more clear with this: https://github.com/lightningnetwork/lnd/issues/7434

guggero on Mar 27, 2023

Updated to 0.16.1.rc1, the channels works! 🥳 Thank’s @ellemouton

bota87 on Apr 19, 2023

Hmm… I was also able to reproduce that a couple of times locally on a regtest setup… Will see if I can get that error again and share some context. Although I was experimenting with 0-conf channels so could be same bug but different origin.

GeorgeTsagk on Oct 6, 2022