Ryu
September 4, 2022, 2:12pm
1
Dear Umbrel team,
I have faced stuck in updating fee rate for newly opened channel afeter recent LND update.
I found this is a already reported issue below.
opened 08:37AM - 04 Sep 22 UTC
closed 05:21PM - 21 Sep 22 UTC
bug
server
P1
### Background
Since upgrading to 0.15.1-beta I and some others are facing a … unique issue. Once a channel is opened (either initiated by me or opened to me by remote), it seems to get stuck in "confirming funding locked" and never gets announced to graph until I restart lnd. Here is the latest example, I will add more (historical or future) as and when I find them.
**Channel Initiated by Remote**
1. Channel Open by remote
```
2022-09-04 02:36:53.134 [INF] FNDG: Recv'd fundingRequest(amt=0.11040886 BTC, push=0 mSAT, delay=144, pendingId=cde52bb26051dffee584fc33e2b73b35b1881499ebba665bdf34ca80e128d197) from peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293)
2022-09-04 02:36:53.139 [INF] CHFD: Performing funding tx coin selection using 0 sat/kw as fee rate
2022-09-04 02:36:53.216 [INF] FNDG: Requiring 1 confirmations for pendingChan(cde52bb26051dffee584fc33e2b73b35b1881499ebba665bdf34ca80e128d197): amt=0.11040886 BTC, push_amt=0 mSAT, committype=tweakless, upfrontShutdown=
2022-09-04 02:36:53.217 [INF] FNDG: Sending fundingResp for pending_id(cde52bb26051dffee584fc33e2b73b35b1881499ebba665bdf34ca80e128d197)
2022-09-04 02:36:53.377 [INF] FNDG: completing pending_id(cde52bb26051dffee584fc33e2b73b35b1881499ebba665bdf34ca80e128d197) with ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2)
2022-09-04 02:36:53.405 [INF] FNDG: sending FundingSigned for pending_id(cde52bb26051dffee584fc33e2b73b35b1881499ebba665bdf34ca80e128d197) over ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2)
2022-09-04 02:36:53.407 [INF] CNCT: Creating new ChannelArbitrator for ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2)
2022-09-04 02:36:53.418 [INF] CNCT: ChannelArbitrator(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): starting state=StateDefault, trigger=chainTrigger, triggerHeight=752513
2022-09-04 02:36:53.424 [INF] NTFN: New spend subscription: spend_id=229, outpoint=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2, script=0 1a2bb535ebead75e4f2942b4881a1899fab918d4e87603c04b9c0d2ab95acf6b, height_hint=752513
2022-09-04 02:36:53.424 [INF] NTFN: Dispatching historical spend rescan for outpoint=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2, script=0 1a2bb535ebead75e4f2942b4881a1899fab918d4e87603c04b9c0d2ab95acf6b, start=752513, end=752513
2022-09-04 02:36:53.449 [INF] CNCT: Close observer for ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2) active
2022-09-04 02:36:53.452 [INF] NTFN: New block epoch subscription
2022-09-04 02:36:53.457 [INF] NTFN: New confirmation subscription: conf_id=4, txid=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35, num_confs=1 height_hint=752513
2022-09-04 02:36:53.459 [INF] FNDG: Waiting for funding tx (86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35) to reach 1 confirmations
2022-09-04 02:36:53.461 [INF] NTFN: Historical spend dispatch finished for request outpoint=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2, script=0 1a2bb535ebead75e4f2942b4881a1899fab918d4e87603c04b9c0d2ab95acf6b (start=752513 end=752513) with details: <nil>
2022-09-04 02:36:53.469 [INF] CHBU: Updating on-disk multi SCB backup: num_old_chans=225, num_new_chans=226
2022-09-04 02:36:53.596 [WRN] CHBU: Replacing disk backup for ChannelPoint(d6a24e9fb889213cead5fdb52489d3952716d9ba4bff6a35fec595dbdac261b2:1) w/ newer version
2
```
2. Chanel Opened
```
2022-09-04 02:49:32.071 [INF] NTFN: Dispatching 1 confirmation notification for txid=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35
2022-09-04 02:49:32.077 [INF] UTXN: Attempting to graduate height=752514: num_kids=0, num_babies=0
2022-09-04 02:49:32.078 [INF] FNDG: ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2) is now active: ChannelID(351be2b1a22612daebc0fb692c71e2828c6f957ded05c55d1483cec370b9bd84)
2022-09-04 02:49:32.187 [INF] FNDG: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293) is online, sending FundingLocked for ChannelID(351be2b1a22612daebc0fb692c71e2828c6f957ded05c55d1483cec370b9bd84)
```
3. Channel unable to receive funding lock. Unable to find forwarding policies
```
2022-09-04 02:49:57.236 [INF] PEER: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293): loading ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2)
2022-09-04 02:49:57.239 [WRN] PEER: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293): Unable to find our forwarding policy for channel 86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2, using default values
2022-09-04 02:49:57.239 [INF] HSWC: ChannelLink(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): starting
2022-09-04 02:49:57.239 [INF] HSWC: Trimming open circuits for chan_id=752514:1289:2, start_htlc_id=0
2022-09-04 02:49:57.240 [INF] HSWC: Adding live link chan_id=351be2b1a22612daebc0fb692c71e2828c6f957ded05c55d1483cec370b9bd84, short_chan_id=752514:1289:2
2022-09-04 02:49:57.240 [INF] HSWC: ChannelLink(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): HTLC manager started, bandwidth=0 mSAT
2022-09-04 02:49:57.240 [INF] HSWC: ChannelLink(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): attempting to re-synchronize
2022-09-04 02:49:57.240 [INF] PEER: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293): Negotiated chan series queries
2022-09-04 02:49:57.240 [INF] DISC: Creating new GossipSyncer for peer=03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293
2022-09-04 02:49:57.240 [INF] NTFN: New block epoch subscription
2022-09-04 02:49:57.240 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2)
2022-09-04 02:49:58.223 [INF] HSWC: ChannelLink(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): resending FundingLocked message to peer
2022-09-04 02:49:58.224 [INF] HSWC: ChannelLink(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): received re-establishment message from remote side
2022-09-04 02:49:58.312 [INF] PEER: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293): Already have ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2), ignoring.
2022-09-04 02:49:58.312 [INF] PEER: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293): Processing retransmitted FundingLocked for ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2)
2022-09-04 02:50:04.176 [ERR] NANN: Unable to retrieve chan status for Channel(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): edge not found
2022-09-04 02:51:06.241 [ERR] PEER: Peer(03cf31364b9361f434b91f0e1943664f723e30c818b9a396bbbf5ef4284612c293): Unable to enable channel 86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2: edge not found
```
4. This goes on and on until I restart lnd
```
2022-09-04 02:53:31.163 [ERR] NANN: Unable to retrieve chan status for Channel(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): edge not found
....
2022-09-04 07:47:55.181 [ERR] NANN: Unable to retrieve chan status for Channel(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): edge not found
```
5. Restart lnd
```
2022-09-04 07:51:14.149 [ERR] FNDG: Unable to advance state(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2): failed to check if funding locked was received: funding manager shutting down
2022-09-04 07:51:14.837 [INF] LTND: Shutdown complete
2022-09-04 07:51:45.866 [INF] LTND: Version: 0.15.1-beta commit=v0.15.1-beta, build=production, logging=default, debuglevel=info
```
6. Channel Announced
```
2022-09-04 07:56:56.165 [INF] NTFN: New confirmation subscription: conf_id=3, txid=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35, num_confs=6 height_hint=752514
2022-09-04 07:56:56.530 [INF] DISC: Received new remote channel announcement for 725154:2737:2
2022-09-04 07:56:56.545 [WRN] DISC: ignoring remote ChannelAnnouncement for own channel
2022-09-04 07:56:57.527 [INF] NTFN: Dispatching 6 confirmation notification for txid=86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35
2022-09-04 07:56:57.528 [INF] FNDG: Announcing ChannelPoint(86bdb970c3ce83145dc505ed7d956f8c82e2712c69fbc0ebda1226a2b1e21b35:2), short_chan_id=752514:1289:2
2022-09-04 07:56:57.529 [INF] DISC: Received new local channel announcement for 752514:1289:2
2022-09-04 07:56:57.829 [INF] DISC: Fully valid channel proof for short_chan_id=827397893148704770 constructed, adding to next ann batch
```
### Your environment
* version of `lnd`
```
umbrel@umbrel:~ $ lncli getinfo
{
"version": "0.15.1-beta commit=v0.15.1-beta",
"commit_hash": "fd1a95bf322cdd1c743a1554f8e470fbf9a5e564",
"identity_pubkey": "03c5528c628681aa17ab9e117aa3ee6f06c750dfb17df758ecabcd68f1567ad8c1",
```
* which operating system (`uname -a` on *Nix)
`Linux umbrel 5.10.17-v8+ #1421 SMP PREEMPT Thu May 27 14:01:37 BST 2021 aarch64 GNU/Linux`
Please kindly check it and let users know what we should and shoud not.
Thank you in advance.
Best Regards,
Hakuna
September 5, 2022, 7:04am
2
It looks like an LND (or LND <> CLN interoperability) issue. Not much umbrel can do about it.
1 Like