lnd: [bug]: "edge not found" for local channel

Background

A peer opened a channel to my node. This channel is listed in lncli listchannels. However, lncli getchaninfo X shows an error (with X being the channel ID):

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

According to lncli listchannels, this appears to be a regular (inactive) channel. It’s not private, it has “remote_constraints”, there’s an ID in “alias_scids”. It’s not a zero-conf channel. Strangely, there are two incoming HTLCs already, where “forwarding_channel” is set to 0. Currently, the channel is inactive, but it has been active before.

When reconnecting to the peer, I get:

[INF] PEER: Peer(xxx): loading ChannelPoint(xxx:1)
[WRN] PEER: Peer(xxx): Unable to find our forwarding policy for channel xxx:1, using default values

In my logs I also see:

[INF] RPCS: channel: xxx:1 not found by channel event store

I’d be happy to provide further information.

Your environment

lnd v0.15.5-beta
Linux server 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux
bitcoind v24.0.1

About this issue

Original URL
State: open
Created 2 years ago
Comments: 16 (5 by maintainers)

Commits related to this issue

return unknown policy instead of returning error if edge for local channel cannot be found see https://github.com/lightningnetwork/lnd/issues/7261 — committed to C-Otto/lnd-manageJ by C-Otto a year ago

Most upvoted comments

We’re running into this also, on nodes running 0.16.0

litch on Apr 20, 2023

I think this is distinct from https://github.com/lightningnetwork/lnd/issues/7229 since this was not a zero-conf channel

Crypt-iQ on Jan 5, 2023

For those who recently experienced this bug, pls can you try updated to 0.16.1-beta.rc1 to see if that fixes your issue?

It might be that your issue is the same as this user’s issue which is distinct from this issue even though it throws the same error message. That user’s issue was fixed in 0.16.1-beta.rc1

ellemouton on Apr 21, 2023