--- Log opened Sat May 25 00:00:22 2019 01:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 01:47 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 01:55 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 02:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 02:07 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds] 02:47 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning 03:04 <@cdecker> darosior: I usually try to fix them before finishing the PR, if one slipped through feel free to take it over :-) 03:25 < m-schmoock> cdecker: do you also havve these annoying stacktrace dumps when shutting down the daemon? https://github.com/ElementsProject/lightning/issues/2677 03:45 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 03:45 <@cdecker> Not really, looks like it is attempting to talk to the owner but the channel is unowned (or has been freed before) 03:50 < m-schmoock> I really have this each time i shotdown on all of my machines 03:50 < m-schmoock> I cant remeber a time this didnt happen, so i thought this was kinda normal 03:50 < m-schmoock> (thought I cant be the only one) 03:50 < m-schmoock> anyway, now its an open issue :D 03:51 <@cdecker> Ok, then we likely have some ownership the wrong way around 03:52 <@cdecker> Yeah, the subdaemon is exiting, the daemon wants to re-assign the owner and runs into trouble while de-allocating 03:54 < m-schmoock> Why am I the only one having this like each time? Bad luck? 03:55 < m-schmoock> maybe OS archlinux related 03:56 < m-schmoock> I also see these in the logs before the crash: lightning_connectd(15896): Status closed, but waitpid 15896 says No child processe 03:56 < m-schmoock> and lightning_gossipd(15897): Status closed, but waitpid 15897 says No child processes 03:56 < m-schmoock> then after the timeout I have the crash 03:56 < m-schmoock> 'crash' , it was supposed to shutdown anway 03:58 < m-schmoock> cdecker: I added another stacktrace to the Issue #2677 that just happend with the same cause and symptom 03:58 < m-schmoock> The second one is less often 04:12 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 04:26 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has joined #c-lightning 05:58 -!- trueptolemy [2e1da31c@gateway/web/freenode/ip.46.29.163.28] has joined #c-lightning 06:16 < t0mix> roasbeef: just because the block height is different, my node (or the other) will assume that commitment was closed onchain? (just to make sure I'm not mistaken, commitment = funding transaction? ) 06:19 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 06:20 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 06:34 -!- justan0theruser is now known as justanotheruser 07:13 -!- trueptolemy [2e1da31c@gateway/web/freenode/ip.46.29.163.28] has quit [Ping timeout: 256 seconds] 07:50 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 07:54 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds] 08:21 -!- Kostenko [~Kostenko@176.78.154.81] has quit [Ping timeout: 248 seconds] 08:22 < jb55> so I loaded all my keys into core and it matches clightnings listfunds outputs. (just checking ;) although there is a random null-address output that doesn't look value in my db 08:22 < jb55> not sure how that got there 08:22 < jb55> doesn't look valid* 08:28 < jb55> the way you do this: clightning-dumpkeys now exports combo output descriptors like so: https://jb55.com/s/0ef72793201d7125.txt which you can import into core with importmulti. combo just means it will import all pkh, sh_wpkh and wpkh keys on the bip32 path 08:33 -!- Kostenko [~Kostenko@dsl-154-81.bl26.telepac.pt] has joined #c-lightning 08:37 -!- Kostenko [~Kostenko@dsl-154-81.bl26.telepac.pt] has quit [Remote host closed the connection] 08:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 09:03 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 09:03 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 09:08 -!- booyah_ [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 09:09 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 09:11 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Remote host closed the connection] 09:11 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has joined #c-lightning 09:12 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 09:23 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 09:23 -!- booyah_ [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 09:51 -!- darosior [52ff9820@gateway/web/freenode/ip.82.255.152.32] has quit [Quit: Page closed] 10:03 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 11:12 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 11:21 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 12:08 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 15:13 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:38 < grubles> is it possible to turn off routeboost while online? 15:42 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 16:31 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 16:33 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 248 seconds] 16:43 -!- justan0theruser is now known as justanotheruser 17:14 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning 21:58 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] --- Log closed Sun May 26 00:00:23 2019