Open
Description
I am trying to trigger a force close to a CLN peer because I think I am experiencing the issue described in https://github.com/lightninglabs/chantools/blob/master/doc/chantools_triggerforceclose.md
in case the peer is a specific version of CLN that does not properly respond to a Data Loss Protection re-establish message
It looks like even this isn't working and I haven't been able to get in contact with the peer. This is an unannounced channel, not sure if that makes a difference. Is there any way to further debug this?
lnd:~# chantools triggerforceclose --peer 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735 --channel_point *** --rootkey *** --torproxy $(ip route | grep default | awk '{print $3}'):9050
2024-07-27 12:41:48.899 [INF] CHAN: chantools version v0.13.1 commit
2024-07-27 12:41:48.900 [DBG] CHAN: Attempting to resolve peer address 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:41:48.901 [DBG] CHAN: Attempting to dial resolved peer address 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:41:52.140 [INF] CHAN: Attempting to establish p2p connection to peer 02d523cf57a7736d04db04b76076badb2d4b81a4cfe6fe16114aee2f500cef845d, dialtimeout is 1m0s
2024-07-27 12:41:52.152 [DBG] CHDB: Populating in-memory channel graph, this might take a while...
2024-07-27 12:41:52.152 [DBG] CHDB: Finished populating in-memory channel graph (took 479.989µs, num_node_features=0, num_nodes=0, num_channels=0)
2024-07-27 12:41:52.152 [INF] CHDB: Checking for schema update: latest_version=31, db_version=31
2024-07-27 12:41:52.153 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
2024-07-27 12:41:52.153 [DBG] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Sending Init to 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:41:52.796 [DBG] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Received Init from 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:41:52.796 [DBG] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Loaded 0 active channels from database
2024-07-27 12:41:52.796 [INF] CHAN: Connection established to peer 02d523cf57a7736d04db04b76076badb2d4b81a4cfe6fe16114aee2f500cef845d
2024-07-27 12:41:52.796 [INF] CHAN: Sending channel re-establish to peer to trigger force close of channel ***
2024-07-27 12:41:52.797 [DBG] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Sending ChannelReestablish(chan_id=08c9d1f07af7b677f86d95b9574862e38ad224afcbd5f64c2a3e91edf96969d2, next_local_height=0, remote_tail_height=0) to 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:41:52.797 [INF] CHAN: Sending channel error message to peer to trigger force close of channel ***
2024-07-27 12:41:52.797 [INF] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Negotiated chan series queries
2024-07-27 12:41:52.797 [DBG] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Sending Error(type=17) to 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:41:52.798 [INF] CHAN: Message sent, waiting for force close transaction to appear in mempool
2024-07-27 12:42:08.047 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:42:13.138 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:42:22.709 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:42:31.743 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:42:38.219 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:42:47.613 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:42:52.798 [DBG] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): Sending Ping(ping_bytes=0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000) to 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735
2024-07-27 12:42:52.798 [INF] PEER: Peer(037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138): disconnecting 037a43b480b33ffaaaef6abd80814becfb89389c21bd18787884e186a5cb507138@jg7tka7hxo4tzqlwom56urpeuhdxn4bya73egflw6xcwki2tddcsuaid.onion:9735, reason: unable to write message: write tcp 172.18.0.232:54120->172.18.0.1:9050: write: broken pipe
2024-07-27 12:42:55.675 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:43:07.793 [INF] CHAN: No spends found yet, waiting 5 seconds...
2024-07-27 12:43:14.686 [INF] CHAN: No spends found yet, waiting 5 seconds...
Metadata
Metadata
Assignees
Labels
No labels