ChannelLink - remote unresponsive

[frbitten]

I have a channel that is constantly offline. But I already noticed that the LND shows the channel as offline, but the peer is active and I can connect to it.
I didn't understand the reason for the error in ChannelLink that in the sequence when trying to connect again indicates that the peers are already connected.

lnd_1        | 2023-04-11 10:08:19.154 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
lnd_1        | 2023-04-11 10:08:19.556 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:57506
lnd_1        | 2023-04-11 10:54:28.844 [ERR] RPCS: [/routerrpc.Router/SendPaymentV2]: context deadline exceeded
lnd_1        | 2023-04-11 11:06:56.648 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:07:13.675 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:38822
lnd_1        | 2023-04-11 11:41:22.833 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:41:33.387 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:36108
lnd_1        | 2023-04-11 11:44:03.790 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:45:29.530 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:45:33.663 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:54786
lnd_1        | 2023-04-11 11:47:16.618 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:50:21.305 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:53:24.652 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 11:53:33.753 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:9735
lnd_1        | 2023-04-11 12:11:25.784 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:11:33.479 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:9735
lnd_1        | 2023-04-11 12:13:30.956 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:17:31.803 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:18:05.555 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:9735
lnd_1        | 2023-04-11 12:20:13.279 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:23:17.837 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:24:22.092 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:9735
lnd_1        | 2023-04-11 12:31:13.981 [ERR] RPCS: [/lnrpc.Lightning/GetNodeInfo]: rpc error: code = NotFound desc = unable to find node
lnd_1        | 2023-04-11 12:41:30.147 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:41:32.663 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:9735
lnd_1        | 2023-04-11 12:42:59.228 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:44:40.404 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:59812
lnd_1        | 2023-04-11 12:45:46.935 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:50:52.133 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:50:55.204 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:34472
lnd_1        | 2023-04-11 12:56:18.965 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 12:56:19.771 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:43240
lnd_1        | 2023-04-11 13:12:26.823 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 13:12:35.244 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:43278
lnd_1        | 2023-04-11 13:14:51.056 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 13:15:42.769 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:42010
lnd_1        | 2023-04-11 13:17:21.622 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 13:20:14.577 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 13:23:08.062 [ERR] HSWC: ChannelLink(2db351bae60d655c2dd72c3b852e518fe7c80c2dc7e1069f879cd1b6177a0d88:1): failing link: unable to complete dance with error: remote unresponsive
lnd_1        | 2023-04-11 13:23:22.839 [ERR] RPCS: [connectpeer]: error connecting to peer: already connected to peer: 03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09@90.146.208.162:33568

[guggero]

Sounds like it could be a connection issue. Are you running a Tor only node or are you using the --tor.skip-proxy-for-clearnet-targets flag?

[guggero]

Can you try if that still happens with 0.16.0? There were a few improvements in that area of the code I think.

[frbitten]

I left LNDg rebalancing turned off and noticed that the channel was much less offline. It goes offline when there is a routing attempt or a rebalance for it. In other words, when you have an HTLC attempt.

I'll have to wait for Umbrel to release version 16 to be able to test it.

[frbitten]

I tried now to close the channel and I get the following message: "Channel close failed! Error: link failed to shutdown"
The peer is large and I think it's unlikely that you're having problems.
https://amboss.space/node/03b9aacb265dc5ebde04b91b28f7c8bb6ba0af146e5f37426915742daf8f195a09

[guggero]

I'd try again with 0.16 (I think Umbrel will publish the update soon). Or try directly after re-connecting. If it still doesn't work, I'd create an issue with the full logs around the time of the close attempt. Or, if you don't want to wait, you can also just force close the channel (though then we won't know what caused the problem).

[frbitten]

I couldn't wait and decided to force the channel to close. I'll follow up if it happens again with another channel.
But thanks for the help.