lncli feereport fails with error "no policy for outgoing channel" from a previously cooperatively closed channel, and open channels

[bretton]

Background

I'm having trouble with channels being closed, and then I get an error with lncli feereport as follows:

@lnd:~$ lncli feereport
[lncli] rpc error: code = Unknown desc = no policy for outgoing channel REDACTED

and the log has

[ERR] RPCS: [/lnrpc.Lightning/FeeReport]: no policy for outgoing channel REDACTED

if I examine the channel:

$ lncli getchaninfo REDACTED
{
    "channel_id": "REDACTED",
    "chan_point": "0000000000000000000000000000000000000000000000000000000000000000:0",
    "last_update": 0,
    "node1_pub": "REDACTED",
    "node2_pub": "REDACTED",
    "capacity": "0",
    "node1_policy": null,
    "node2_policy": null
}

This happened over 2 nodes, one testnet, one mainnet. In both instances the chan_point is all zeros

However, one instance has a single nodeX_policy as null, while the other instance above, both are null.

If I examine the output of lncli closechannels and find the node pubkey it's a cooperative close in both instances, e.g.

{
    "channel_point": "REDACTED:0",
    "chan_id": "REDACTED",
    "chain_hash": "REDACTED",
    "closing_tx_hash": "REDACTED",
    "remote_pubkey": "REDACTED",
    "capacity": "20000",
    "close_height": 1637586,
    "settled_balance": "0",
    "time_locked_balance": "0",
    "close_type": "COOPERATIVE_CLOSE",
    "open_initiator": "INITIATOR_REMOTE",
    "close_initiator": "INITIATOR_UNKNOWN",
    "resolutions": [
    ]
},

I'm fully synced:

"synced_to_chain": true,
"synced_to_graph": true,

Your environment

• lnd version 0.11.0-beta commit=v0.11.0-beta
• Ubuntu 16.04, Linux lnd 4.4.0-179-generic Add litecoin docker image and container. #209-Ubuntu SMP Fri Apr 24 17:48:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
• testnet instance is backed with btcd version 0.20.1-beta
• mainnet instance is backed with Bitcoin Core RPC client version v0.18.0.0-2472733a24a9364e4c6233ccd04166a26a68cc65
• these are long-running nodes, which have gone through upgrades from the earliest public LND releases

Steps to reproduce

An unknown something happens with a closed channel.

Run lncli feereport and get an error

Expected behaviour

I should see output with a list of fees.

Actual behaviour

I get an error

[lncli] rpc error: code = Unknown desc = no policy for outgoing channel REDACTED

[bretton]

The issue is happening on another node now, only this time it's an active channel.

[ERR] RPCS: [/lnrpc.Lightning/FeeReport]: no policy for outgoing channel REDACTED

lncli getchaninfo gives a null result for node1_policy, which is my node in this instance.

Is there any way I can manually set the missing value so the error goes away?
How can I check it's not something I'm doing wrong. I run with default fee options, and never adjust those settings on the fly.

[bretton]

Found earlier issues, going back a year. It's strange it's popped up on 3 different nodes of mine in a short time period.

The suggestion seems to be to wipe the node and start over, lose of network reputation scoring. Else patch code on every update. Neither option is attractive. Will try abandonchannel options. Also the open channel with the error got closed now, but the error remains my side.

note added: abandonchannel is a dangerous command and can lead to loss of funds if used incorrectly - ask in the LND slack channel if unsure

#2911

#3477

raspiblitz/raspiblitz#1107

edit no luck with abandonchannel

[bretton]

Further investigation lncli feereport error with null node_policy, shows the problem channels were opened in March 2018, Dec 2019. Functioned just fine since then till now.

Things that helped finding the fundingtx for lncli abandonchannel purposes was logs going back that many years. I'm not sure if there's another way?

[githorray]

This has just started happening on my node as well. A channel closed from mid 2019 is suddenly back in the graph. "no policy for outgoing channel" errors now.

[githorray]

Things that helped finding the fundingtx for lncli abandonchannel purposes was logs going back that many years. I'm not sure if there's another way?

1ml shows the funding transaction (channel point) from a channel id.

[githorray]

I tried using lncli abandonchannel as well on the previously closed channel. No error returned, but no change in behavior. Still an error running lncli feereport with the same channel id.

[bretton]

if I try update the channel policy for the problem channel, I get the error

[lncli] rpc error: code = Unknown desc = channel from self node has no policy

however it's a closed channel so retroactively adjusting policy probably not possible?

[githorray]

Maybe a strategic continue is in order. ☺️

[githorray]

This is the patch I am using to get back up and running in the meantime if anyone is stuck with this.

diff --git a/routing/router.go b/routing/router.go
index af1e8d75..396fbdd2 100644
--- a/routing/router.go
+++ b/routing/router.go
@@ -2255,7 +2255,7 @@ func (r *ChannelRouter) ForAllOutgoingChannels(cb func(*channeldb.ChannelEdgeInf
                e, _ *channeldb.ChannelEdgePolicy) error {

                if e == nil {
-                       return fmt.Errorf("channel from self node has no policy")
+                       return nil
                }

                return cb(c, e)
diff --git a/rpcserver.go b/rpcserver.go
index 8d39547f..4d74ca11 100644
--- a/rpcserver.go
+++ b/rpcserver.go
@@ -5756,8 +5756,7 @@ func (r *rpcServer) FeeReport(ctx context.Context,

                // Self node should always have policies for its channels.
                if edgePolicy == nil {
-                       return fmt.Errorf("no policy for outgoing channel %v ",
-                               chanInfo.ChannelID)
+                       return nil
                }

                // We'll compute the effective fee rate by converting from a

[halseth]

So you are saying this channel is closed? Or is this an old channel that was working fine before, and this suddenly started happening?

[bretton]

So you are saying this channel is closed?

the channel was in closed channels. I'm not sure why it closed. the error started appearing for some reason. happened on multiple nodes.

[halseth]

Interesting. Are you able to see it either in listchannels or closedchannels? Can you post the info shown there?

[bretton]

The output of lncli closedchannels is included in the original issue report. (it has a typo). I was asked to redact identifying info.

The channel doesn't appear in lncli listchannels.

on my other node it gives similar results to original above:

{
    "channel_point": "REDACTED",
    "chan_id": "REDACTED",
    "chain_hash": "REDACTED",
    "closing_tx_hash": "REDACTED",
    "remote_pubkey": "REDACTED",
    "capacity": "3000000",
    "close_height": 580311,
    "settled_balance": "141045",
    "time_locked_balance": "0",
    "close_type": "COOPERATIVE_CLOSE",
    "open_initiator": "INITIATOR_UNKNOWN",
    "close_initiator": "INITIATOR_UNKNOWN",
    "resolutions": [
    ]
}

except that INITIATOR_UNKNOWN appears twice, instead of only once like the original issue note.

examining the channel:

{
    "channel_id": "REDACTED",
    "chan_point": "0000000000000000000000000000000000000000000000000000000000000000:0",
    "last_update": 1560165966,
    "node1_pub": "REDACTED",
    "node2_pub": "REDACTED",
    "capacity": "0",
    "node1_policy": {
        "time_lock_delta": 14,
        "min_htlc": "1000",
        "fee_base_msat": "200",
        "fee_rate_milli_msat": "200",
        "disabled": false,
        "max_htlc_msat": "2940000000",
        "last_update": 1560165966
    },
    "node2_policy": null
}