Core-Lightning with CLBOSS - htlc failed - Since a day, I cannot route payments anymore, out of nowhere

tennis · January 16, 2025, 7:16am

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).

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

StuPleb · January 16, 2025, 1:36pm

Are you saying that since you activated CLBOSS routing doesn’t work?

The majority of the errors refer to a specific channel, and specific nodes further down the intended route. There’s not much you can do about that node’s problems.

On your end, the peer for channel 19 might not be a good choice. Or maybe it is. We see from other errors here and there that you lose connections with other peers. Could you be suffering from poor Tor conenction issues? What does System → Tor Logs say?

It also shows channeld: Owning subdaemon channeld died - is there anything else in the logs similar? What about overall server stability? Are you running on slow hardware with low resources causing services to crash?

tennis · January 16, 2025, 1:41pm

Thanks for the reply.

Hmmmm… interesting. The TOR log looks more or less normal to me. I did a restart though.
I also “resynced” CLN, this will take some hours.

This is my current TOR log. It mentions attacks or “me using it wrong” here and there, but I get those messages also on my MacBook usually, and I can browse the internet over TOR there.

2025-01-16T14:27:48+01:00  Starting tor@default.service - Anonymizing overlay network for TCP...
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.172 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.172 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.173 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.173 [notice] Read configuration file "/etc/tor/torrc".
2025-01-16T14:27:48+01:00  Configuration was valid
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.192 [notice] Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.192 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.192 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.192 [notice] Read configuration file "/etc/tor/torrc".
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.193 [warn] You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.193 [notice] Opening Socks listener on 0.0.0.0:9050
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.193 [notice] Opened Socks listener connection (ready) on 0.0.0.0:9050
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.193 [notice] Opening Control listener on 127.0.0.1:9051
2025-01-16T14:27:48+01:00  Jan 16 13:27:48.193 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051
2025-01-16T14:27:48+01:00  We compiled with OpenSSL 300000b0: OpenSSL 3.0.11 19 Sep 2023 and we are running with OpenSSL 300000b0: 3.0.11. These two versions should be binary compatible.
2025-01-16T14:27:48+01:00  Tor 0.4.8.9 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
2025-01-16T14:27:48+01:00  Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
2025-01-16T14:27:48+01:00  Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
2025-01-16T14:27:48+01:00  Read configuration file "/etc/tor/torrc".
2025-01-16T14:27:48+01:00  You specified a public address '0.0.0.0:9050' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason.
2025-01-16T14:27:48+01:00  Opening Socks listener on 0.0.0.0:9050
2025-01-16T14:27:48+01:00  Opened Socks listener connection (ready) on 0.0.0.0:9050
2025-01-16T14:27:48+01:00  Opening Control listener on 127.0.0.1:9051
2025-01-16T14:27:48+01:00  Opened Control listener connection (ready) on 127.0.0.1:9051
2025-01-16T14:27:48+01:00  Parsing GEOIP IPv4 file /usr/share/tor/geoip.
2025-01-16T14:27:48+01:00  Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
2025-01-16T14:27:48+01:00  Bootstrapped 0% (starting): Starting
2025-01-16T14:27:48+01:00  Starting with guard context "default"
2025-01-16T14:27:48+01:00  Signaled readiness to systemd
2025-01-16T14:27:48+01:00  Started tor@default.service - Anonymizing overlay network for TCP.
2025-01-16T14:27:49+01:00  New control connection opened from 127.0.0.1.
2025-01-16T14:27:49+01:00  Opening Control listener on /run/tor/control
2025-01-16T14:27:49+01:00  Opened Control listener connection (ready) on /run/tor/control
2025-01-16T14:27:49+01:00  Bootstrapped 5% (conn): Connecting to a relay
2025-01-16T14:27:50+01:00  Bootstrapped 10% (conn_done): Connected to a relay
2025-01-16T14:27:50+01:00  Bootstrapped 14% (handshake): Handshaking with a relay
2025-01-16T14:27:50+01:00  Bootstrapped 15% (handshake_done): Handshake with a relay done
2025-01-16T14:27:50+01:00  Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
2025-01-16T14:27:50+01:00  Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
2025-01-16T14:27:50+01:00  Bootstrapped 30% (loading_status): Loading networkstatus consensus
2025-01-16T14:27:50+01:00  I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
2025-01-16T14:27:50+01:00  Bootstrapped 40% (loading_keys): Loading authority key certs
2025-01-16T14:27:50+01:00  The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
2025-01-16T14:27:50+01:00  Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
2025-01-16T14:27:50+01:00  I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7954, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
2025-01-16T14:27:51+01:00  Bootstrapped 50% (loading_descriptors): Loading relay descriptors
2025-01-16T14:27:51+01:00  The current consensus contains exit nodes. Tor can build exit and internal paths.
2025-01-16T14:27:52+01:00  Bootstrapped 55% (loading_descriptors): Loading relay descriptors
2025-01-16T14:27:52+01:00  Bootstrapped 63% (loading_descriptors): Loading relay descriptors
2025-01-16T14:27:52+01:00  Bootstrapped 72% (loading_descriptors): Loading relay descriptors
2025-01-16T14:27:52+01:00  Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
2025-01-16T14:27:53+01:00  Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
2025-01-16T14:27:53+01:00  Bootstrapped 95% (circuit_create): Establishing a Tor circuit
2025-01-16T14:27:53+01:00  Bootstrapped 100% (done): Done
2025-01-16T14:27:58+01:00  Guard spire3 ($B32F57F3DBD9E50D68A28EA38D3E51910428CFD1) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 90/151. Use counts are 74/74. 90 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
2025-01-16T14:27:58+01:00  Guard spire3 ($B32F57F3DBD9E50D68A28EA38D3E51910428CFD1) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 90/181. Use counts are 74/74. 90 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
2025-01-16T14:27:58+01:00  Guard TorRelay1c ($255CC3EA8DB03A9E45EAA7D2CE8A05A4F26F0457) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 85/151. Use counts are 24/24. 85 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
2025-01-16T14:27:58+01:00  Guard TorRelay1c ($255CC3EA8DB03A9E45EAA7D2CE8A05A4F26F0457) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 85/171. Use counts are 24/24. 85 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
2025-01-16T14:27:58+01:00  Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 298 buildtimes.

StuPleb · January 16, 2025, 1:47pm

There’s nothing here to go off of, it’s just the logs for the last few seconds.

You need to be looking for signs of poor connectivity over hours. The easiest to spot sign is bootstrapping happening over and over.

Troubleshooting peers is difficult to say the least.

Your hardware specs is a avenue to pursue also.

tennis · January 16, 2025, 2:00pm

Do you think, it’s in general good to do a system reboot in such a case?

Thanks for helping man, I appreciate it!

StuPleb · January 16, 2025, 2:04pm

I’ve mentioned three cases.

For a Tor issue, you don’t need to reboot, since you can instead go to System → Experimental Features → Reset Tor

For the other two, a reset obviously won’t increase your RAM or fix your peer’s node! If channel 19 is giving you lots a trouble and never improving, you could always close it.

tennis · January 16, 2025, 3:39pm

I’m a bit scared to manually close channel that are fully being managed by CLBOSS.

Ram is 16 GB, disk is a 4 TB M2 SSD, so those shouldn’t cause any issues.

Thanks for the hint with TOR restarting, that’s a thing I will try if it happens again. Still waiting for the resync.

StuPleb · January 16, 2025, 4:26pm

If you closed a channel, CLBOSS would make use of the returned funds, but it wouldn’t do anything else and it wouldn’t break things.

tennis · January 18, 2025, 7:11am

Ok, so here is what I changed:

Rescanned the blockchain on Core-Lightning Service
Reset TOR
Added IPv4 Support as described here:
Restart of the host, restart of the Apps
Switched to experimental “xpay”.

Still, my node does not route anything it seems.

Can this be, that because of the change to IPv4, my channel peers no longer recognize me now? Amboss for instance, sees the same node-id with my clearnet address now.

@StuPleb: If this is a shitty channel, how do I find it and shouldn’t it be closed by CLBOSS directly?

Here is the log of core-lightning:


2025-01-18T06:30:56.496Z INFO lightningd: Sending 60949579msat over 9 hops to deliver 60940000msat

2025-01-18T06:31:00.612Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:01.103Z INFO lightningd: Sending 60952846msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:01.625Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:02.882Z INFO lightningd: Sending 60966366msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:22.453Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:22.743Z INFO lightningd: Sending 60948116msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:37.147Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:37.147Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:37.779Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:37.779Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:40.092Z INFO lightningd: Sending 60949702msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:40.115Z INFO lightningd: Sending 60950315msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:40.141Z INFO lightningd: Sending 60949406msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:40.158Z INFO lightningd: Sending 60946826msat over 7 hops to deliver 60940000msat

2025-01-18T06:31:44.422Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:44.711Z INFO lightningd: Sending 60945825msat over 7 hops to deliver 60940000msat

2025-01-18T06:31:48.251Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:49.565Z INFO lightningd: Sending 60950168msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:51.357Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:51.858Z INFO lightningd: Sending 60943628msat over 8 hops to deliver 60940000msat

2025-01-18T06:31:53.697Z INFO plugin-clboss: InternetConnectionMonitor: online.

2025-01-18T06:31:53.700Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:53.995Z INFO lightningd: Sending 60945825msat over 7 hops to deliver 60940000msat

2025-01-18T06:31:58.371Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:31:59.314Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:00.059Z INFO lightningd: Sending 60950407msat over 9 hops to deliver 60940000msat

2025-01-18T06:32:00.086Z INFO lightningd: Sending 60943628msat over 8 hops to deliver 60940000msat

2025-01-18T06:32:03.607Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 4th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:04.162Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:04.528Z INFO lightningd: Sending 60965829msat over 5 hops to deliver 60940000msat

2025-01-18T06:32:04.585Z INFO lightningd: Sending 60948204msat over 6 hops to deliver 60940000msat

2025-01-18T06:32:38.729Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:39.318Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:39.319Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:39.319Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 4th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:39.998Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:41.586Z INFO lightningd: Sending 60949616msat over 9 hops to deliver 60940000msat

2025-01-18T06:32:41.826Z INFO lightningd: Sending 60948957msat over 8 hops to deliver 60940000msat

2025-01-18T06:32:41.868Z INFO lightningd: Sending 60945984msat over 8 hops to deliver 60940000msat

2025-01-18T06:32:41.896Z INFO lightningd: Sending 60961770msat over 7 hops to deliver 60940000msat

2025-01-18T06:32:41.924Z INFO lightningd: Sending 60945460msat over 7 hops to deliver 60940000msat

2025-01-18T06:32:47.969Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:48.692Z INFO lightningd: Sending 60942947msat over 9 hops to deliver 60940000msat

2025-01-18T06:32:48.935Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:49.589Z INFO lightningd: Sending 60949237msat over 8 hops to deliver 60940000msat

2025-01-18T06:32:49.832Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:50.148Z INFO lightningd: Sending 60947824msat over 6 hops to deliver 60940000msat

2025-01-18T06:32:50.962Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:50.963Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:52.742Z INFO lightningd: Sending 60944786msat over 8 hops to deliver 60940000msat

2025-01-18T06:32:52.760Z INFO lightningd: Sending 60953905msat over 10 hops to deliver 60940000msat

2025-01-18T06:32:57.419Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:58.113Z INFO lightningd: Sending 60946897msat over 7 hops to deliver 60940000msat

2025-01-18T06:32:58.361Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:32:58.904Z INFO lightningd: Sending 60943689msat over 8 hops to deliver 60940000msat

2025-01-18T06:33:02.798Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:03.132Z INFO lightningd: Sending 60946057msat over 7 hops to deliver 60940000msat

2025-01-18T06:33:03.667Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:03.668Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:05.497Z INFO lightningd: Sending 60952532msat over 9 hops to deliver 60940000msat

2025-01-18T06:33:05.518Z INFO lightningd: Sending 60949444msat over 7 hops to deliver 60940000msat

2025-01-18T06:33:19.183Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:19.881Z INFO lightningd: Sending 60954322msat over 8 hops to deliver 60940000msat

2025-01-18T06:33:21.262Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:21.263Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:22.028Z INFO lightningd: Sending 60948336msat over 8 hops to deliver 60940000msat

2025-01-18T06:33:22.183Z INFO lightningd: Sending 60946118msat over 7 hops to deliver 60940000msat

2025-01-18T06:33:25.301Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 4th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:26.565Z INFO lightningd: Sending 60952532msat over 9 hops to deliver 60940000msat

2025-01-18T06:33:29.343Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:29.899Z INFO lightningd: Sending 60949444msat over 7 hops to deliver 60940000msat

2025-01-18T06:33:33.182Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:33.869Z INFO lightningd: Sending 60945293msat over 8 hops to deliver 60940000msat

2025-01-18T06:33:39.901Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:40.419Z INFO lightningd: Sending 60948340msat over 7 hops to deliver 60940000msat

2025-01-18T06:33:43.310Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:43.311Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:44.828Z INFO lightningd: Sending 60949773msat over 8 hops to deliver 60940000msat

2025-01-18T06:33:44.847Z INFO lightningd: Sending 60944157msat over 6 hops to deliver 60940000msat

2025-01-18T06:33:45.286Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:45.859Z INFO lightningd: Sending 60944825msat over 8 hops to deliver 60940000msat

2025-01-18T06:33:54.712Z INFO plugin-clboss: ChannelCandidateInvestigator: Best candidates: 02b56712f65c281a1eacee0bb034699a716535a1c8ae1c912e232893d4ad27d3a7(24), 02c3ce96ca5006e06e0513f46c1e964cfa5a2cb1a765c74799c6d88535d81ca4d5(24), 02ca8d072374c685cb7e8fb24c1f1b2e7de6c43b8ffe89acb23377c5ff09f1d0dc(24), 02972e2342498fa91691dc5efd0deeb3dc7877b2f3d68ba9a698cf276b1d5de6ca(24), 033e9ce4e8f0e68f7db49ffb6b9eecc10605f3f3fcb3c630545887749ab515b9c7(24), 02f460ae6d3d3e104f8afe520ae0cff3d94c35c2ba8df66da89f3c8006a265b90a(24), 025ae40275ff32c9461ea7f65aa7ac8cdbf83814d2d9d2c402262fdcf69fd1f3d4(24) ... 25 candidates.

2025-01-18T06:33:54.726Z INFO plugin-clboss: Connector: connected to 02b56712f65c281a1eacee0bb034699a716535a1c8ae1c912e232893d4ad27d3a7

2025-01-18T06:33:54.727Z INFO plugin-clboss: Connector: connected to 03910da61c1b42e135f134ed92a537c758d1edac5436efbec5ee8cec1928e1a095

2025-01-18T06:33:54.740Z INFO plugin-clboss: Connector: connected to 02f1a8c87607f415c8f22c00593002775941dea48869ce23096af27b0cfdcc0b69

2025-01-18T06:33:54.835Z INFO plugin-clboss: Connector: connected to 02977d1f5235b37ed63497e6bc3c165e4e70583eea6d967d0fff8cddc96286e7bc

2025-01-18T06:33:54.873Z INFO plugin-clboss: Connector: connected to 03d35779ff612c574b92494d74300ce467e0eb510181a6ae3eb74d8ada891d82aa

2025-01-18T06:33:54.874Z INFO plugin-clboss: Connector: connected to 03cc1d0932bb99b0697f5b5e5961b83ab7fd66f1efc4c9f5c7bad66c1bcbe78f02

2025-01-18T06:33:54.875Z INFO plugin-clboss: Connector: connected to 039edc94987c8f3adc28dab455efc00dea876089a120f573bd0b03c40d9d3fb1e1

2025-01-18T06:33:54.894Z INFO plugin-clboss: Connector: connected to 0294ac3e099def03c12a37e30fe5364b1223fd60069869142ef96580c8439c2e0a

2025-01-18T06:33:55.095Z INFO lightningd: Sending 60945618msat over 4 hops to deliver 60940000msat

2025-01-18T06:33:55.510Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:33:56.227Z INFO lightningd: Sending 60950421msat over 7 hops to deliver 60940000msat

2025-01-18T06:34:03.706Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:04.209Z INFO lightningd: Sending 60946740msat over 8 hops to deliver 60940000msat

2025-01-18T06:34:20.760Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:20.761Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:22.549Z INFO lightningd: Sending 60945520msat over 8 hops to deliver 60940000msat

2025-01-18T06:34:22.566Z INFO lightningd: Sending 60966475msat over 8 hops to deliver 60940000msat

2025-01-18T06:34:39.762Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:39.762Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:40.110Z INFO lightningd: Sending 60945618msat over 5 hops to deliver 60940000msat

2025-01-18T06:34:40.127Z INFO lightningd: Sending 60945923msat over 7 hops to deliver 60940000msat

2025-01-18T06:34:46.261Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:46.987Z INFO lightningd: Sending 60945095msat over 7 hops to deliver 60940000msat

2025-01-18T06:34:48.467Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:49.001Z INFO lightningd: Sending 60948143msat over 9 hops to deliver 60940000msat

2025-01-18T06:34:56.278Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:56.278Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:57.011Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:57.011Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:57.854Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:34:58.051Z INFO lightningd: Sending 60945071msat over 8 hops to deliver 60940000msat

2025-01-18T06:34:59.076Z INFO lightningd: Sending 60967175msat over 8 hops to deliver 60940000msat

2025-01-18T06:34:59.142Z INFO lightningd: Sending 60945461msat over 8 hops to deliver 60940000msat

2025-01-18T06:34:59.157Z INFO lightningd: Sending 60943791msat over 5 hops to deliver 60940000msat

2025-01-18T06:34:59.171Z INFO lightningd: Sending 60947445msat over 9 hops to deliver 60940000msat

2025-01-18T06:35:01.267Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:01.797Z INFO lightningd: Sending 60943791msat over 8 hops to deliver 60940000msat

2025-01-18T06:35:03.801Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:04.404Z INFO lightningd: Sending 60944851msat over 9 hops to deliver 60940000msat

2025-01-18T06:35:04.425Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 0th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:04.626Z INFO lightningd: Sending 60944718msat over 4 hops to deliver 60940000msat

2025-01-18T06:35:39.618Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:39.618Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:39.619Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:39.619Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:40.186Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 0th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:42.350Z INFO lightningd: Sending 60952443msat over 9 hops to deliver 60940000msat

2025-01-18T06:35:42.371Z INFO lightningd: Sending 60943791msat over 8 hops to deliver 60940000msat

2025-01-18T06:35:42.391Z INFO lightningd: Sending 60947457msat over 9 hops to deliver 60940000msat

2025-01-18T06:35:42.408Z INFO lightningd: Sending 60946397msat over 6 hops to deliver 60940000msat

2025-01-18T06:35:42.427Z INFO lightningd: Sending 60947483msat over 6 hops to deliver 60940000msat

2025-01-18T06:35:44.721Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:45.309Z INFO lightningd: Sending 60944851msat over 7 hops to deliver 60940000msat

2025-01-18T06:35:49.235Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:49.349Z INFO lightningd: Sending 60942950msat over 5 hops to deliver 60940000msat

2025-01-18T06:35:49.796Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:50.380Z INFO lightningd: Sending 60944851msat over 7 hops to deliver 60940000msat

2025-01-18T06:35:53.159Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:53.159Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:53.912Z INFO lightningd: Sending 60948765msat over 6 hops to deliver 60940000msat

2025-01-18T06:35:53.930Z INFO lightningd: Sending 60943791msat over 7 hops to deliver 60940000msat

2025-01-18T06:35:55.727Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:56.271Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:56.479Z INFO lightningd: Sending 60947457msat over 7 hops to deliver 60940000msat

2025-01-18T06:35:56.516Z INFO lightningd: Sending 60947227msat over 5 hops to deliver 60940000msat

2025-01-18T06:35:59.418Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:59.419Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 5th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:35:59.419Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:01.455Z INFO lightningd: Sending 60948765msat over 6 hops to deliver 60940000msat

2025-01-18T06:36:01.472Z INFO lightningd: Sending 60952443msat over 9 hops to deliver 60940000msat

2025-01-18T06:36:01.504Z INFO lightningd: Sending 60944851msat over 7 hops to deliver 60940000msat

2025-01-18T06:36:04.265Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:04.783Z INFO lightningd: Sending 60943791msat over 7 hops to deliver 60940000msat

2025-01-18T06:36:05.383Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:05.470Z INFO lightningd: Sending 60945618msat over 5 hops to deliver 60940000msat

2025-01-18T06:36:25.926Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:26.213Z INFO lightningd: Sending 60948765msat over 6 hops to deliver 60940000msat

2025-01-18T06:36:36.942Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:36.943Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 5th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:36.944Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:37.523Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:39.857Z INFO lightningd: Sending 60948179msat over 8 hops to deliver 60940000msat

2025-01-18T06:36:39.879Z INFO lightningd: Sending 60947191msat over 8 hops to deliver 60940000msat

2025-01-18T06:36:39.900Z INFO lightningd: Sending 60967175msat over 8 hops to deliver 60940000msat

2025-01-18T06:36:39.926Z INFO lightningd: Sending 60943791msat over 7 hops to deliver 60940000msat

2025-01-18T06:36:40.138Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:40.269Z INFO lightningd: Sending 60945618msat over 5 hops to deliver 60940000msat

2025-01-18T06:36:40.953Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:41.281Z INFO lightningd: Sending 60944157msat over 7 hops to deliver 60940000msat

2025-01-18T06:36:47.245Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:47.823Z INFO lightningd: Sending 60947191msat over 8 hops to deliver 60940000msat

2025-01-18T06:36:48.065Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:48.600Z INFO lightningd: Sending 60943791msat over 7 hops to deliver 60940000msat

2025-01-18T06:36:49.096Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:49.245Z INFO lightningd: Sending 60945618msat over 5 hops to deliver 60940000msat

2025-01-18T06:36:50.857Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:51.487Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:52.810Z INFO lightningd: Sending 60952601msat over 9 hops to deliver 60940000msat

2025-01-18T06:36:52.846Z INFO lightningd: Sending 60951201msat over 8 hops to deliver 60940000msat

2025-01-18T06:36:54.601Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:55.207Z INFO lightningd: Sending 60947191msat over 8 hops to deliver 60940000msat

2025-01-18T06:36:56.865Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:57.433Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:36:57.456Z INFO lightningd: Sending 60943791msat over 7 hops to deliver 60940000msat

2025-01-18T06:36:57.569Z INFO lightningd: Sending 60945618msat over 5 hops to deliver 60940000msat

2025-01-18T06:37:00.294Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:00.614Z INFO lightningd: Sending 60944157msat over 7 hops to deliver 60940000msat

2025-01-18T06:37:00.948Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:01.552Z INFO lightningd: Sending 60947191msat over 8 hops to deliver 60940000msat

2025-01-18T06:37:05.679Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:05.679Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:05.680Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:05.680Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:08.160Z INFO lightningd: Sending 60945618msat over 5 hops to deliver 60940000msat

2025-01-18T06:37:08.174Z INFO lightningd: Sending 60961404msat over 7 hops to deliver 60940000msat

2025-01-18T06:37:08.201Z INFO lightningd: Sending 60943791msat over 7 hops to deliver 60940000msat

2025-01-18T06:37:08.323Z INFO lightningd: Sending 60950531msat over 8 hops to deliver 60940000msat

2025-01-18T06:37:25.471Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:26.025Z INFO lightningd: Sending 60957869msat over 7 hops to deliver 60940000msat

2025-01-18T06:37:31.227Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:31.559Z INFO lightningd: Sending 60950251msat over 7 hops to deliver 60940000msat

2025-01-18T06:37:42.112Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 1th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:42.226Z INFO lightningd: Sending 60943791msat over 5 hops to deliver 60940000msat

2025-01-18T06:37:43.942Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:44.485Z INFO lightningd: Sending 60943340msat over 9 hops to deliver 60940000msat

2025-01-18T06:37:45.268Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:45.269Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:46.086Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 3th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:46.087Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 0th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:47.064Z INFO lightningd: Sending 60950235msat over 8 hops to deliver 60940000msat

2025-01-18T06:37:47.390Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 2th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

2025-01-18T06:37:47.876Z INFO lightningd: Sending 60952616msat over 8 hops to deliver 60940000msat

2025-01-18T06:37:48.134Z INFO lightningd: Sending 60943791msat over 5 hops to deliver 60940000msat

2025-01-18T06:37:48.155Z INFO lightningd: Sending 60950056msat over 10 hops to deliver 60940000msat

2025-01-18T06:37:48.203Z INFO lightningd: Sending 60946594msat over 8 hops to deliver 60940000msat

2025-01-18T06:37:52.378Z INFO 024a8228d764091fce2ed67e1a7404f83e38ea3c7cb42030a2789e73cf3b341365-chan#7: htlc failed from 0th node with code 0x1007 (WIRE_TEMPORARY_CHANNEL_FAILURE)

StuPleb · January 18, 2025, 12:08pm

I can’t say that I have an exact answer for you.

I have no true idea whether you should be routing. Just because you’ve seen these probing attempts, it does not mean you would have routed if it didn’t fail.
I don’t actually know what CLBOSS would do if it encountered a specific channel and a route through that channel that kept failing. I know CLN is weaker than LND in this regard generally. I just don’t know the ins and outs of CLBOSS.