--- Log opened Sun May 08 00:00:17 2022 00:27 < laanwj> what's the most straightforward way to figure out what a peer is sending instead of the expected, for debugging? (re https://github.com/ElementsProject/lightning/issues/5243) 01:02 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning 01:03 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Remote host closed the connection] 01:04 -!- befalou [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 01:51 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Remote host closed the connection] 01:58 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 02:17 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Remote host closed the connection] 02:18 -!- befalou [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 02:52 -!- jespada [~jespada@146.70.119.114] has quit [Ping timeout: 248 seconds] 02:54 -!- jespada [~jespada@cpc121022-nmal24-2-0-cust171.19-2.cable.virginm.net] has joined #c-lightning 03:46 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 05:00 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 06:02 -!- befalou [~befalou@gateway/tor-sasl/befalou] has quit [Remote host closed the connection] 06:02 -!- befalou [~befalou@gateway/tor-sasl/befalou] has joined #c-lightning 06:25 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 256 seconds] 07:25 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 07:27 < vincenzopalazzo> laanwj: I think here rusty can know for sure the answer, looks like related to multiple channels for peer issue 07:27 < vincenzopalazzo> I noted that you are having problem also with some channel_restablish data https://github.com/ElementsProject/lightning/issues/5240 07:38 < laanwj> vincenzopalazzo: yeah i intended to do some sniffing today but didn't get around to it, well unilateral close is not nice but it works 07:39 < laanwj> vincenzopalazzo: right, although i suspect that issue is entirely unrelated 07:40 < laanwj> that one was just weird, apparantly the network connection with the peer was lost (which can happen), and immediately after reconnection the state is no longer compatible 07:40 < laanwj> and that happened three times in a day; luckily it hasn't happend since 07:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 07:53 < vincenzopalazzo> laanwj:yeah, the state mismatch can happen and it could not be related! Hopefully to get it a new proposal to prevent this force close, but send only a warning to the peer to tell that it is behind 07:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 08:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 08:15 -!- HelloShitty [~psysc0rpi@bl6-131-248.dsl.telepac.pt] has joined #c-lightning 08:33 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 09:40 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 10:40 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds] 10:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 10:51 -!- jarthur [~jarthur@user/jarthur] has quit [Quit: jarthur] 12:32 -!- jarthur [~jarthur@user/jarthur] has joined #c-lightning 13:23 -!- Guest22 [~Guest22@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 252 seconds] 16:01 -!- litch [~litch@2605:a601:aa3d:3a00:a405:7344:2ddd:4bf8] has quit [Remote host closed the connection] 16:35 -!- Guest22 [~Guest22@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has joined #c-lightning 16:40 -!- Guest22 [~Guest22@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 252 seconds] 19:02 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 240 seconds] 19:15 -!- Guest2282 [~Guest22@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has joined #c-lightning 19:15 -!- Guest2282 [~Guest22@108-228-8-99.lightspeed.sntcca.sbcglobal.net] has quit [Client Quit] 19:33 -!- litch [~litch@2605:a601:aa3d:3a00:8d61:4c8b:760:413c] has joined #c-lightning 19:40 -!- litch [~litch@2605:a601:aa3d:3a00:8d61:4c8b:760:413c] has quit [Remote host closed the connection] 19:50 -!- jarthur [~jarthur@user/jarthur] has joined #c-lightning 19:50 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 20:12 -!- jarthur_ [~jarthur@user/jarthur] has joined #c-lightning 20:15 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 250 seconds] 21:04 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has quit [Ping timeout: 240 seconds] 21:41 -!- jarthur_ [~jarthur@user/jarthur] has quit [Ping timeout: 276 seconds] 21:47 -!- jarthur [~jarthur@user/jarthur] has joined #c-lightning 22:04 -!- Netsplit *.net <-> *.split quits: kanzure, _0x0ff 22:04 -!- _0x0ff [~0x0ff@2001:bc8:47b0:123::1] has joined #c-lightning 22:04 -!- _0x0ff [~0x0ff@2001:bc8:47b0:123::1] has quit [Changing host] 22:04 -!- _0x0ff [~0x0ff@user/0x0ff/x-0302470] has joined #c-lightning 22:04 -!- Netsplit over, joins: kanzure 22:11 -!- Netsplit *.net <-> *.split quits: instagibbs, darosior 22:11 -!- Netsplit over, joins: instagibbs 22:12 -!- Netsplit over, joins: darosior 22:19 -!- evanlinjin [~evanlinji@gateway/tor-sasl/evanlinjin] has joined #c-lightning 22:46 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning 23:33 -!- cdecker [~cdecker@243.86.254.84.ftth.as8758.net] has joined #c-lightning 23:52 -!- endothermicdev [~endotherm@2600:1700:8481:8900:bb09:a7ef:a5f5:4435] has joined #c-lightning 23:54 -!- endothermicdev_ [~endotherm@99-98-58-43.lightspeed.tulsok.sbcglobal.net] has quit [Ping timeout: 246 seconds] --- Log closed Mon May 09 00:00:18 2022