--- Log opened Wed Dec 04 00:00:27 2019
00:14 -!- kabaum [~kabaum@185.224.57.161] has joined #c-lightning
00:23 -!- Netsplit *.net <-> *.split quits: Nebraskka, t0mix, kristapsk_, wraithm, cryptosoap, afk11, ghost43, jb55, lowentropy, GAit
00:24 -!- Netsplit *.net <-> *.split quits: nothingmuch, m-schmoock, RubenSomsen, berndj, achow101, RonNa, cncr04s, darosior, harding, midnight,  (+41 more, use /NETSPLIT to show all of them)
00:24 -!- Netsplit over, joins: kabaum, justan0theruser, jb55, reallll, lowentropy, dr-orlovsky, CubicEarth, achow101, jonasschnelli, drolmer_ (+51 more)
00:47 -!- kabaum [~kabaum@185.224.57.161] has quit [Ping timeout: 268 seconds]
00:58 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:00 -!- kabaum [~kabaum@ec2-52-212-246-229.eu-west-1.compute.amazonaws.com] has joined #c-lightning
01:02 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
01:03 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:08 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 250 seconds]
01:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:15 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:20 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
01:22 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:27 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 276 seconds]
01:30 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:36 -!- kabaum [~kabaum@ec2-52-212-246-229.eu-west-1.compute.amazonaws.com] has quit [Ping timeout: 240 seconds]
01:51 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
01:53 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 276 seconds]
02:02 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:07 -!- orlovsky [~dr-orlovs@2a02:1205:500f:2e90:44e8:6142:feef:d44f] has joined #c-lightning
02:09 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
02:10 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:10 -!- dr-orlovsky [~dr-orlovs@2a02:1205:500f:2e90:d009:4f2d:a9d0:a572] has quit [Ping timeout: 276 seconds]
02:14 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
02:15 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:19 -!- kabaum [~kabaum@ec2-52-212-246-229.eu-west-1.compute.amazonaws.com] has joined #c-lightning
02:24 < m-schmoock> darosior: thx for your response :D
02:25 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 276 seconds]
02:26 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
02:27 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:32 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 276 seconds]
02:33 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:37 < darosior> m-schmoock: I almost proposed "stuffed the stuff" as a name ^^
02:37 < m-schmoock> hehe
02:38 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
02:38 < m-schmoock> Carbon Neutral Mining Algorithm   is very good because stupid political populism included
02:42 < m-schmoock> there are quite a few good proposals, gonna be hard to pick one and drop the others :D
02:45 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:50 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
02:51 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
02:53 -!- reallll [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
02:58 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
02:59 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:06 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
03:09 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:12 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
03:16 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
03:16 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
03:17 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:34 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
03:36 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
03:51 -!- cubancorona [~cubancoro@pool-72-77-31-161.pitbpa.ftas.verizon.net] has joined #c-lightning
03:53 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 276 seconds]
03:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning []
03:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning
04:04 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
04:05 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
04:20 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
04:23 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
04:28 < willcl_ark> I asked a little about this the other day, but, when shutting down, what exactly does C-lightnign do to plugins? My plugin is s type of server and it currently stays running; I'd like it to shutdown cleanly... I do have quite a non-standard plugin structure though...
04:29 < willcl_ark> Two approaches I've considered: watch the log for the DEBUG shutdown messages (prefer not to do this) or use rpc_command hook to takeover the `lightning-cli stop` command
04:30 -!- potatoe_face [~potatoe_f@157.230.27.253] has quit [Ping timeout: 240 seconds]
04:31 < m-schmoock> both? rpc_command hook for graceful shutdown and log parsing to abort because daemon died?
04:32 < m-schmoock> you could also have a timer calling `getinfo` once in a while
04:32 < m-schmoock> but generally the daemon should kill your plugin afaik
04:32 < m-schmoock> plugins do not stay running when daemon dies
04:32 <@cdecker> The plugin gets a SIGTERM since its parent dies, so if you have a signal handler installed it should be called before being terminated
04:32 < m-schmoock> (unless you modified it hardly)
04:36 < willcl_ark> m-schmoock: my plugin runs within Trio, the plugin is run as a sub-thread, so that it why it stays alive. I will try to catch the SIGTERM and propagate it up though, that is more the solution-type I was searching for! Thanks each
04:43 -!- potatoe_face [~potatoe_f@157.230.27.253] has joined #c-lightning
04:43 < m-schmoock> good
04:43 < m-schmoock> I dont know trio thogh
04:44 < m-schmoock> why is it ignoring SIGTERM?
04:44 < m-schmoock> willcl_ark: sounds like a fun plugin you are workin on
04:49 <@cdecker> willcl_ark: what is Trio? Sounds like it is capturing SIGTERM already
04:49 < willcl_ark> Trio is like a fancy wrapper for python:asyncio
04:50 < willcl_ark> cdecker: here is the current structure of the plugin: https://github.com/willcl-ark/lnproxy/blob/master/scripts/gotenna-plugin.py
04:50 < willcl_ark> It's all working pretty nicely actually, excepting not being terminated every time (sometimes it is, but sometimes not)
04:54 < willcl_ark> hmmm, I think it's actually getting shutdown everytime with graceful shutdown. Perhaps it's only not getting shutdown properly when my plugin code is malformed and C-Lightning never fully loads it (and starts it's thread) or somethign like that. then C-Lightning doesn't issue the SIGKILL to it. 
04:59 <@cdecker> Interesting, I've been wanting to try the asyncio API for a while now
05:00 < willcl_ark> As I understand, Trio is not the absolute fastest, but provides a consistent (and therefore expected) interface for the programmer. It's really been nice to work with to be honest. The docs are also great. As a relative Python newbie, I would recommend :)
05:00 <@cdecker> Hm, I'll check, but I think sending the SIGTERM to children is automatic. We might now be reaping the children automatically but that should only be after the shutdown anyway
05:02 < willcl_ark> yeah I think shutdown is actually OK. I was only seeing my main loop keep running when C-Lightnign wasn't loading the plugin (and therefore not killing it afterwards either) -- my bad!
05:03 < willcl_ark> just going to try and slot in `rpc createonion` now :)
05:05 -!- kabaum [~kabaum@ec2-52-212-246-229.eu-west-1.compute.amazonaws.com] has quit [Ping timeout: 240 seconds]
05:21 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
05:23 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:28 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds]
05:29 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:35 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
05:39 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 250 seconds]
05:42 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:51 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
05:52 -!- kabaum [~kabaum@93.182.128.34] has joined #c-lightning
05:56 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:00 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds]
06:02 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:04 -!- Netsplit *.net <-> *.split quits: GAit, Nebraskka, t0mix, wraithm
06:09 -!- Netsplit over, joins: wraithm, GAit, t0mix, Nebraskka
06:13 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 252 seconds]
06:14 -!- Netsplit *.net <-> *.split quits: GAit, Nebraskka, t0mix, wraithm
06:15 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:19 -!- Netsplit over, joins: wraithm, GAit, t0mix, Nebraskka
06:22 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
06:25 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:33 -!- kabaum [~kabaum@93.182.128.34] has quit [Ping timeout: 240 seconds]
07:01 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
07:05 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:09 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 265 seconds]
07:10 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:15 -!- jonatack [~jon@213.152.162.154] has joined #c-lightning
07:19 -!- wxss [~user@mail.deeplinkmedia.com] has joined #c-lightning
07:22 -!- kabaum [~kabaum@185.224.57.161] has joined #c-lightning
07:39 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
07:47 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 250 seconds]
07:49 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:53 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 250 seconds]
08:18 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 260 seconds]
08:39 -!- kabaum [~kabaum@185.224.57.161] has quit [Ping timeout: 250 seconds]
09:53 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #c-lightning
11:50 -!- kristapsk_ is now known as kristapsk
11:57 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 276 seconds]
11:57 -!- jonatack [~jon@213.152.162.154] has quit [Ping timeout: 268 seconds]
12:02 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning []
12:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning
12:15 < kristapsk> I have strange issue with no idea how that happened, but it currently looks I could have lost all the funds in channel, before even doing any spends or forwards
12:16 < kristapsk> opened channel to Bitfinex yesterday, but in a blockchain channel point was spent some hour later, with all the funds going to some address
12:16 < kristapsk> my node still shows that channel in listfunds output, with all funds at my side
12:17 < kristapsk> at startup c-lightning outputs
12:17 < kristapsk> 2019-12-04T12:30:08.333Z UNUSUAL lightningd(4773): 033d8656219478701227199cbd6f670335c8d408a92ae88b962c49d4dc0e83e025 chan #138: Peer permanent failure in ONCHAIN: Funding transaction spent
12:17 < kristapsk> 2019-12-04T12:30:08.338Z INFO lightningd(4773): 033d8656219478701227199cbd6f670335c8d408a92ae88b962c49d4dc0e83e025 chan #138: State changed from ONCHAIN to FUNDING_SPEND_SEEN
12:18 < kristapsk> unfortunatelly, lost all the logs from specific time, when channel opening and other events happened (ran lightningd in tmux with tee to logile, without -a, lost log on restart, of course)
12:36 <@cdecker> kristapsk: seems like a unilateral close, the funds will be back eventually, once the penalty timeout expires.
12:36 <@cdecker> The fact you haven't gotten the funds back points to your node having closed the channel, can't say much more without the logs, sorry
12:36 <@cdecker> `listpeers` should likely show the timeout until the funds are back
12:37 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
12:40 < kristapsk> tnx, cdecker , "ONCHAIN:1 outputs unresolved: in 983 blocks will spend DELAYED_OUTPUT_TO_US" should be good news for me, right?
12:48 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
12:50 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
12:52 <@cdecker> Yep, that's ~6 days till you get the funds back. My guess is the other side was lnd which has some quirks in their interpretation of the spec (potential cause for the close) and it insists on these long timeouts (even though I expect that particular node to be online and able to react 24/7)...
12:54 < kristapsk> yes, I think they use LND, read that somewhere
14:15 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
14:32 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 246 seconds]
14:33 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
14:44 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
15:20 < roasbeef> better safe than sorry ;) 
15:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
15:58 -!- mdunnio [~mdunnio@207.229.172.161] has joined #c-lightning
16:40 -!- mdunnio [~mdunnio@207.229.172.161] has quit [Remote host closed the connection]
16:41 -!- mdunnio [~mdunnio@207.229.172.161] has joined #c-lightning
16:42 -!- mdunnio [~mdunnio@207.229.172.161] has quit [Remote host closed the connection]
16:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
18:38 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning []
20:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning
20:22 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
20:23 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
21:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 260 seconds]
21:36 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds]
21:36 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Ping timeout: 260 seconds]
21:37 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 260 seconds]
21:37 -!- _andrewtoth_ [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Ping timeout: 260 seconds]
21:37 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has quit [Ping timeout: 260 seconds]
21:58 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
22:02 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has joined #c-lightning
22:03 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
22:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
23:10 -!- kabaum [~kabaum@2001:9b1:efd:9b00::281] has joined #c-lightning
--- Log closed Thu Dec 05 00:00:28 2019