Da ich technisch zu wenig davon verstehe, würde ich gerne Meinungen zu folgendem Tweed hören:
GBC
19. Mai 2023 um 07:52
2
bitcoind lastet einen Core aus
Der genannte CPU hat 32 Kerne und 64 Threads.
Wenn ich mein Auto nur im ersten Gang fahre und mich dann beschwere, dass es langsam, laut und stinkig ist…
Das „Congestion“ Problem ist kein Problem. Wie man sehen kann, hat sich der Markt erfolgreich selbst reguliert. Steigt die Nachfrage, steigt eben der Preis. Aber auch nur bis zu dem Punkt, ab dem keiner mehr diese Preise zahlen will.
Aber auch, wenn eine Transaktion 50€ in Gegenwert kostet könnte ich damit tausende von Euro in Gegenwert in das Lightning Netzwerk bringen und damit quasi kostenfrei unendlich oft transaktieren.
Die Kritik ist sehr einfach gehalten.
Wenn die Gebühren so hoch sind, muss ich ja auch keinen Force-Close machen. Das ergibt gar keinen Sinn.
Das ist so, als wenn man zum Höhepunkt der Benzinpreise tanken fährt, obwohl man das Auto eigentlich gar nicht nutzt und sowieso lieber mit den Fahrrad überall hinfährt.
mxm
19. Mai 2023 um 10:58
3
Also mein Raspberry Pi 4 (es läuft bitcoind, electrum und LND) hat seit LND v0.16.2-beta eine höhere CPU-Auslastung (Problem wohl schon gefixt, siehe [bug]: high cpu usage · Issue #7675 · lightningnetwork/lnd · GitHub ), aber ist nie abgestürzt.
Was die Force-Close Probleme angeht, so haben die auch nichts mit der hohen mempool-Auslastung zu tun.
opened 01:41AM - 17 Dec 21 UTC
bug
force closes
### Background
Some channels get disabled but the connections to the channel … peers remain active. Network sees that the channel is disabled from one side (my side) but is active from the peer side. They remain this way until I manually disconnect the peer.
### Your environment
* `lnd v0.14.1-beta`
* Centos 8 `4.18.0-305.19.1.el8_4.x86_64`
* `bitcoind 22.0` running on a remote node
### Steps to reproduce
Unable to reproduce on demand. But it has been happening for the past few weeks over multiple service restarts.
All the channels involved exhibit the same behaviour in the logs:
1. `ChannelLink` fails and exits after attempt to update commit fee
2. 22 minutes later channel is announced as disabled
3. Connection with peer remains active, `GossipSyncer` still works on the peer.
4. Network sees channel as `disabled:true` from my side but `disabled:false` from the peer side.
5. This remains until I then manually disconnect the peer, which then causes the new incoming connection to fix everything.
Here are some logs to show the behaviour
Channel 1:
```
2021-12-16 17:46:16.695 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): no more chans to query
2021-12-16 20:04:06.922 [INF] HSWC: ChannelLink(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1): updating commit fee to 1161 sat/kw sat/kw
2021-12-16 20:25:42.874 [INF] HSWC: ChannelLink(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1): updating commit fee to 1161 sat/kw sat/kw
2021-12-16 20:26:42.874 [ERR] HSWC: ChannelLink(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1): failing link: unable to complete dance with error: remote unresponsive
2021-12-16 20:26:42.875 [INF] HSWC: ChannelLink(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1): exited
2021-12-16 20:26:42.875 [INF] HSWC: ChannelLink(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1): stopping
2021-12-16 20:47:22.690 [INF] NANN: Announcing channel(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1) disabled [detected]
2021-12-16 23:44:35.385 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): requesting new chans from height=0 and 714409 blocks after
2021-12-17 07:42:24.013 [WRN] CHBU: Replacing disk backup for ChannelPoint(eaddf2d59d74e4f9d9450241772c9180516d6d6a478cb5e23cc48a33e065b33a:1) w/ newer version
2021-12-17 07:48:03.949 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=8000
2021-12-17 07:48:03.949 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=8000
2021-12-17 07:48:03.949 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=7999
2021-12-17 07:48:03.949 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=8000
2021-12-17 07:48:03.949 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=7999
2021-12-17 07:48:03.949 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=7998
2021-12-17 07:48:03.950 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=8000
2021-12-17 07:48:03.950 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=7999
2021-12-17 07:48:03.950 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=8000
2021-12-17 07:48:03.950 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=7944
2021-12-17 07:48:03.951 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): buffering chan range reply of size=2148
2021-12-17 07:48:03.951 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): filtering through 82087 chans
2021-12-17 07:48:04.036 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): starting query for 23 new chans
2021-12-17 07:48:04.036 [INF] DISC: GossipSyncer(0272dfe15e1f7781e46fc485249d65af013c092e5a1c474d9ede2a6e7e5624c09c): querying for 23 new channels
```
Channel 2:
```
2021-12-16 01:43:17.938 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:1): updating commit fee to 1053 sat/kw sat/kw
2021-12-16 02:16:39.872 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:1): updating commit fee to 1110 sat/kw sat/kw
2021-12-16 02:17:39.873 [ERR] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:1): failing link: unable to complete dance with error: remote unresponsive
2021-12-16 02:17:39.873 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:1): exited
2021-12-16 02:17:39.873 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:1): stopping
2021-12-16 02:38:22.687 [INF] NANN: Announcing channel(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:1) disabled [detected]
2021-12-16 03:09:05.672 [INF] DISC: GossipSyncer(03cb29720b97a67c8b21de36492e45ed28e25b06a04d880b1cbd5fc77c7e0ca782): applying new update horizon: start=2021-12-16 03:09:03 +0800 +08, end=2158-01-22 09:37:18 +0800 +08, backlog_size=0
2021-12-16 03:29:03.971 [INF] DISC: GossipSyncer(03cb29720b97a67c8b21de36492e45ed28e25b06a04d880b1cbd5fc77c7e0ca782): applying new update horizon: start=2042-07-14 09:04:00 +0800 +08, end=2042-07-14 09:04:00 +0800 +08, backlog_size=0
```
Channel 3 (with manual disconnect at the end):
```
2021-12-16 05:32:38.204 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): updating commit fee to 1561 sat/kw sat/kw
2021-12-16 05:33:38.204 [ERR] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): failing link: unable to complete dance with error: remote unresponsive
2021-12-16 05:33:38.205 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): exited
2021-12-16 05:33:38.206 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): stopping
2021-12-16 05:54:22.686 [INF] NANN: Announcing channel(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0) disabled [detected]
2021-12-16 07:38:10.008 [INF] DISC: GossipSyncer(03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad): buffering chan range reply of size=7999
2021-12-16 07:38:10.008 [INF] DISC: GossipSyncer(03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad): buffering chan range reply of size=8000
2021-12-16 07:38:10.008 [INF] DISC: GossipSyncer(03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad): buffering chan range reply of size=7999
....
2021-12-17 08:29:28.841 [INF] SRVR: Disconnecting from 03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad@185.220.100.248:19106
2021-12-17 08:29:28.841 [INF] PEER: disconnecting 03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad@185.220.100.248:19106, reason: server: disconnecting peer 03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad@185.220.100.248:19106
2021-12-17 08:29:28.943 [INF] DISC: Removing GossipSyncer for peer=03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad
2021-12-17 08:29:32.337 [INF] SRVR: Finalizing connection to 03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad@209.127.17.234:48042, inbound=true
2021-12-17 08:29:32.573 [INF] PEER: NodeKey(03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad) loading ChannelPoint(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0)
2021-12-17 08:29:32.574 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): starting
2021-12-17 08:29:32.574 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0)
2021-12-17 08:29:32.574 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): HTLC manager started, bandwidth=96316000 mSAT
2021-12-17 08:29:32.574 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): attempting to re-synchronize
2021-12-17 08:29:32.574 [INF] PEER: Negotiated chan series queries with 03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad
2021-12-17 08:29:32.575 [INF] DISC: Creating new GossipSyncer for peer=03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad
2021-12-17 08:29:33.539 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): received re-establishment message from remote side
2021-12-17 08:42:53.698 [INF] DISC: GossipSyncer(03ee951b50d5dc4631bfbde250e7fd2a119a108b7ba3d62079574c584e536563ad): applying new update horizon: start=2021-12-17 08:42:53 +0800 +08, end=2158-01-23 15:11:08 +0800 +08, backlog_size=0
2021-12-17 08:48:18.402 [INF] HSWC: ChannelLink(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0): updating commit fee to 1991 sat/kw sat/kw
2021-12-17 08:48:32.575 [INF] NANN: Announcing channel(bac1e5b2ef4745e30c0aa16e7a298590674297de17ad7f3addf0668d0a7eff22:0) enabled
```
### Expected behaviour
Before disabling a channel, check whether the peer is truly offline and unreachable before finalising the channel disable. Maybe attempt automated disconnect/reconnect to try re-enabling the channel.
### Actual behaviour
Channel is announced as disabled, and lnd just waits for a Channel Reestablish message from peer (which never comes because peer has an active connection and thinks channel is still OK).
I will have to manually disconnect the peer to initiate a new fresh connection which enables the channel.
opened 05:31PM - 09 May 23 UTC
bug
commitments
HTLC
needs triage
force closes
In the past few days I've observed two peers which went unresponsive on me after… the commitment state machine did something nontrivial leading to stuck HTLCs for days and one force-close. On the other channel I disconnected+reconnected and the state machine picked back up and continued fine.
I'm waiting on positive version identification for the channel which force-closed, but the channel which I managed to resume had the following messages exchanged:
```
2023-05-06 18:53:45.864 TRACE [lightning::ln::peer_handler:1119] Enqueueing message UpdateAddHTLC
2023-05-06 18:53:45.864 TRACE [lightning::ln::peer_handler:1119] Enqueueing message CommitmentSigned
2023-05-06 18:56:14.413 TRACE [lightning::ln::peer_handler:1429] Received message RevokeAndACK
2023-05-06 18:56:14.477 TRACE [lightning::ln::peer_handler:1429] Received message CommitmentSigned # lnd peer should now be waiting on my RAA but otherwise happy
2023-05-06 18:56:14.532 TRACE [lightning::ln::peer_handler:1119] Enqueueing message UpdateAddHTLC
2023-05-06 18:56:14.532 TRACE [lightning::ln::peer_handler:1119] Enqueueing message UpdateAddHTLC
2023-05-06 18:56:14.532 TRACE [lightning::ln::peer_handler:1119] Enqueueing message UpdateAddHTLC
2023-05-06 18:56:14.532 TRACE [lightning::ln::peer_handler:1119] Enqueueing message CommitmentSigned
2023-05-06 18:56:14.532 TRACE [lightning::ln::peer_handler:1119] Enqueueing message RevokeAndACK # We're now expecting an RAA (of the previous commitment) and a response commitment_signed
2023-05-06 18:59:10.946 TRACE [lightning::ln::peer_handler:1429] Received message RevokeAndACK
2023-05-06 18:59:11.072 TRACE [lightning::ln::peer_handler:1429] Received message CommitmentSigned
2023-05-06 18:59:11.190 TRACE [lightning::ln::peer_handler:1119] Enqueueing message CommitmentSigned # we now want a n RAA in response to this which never comes
2023-05-06 18:59:11.190 TRACE [lightning::ln::peer_handler:1119] Enqueueing message RevokeAndACK
```
My counterparty indicated they're running LND 0.16.1-beta and
"There's only one line in the logs from that time relevant to our channel `2023-05-06 18:57:21.387 [ERR] HSWC: ChannelLink(ae8eb08347dfcf674392b22553e9cdb0a47c413bf12e0aa3087ee9cdbcaee623:1): failing link: unable to complete dance with error: remote unresponsive`"
opened 07:34PM - 17 May 23 UTC
bug
### Background
Recently during mempool high fees I had multiple HLTC's stuck … pending on my node with no logs information and zero output from `lncli trackpayment`, this happened multiple times during last two weeks. All peers were online during the whole time.
### Your environment
* version of `lnd` : 0.16.2
* operating system: Debian Linux 6.1.21-v8+ aarch64
* version of `btcd`, `bitcoind`, or other backend : 24.0.1
### Steps to reproduce
No idea how this happened, no logs or traces of this problem, could not find single information about the forwards being signed in logs. All that I was able to see were multiple HTLC's by using `lncli listchannels | jq '.channels[] | select(.pending_htlcs | length > 0)'` command thanks to @bitromortac
### Expected behaviour
HLTC's should be resolved in time without getting stuck randomly causing force-closes.
### Actual behaviour
HTLC's timed out, some caused force-closure of channel, some were sent on-chain without force close. Latest HTLC's were saved by advice from another node owner by disconnecting the peers that had pending HLTC's with `lncli disconnect pubkey` just about 12 blocks before expiring, this cleared the pending HTLC every time.
Für mich ist das FUD.
2 „Gefällt mir“
