--- Log opened Sun May 24 00:00:30 2020
00:27 -!- liberliver1 [~Thunderbi@x4d0bdfb4.dyn.telefonica.de] has joined #c-lightning
00:29 -!- liberliver [~Thunderbi@x4dbfeac9.dyn.telefonica.de] has quit [Ping timeout: 272 seconds]
00:29 -!- liberliver1 is now known as liberliver
01:37 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
01:38 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
03:33 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
03:38 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Ping timeout: 272 seconds]
04:04 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
04:17 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
04:18 <@cdecker> That assertion should not have triggered, is his a particularly long-lived node and has it been running some unreleased builds (maybe from master)?
04:19 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
04:19 <@cdecker> The reason I ask is that the field in question can only ever been unset if the channel was loaded from a DB before that field was added, and for the release we added a migration that'd set the field to 1
04:44 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
04:46 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
06:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
06:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
06:17 -!- felixweis [sid154231@gateway/web/irccloud.com/x-prrbldyoeyixqcwk] has quit [Ping timeout: 260 seconds]
06:35 -!- liberliver [~Thunderbi@x4d0bdfb4.dyn.telefonica.de] has quit [Ping timeout: 265 seconds]
06:40 -!- felixweis [sid154231@gateway/web/irccloud.com/x-cjypeezqhvbpncyr] has joined #c-lightning
07:47 < trobjo> The Lightning node fails to start up on testnet. It runs just fine on main.
07:47 < trobjo> https://pastebin.com/gJRjFzLK
07:51 -!- MrHash [~mrhash@189.174.156.235] has quit [Ping timeout: 256 seconds]
07:51 < trobjo> It seems to be caused by the jitrebalance, as testnet runs fine now, after disabling said plugin
07:57 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
08:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
08:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
08:06 < darosior> trobjo: thanks for the report ! I also experienced this with JITrebablance
08:06 < darosior> I'll add your report to the issue
08:10 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
08:32 < MrHash> cdecker: i'm running nodes in regtest and setting up/tearing down to reset environment. so these are nodes that start from scratch
08:32 < MrHash> i have a script with generates bitcoin blocks then immediately connects and opens a channel from lnd to clightning
08:33 < MrHash> it's an intermittent problem
08:34 < MrHash> built from 0.8.2.1
08:42 <@cdecker> Ok, if it's regtest can you share logs and DB in a GH issue? That'd make it easier to reproduce. Also if you're scripting this, could you provide the scripts, that'd be even easier for us :-)
08:42 <@cdecker> darosior, trobjo: yes, the jitrebalance plugin is a bit of an experimental one from me, sorry about the rough edges, I'll take a look
08:45 < trobjo> cdecker: that is cool, please let me know if you want further information!
08:51 <@cdecker> Hm, I think I got the problem: do you guys have channels that are not yet confirmed, i.e., do not have a fix short_channel_id yet?
09:01 < trobjo> in `lightning-cli listfunds` in the `outputs` array, I have three confirmed channels now (that is the place to look, right?). None unconfirmed. However I cannot say if it had unconfirmed channels at the time of the crash.
09:03 <@cdecker> If you look in `listpeers` each peer has a list of channels, and at least one of those channels will likely not have a `short_channel_id` field (unless the issue resolved itself by being confirmed in the meantime)
09:10 < trobjo> All of them have a short_channel_id
09:11 <@cdecker> Hm, ok, might have gotten confirmed in the meantime
09:11 <@cdecker> I think I have a test that can reproduce it though
09:12 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
09:19 < sword_smith> cdecker: trobjo's error was on test net. I don't know if that makes a difference.
09:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
09:20 <@cdecker> Not really, it's a KeyError when accessing `short_channel_id` in the dict that is returned by `listpeers`, I've reproduced it and fixing it now
09:22 < sword_smith> Alright. Cool.
09:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
09:23 -!- vasild_ is now known as vasild
09:27 <@cdecker> Ok, reproduced and fixed: https://github.com/lightningd/plugins/pull/114, darosior and trobjo can you test it and report if the issue is fixed or persists?
09:29 < darosior> cdecker: thanks ! Will test asap
09:46 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
09:46 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
09:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
10:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:04 -!- ghost43_ is now known as ghost43
11:17 -!- liberliver [~Thunderbi@x4d0bdfb4.dyn.telefonica.de] has joined #c-lightning
11:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
11:21 -!- liberliver [~Thunderbi@x4d0bdfb4.dyn.telefonica.de] has quit [Ping timeout: 246 seconds]
11:21 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
11:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
12:24 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]
12:37 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
12:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
13:01 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has joined #c-lightning
14:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
14:23 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
14:34 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
14:35 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
15:10 -!- b42 [~mmilata@b42.cz] has joined #c-lightning
15:29 < b42> hi! trying to set up a node for the first time but after "lightning-cli connect" i always get "Peer connection lost" & "Owning subdaemon openingd died"
15:30 -!- PaulTroon [~paultroon@h-5-150-248-150.NA.cust.bahnhof.se] has quit [Remote host closed the connection]
15:30 < b42> is this because the node is not announcing any addresses?
15:32 < b42> https://paste.rs/GO7
16:19 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
16:33 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
16:46 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
16:47 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
17:03 -!- masterdonx2 [~masterdon@107.181.166.56] has joined #c-lightning
17:03 -!- MasterdonX [~masterdon@84.17.53.222] has quit [Ping timeout: 256 seconds]
17:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
17:06 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
17:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 265 seconds]
17:57 < b42> same with fundchannel instead of connect - the connection is lost in <1 minute: https://paste.rs/7sN
18:24 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
19:39 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer]
20:25 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 240 seconds]
20:25 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
21:09 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:23 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:23 -!- vasild_ is now known as vasild
22:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
22:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
23:50 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
23:56 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 260 seconds]
23:56 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
--- Log closed Mon May 25 00:00:30 2020