-
Notifications
You must be signed in to change notification settings - Fork 32
htlc failed message since a day - Almost no transactions get routed anymore #259
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
Comments
The messages you pasted seem to indicate CLBOSS re-balance failures. Failed forwards are not shown like this. |
@tsjk Thanks for the quick response! I'm not concerned about my node's security or something. More about "being an actual help to the network and not blocking others" and also routing fees that aren't coming in anymore. In Ride The Lightning, I see that I get like 10 sats a day for routing payments, instead of 200. Another thread somewhere assumed, that these are the rebalancing fees of my own node, but not actual payments that actually made it through. I have no idea though. |
Yes, it's confusing, but re-balances do add to the fees you "get". I haven't used Ride The Lightning for a while now, but isn't there a page for showing successful forwards? You should look at that for gathering information on what you route. |
Lol I was dumb enough to click. Wasn't aware that scammers made it to github. |
This is a problem. It's all automated. Wouldn't hold my breath for a remedy. |
Hm I only see an entry called "Routing Fee" and then a link to transactions, including failed ones. But it's not much info I can extract there. |
I realized that I actually have RTL on a testnet node. So, in the Lightning->Routing views you have several tabs, look at those perhaps. |
If you haven't tried turning on xpay yet, I'd highly recommend it. It will make your outgoing payments much more reliable. |
Thx, I activated it! Node is still syncing though. |
Hey, I get a lot of
htlc failed
messages. Is this a known issue and does someone probably know how I can fix my node again? I'm running CLBOSS on it and since a day the routing of payments almost completely stopped. I think, the little that pass through, are probably my own ones (CLBOSS initiating rebalances and so).The host is a Start9 server.
2025-01-16T08:08:46+01:00 2025-01-16T07:08:46.665Z INFO 02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b-chan#19: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) 2025-01-16T08:08:47+01:00 2025-01-16T07:08:47.210Z INFO lightningd: Sending 60945620msat over 7 hops to deliver 60940000msat 2025-01-16T08:08:54+01:00 2025-01-16T07:08:54.763Z INFO 02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b-chan#19: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) 2025-01-16T08:08:55+01:00 2025-01-16T07:08:55.299Z INFO lightningd: Sending 60947474msat over 7 hops to deliver 60940000msat 2025-01-16T08:08:58+01:00 2025-01-16T07:08:58.570Z INFO 03e81689bfd18d0accb28d720ed222209b1a5f2c6825308772beac75b1fe35d491-channeld-chan#16: Peer connection lost 2025-01-16T08:08:58+01:00 2025-01-16T07:08:58.570Z INFO 03e81689bfd18d0accb28d720ed222209b1a5f2c6825308772beac75b1fe35d491-chan#16: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (62208) 2025-01-16T08:09:02+01:00 2025-01-16T07:09:02.171Z INFO 02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b-chan#19: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) 2025-01-16T08:09:02+01:00 2025-01-16T07:09:02.678Z INFO lightningd: Sending 60945621msat over 7 hops to deliver 60940000msat 2025-01-16T08:09:09+01:00 2025-01-16T07:09:09.613Z INFO 02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b-chan#19: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) 2025-01-16T08:09:10+01:00 2025-01-16T07:09:10.141Z INFO lightningd: Sending 60945621msat over 7 hops to deliver 60940000msat 2025-01-16T08:09:17+01:00 2025-01-16T07:09:17.199Z INFO 02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b-chan#19: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) 2025-01-16T08:09:17+01:00 2025-01-16T07:09:17.734Z INFO lightningd: Sending 60945703msat over 8 hops to deliver 60940000msat 2025-01-16T08:09:26+01:00 2025-01-16T07:09:26.951Z INFO 02f4c77dcf12255ccf705c18b8d6b95e4f884910bf61e8aa21242607193a79da1b-chan#19: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE) 2025-01-16T08:09:27+01:00 2025-01-16T07:09:27.482Z INFO lightningd: Sending 60945801msat over 7 hops to deliver 60940000msat
The text was updated successfully, but these errors were encountered: