Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLN interoperability: cooperative close attempt resulted in unilateral close #6599

Closed
C-Otto opened this issue May 31, 2022 · 5 comments
Closed

Comments

@C-Otto
Copy link
Contributor

C-Otto commented May 31, 2022

Also see ElementsProject/lightning#5295

Background

My peer "zero fee routing" (running CLN 0.11.1) attempted to cooperatively close the channel to my node (running lnd 0.15.0-beta.rc3). This resulted in a unilateral close. At this time, the channel had several active/pending HTLCs.

CLN logs:

2022-05-31T12:20:22.034Z UNUSUAL 027ce055380348d7812d2ae7745701c9f93e70c1adeb2657f053f91df4f2843c71-chan#4233: Peer permanent failure in CHANNELD_SHUTTING_DOWN: channeld: received ERROR error channel a97b201f22165254e8035c22f5051f37470208e5248d80bce57871bc684565cd: link failed to shutdown

lnd logs:

2022-05-31 14:20:19.089 [DBG] HSWC: ChannelLink(cc654568bc7178e5bc808d24e5080247371f05f5225c03e8545216221f207ba9:1): queueing keystone of ADD open circuit: (Chan ID=0:0:0, HTLC ID=8175304)->(Chan ID=733084:270:1, HTLC ID=219854)
2022-05-31 14:20:19.168 [DBG] HSWC: ChannelLink(cc654568bc7178e5bc808d24e5080247371f05f5225c03e8545216221f207ba9:1): removing Add packet (Chan ID=0:0:0, HTLC ID=8175304) from mailbox
2022-05-31 14:20:22.240 [INF] HSWC: ChannelLink(cc654568bc7178e5bc808d24e5080247371f05f5225c03e8545216221f207ba9:1): stopping
2022-05-31 14:20:22.240 [INF] HSWC: ChannelLink(cc654568bc7178e5bc808d24e5080247371f05f5225c03e8545216221f207ba9:1): exited
2022-05-31 14:20:52.925 [DBG] NANN: Marking channel(cc654568bc7178e5bc808d24e5080247371f05f5225c03e8545216221f207ba9:1) pending-inactive
2022-05-31 14:20:22.039 [INF] PEER: unable to read message from 038fe1bd966b5cb0545963490c631eaa1924e2c4c0ea4e7dcb5d4582a1e7f2f1a5@167.235.3.234:51448: EOF
2022-05-31 14:20:22.039 [INF] PEER: disconnecting 038fe1bd966b5cb0545963490c631eaa1924e2c4c0ea4e7dcb5d4582a1e7f2f1a5@167.235.3.234:51448, reason: read handler closed
2022-05-31 14:20:22.030 [ERR] PEER: failed link shutdown: link failed to shutdown
2022-05-31 14:20:22.030 [ERR] PEER: Unable to respond to remote close msg: link failed to shutdown

Your environment

  • version of lnd: 0.15.0-beta.rc3
  • which operating system (uname -a on *Nix): Linux server 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux
  • version of btcd, bitcoind, or other backend: bitcoind v23

Steps to reproduce

Have channel with CLN peer. Have active/pending HTLCs. Initiate cooperative close from CLN.

Expected behaviour

Channel is disabled (peer disconnects?) and then closed once the HTLCs time out/settle/fail.

Actual behaviour

Immediate unilateral close triggered by CLN.

@Crypt-iQ
Copy link
Collaborator

This has to wait on the spec issue before we can make progress, but I think it's close

@C-Otto
Copy link
Contributor Author

C-Otto commented May 31, 2022

Could you provide a link?

@Crypt-iQ
Copy link
Collaborator

lightning/bolts#970

@alexbosworth
Copy link
Contributor

could be related to #6039

@Crypt-iQ
Copy link
Collaborator

Crypt-iQ commented Jun 1, 2022

Dupe of #6039

@Crypt-iQ Crypt-iQ closed this as completed Jun 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants