--- Log opened Tue Jan 08 00:00:14 2019 01:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 01:13 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:19 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning 02:05 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:19 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:19 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 02:24 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:26 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 02:44 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:44 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 02:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:53 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:02 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:08 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:08 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:43 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 03:43 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:54 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 03:58 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:49 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:53 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 04:53 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:59 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 250 seconds] 04:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:03 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 05:04 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:09 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 05:13 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:40 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 05:45 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Remote host closed the connection] 05:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:50 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 06:19 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:19 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 06:24 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:34 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:34 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:43 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:43 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:03 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 07:03 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:09 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 07:13 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:25 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning 07:33 -!- deusexbeer [~deusexbee@080-250-076-070-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 244 seconds] 07:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:43 < ctrlbreak> cdecker, George, FWIW - I too encountered a pinned gossipd thread on my node a few days back. It also chewed ~14GB of RAM. https://imgur.com/a/nGZj4wV 07:44 < ctrlbreak> I appealed to the channel to try and assist in gathering some debug information, but didn't receive any feedback from anyone :-/ I tried to use dev-memleak and dev-memdump to gather as much data as I could. I also then called dev-crash to hopefully get something of value in a crashdump? 07:45 < ctrlbreak> I also run with DEBUG level logging and have all of the above mentioned output still available if anyone thinks it would be of any help. 07:46 <@cdecker> Awesome, thanks for the effort ctrlbreak, and sorry for not getting back to you sooner. 07:46 < ctrlbreak> no worries... 07:46 < ctrlbreak> I've just installed gperf 07:47 <@cdecker> We're also running a few nodes, and trying to reproduce the issue 07:47 <@cdecker> Hopefully together we can track it down and squash it ^^ 07:47 < ctrlbreak> and I'm trying out that shell command to ensure I have the syntax correct for if I manage to catch it again. 07:48 <@cdecker> That's an impressive machine btw :-) 07:48 < ctrlbreak> Should we be using 'perf'... or 'gperf' ? 07:48 <@cdecker> `gperf` is the package and `perf` is the command (might be that some distros alias gperf to call perf 07:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:49 <@cdecker> I;m trying to generate a flamegraph like this btw http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html 07:50 < ctrlbreak> cdecker: Thanks ;-) I have a DELL R810 with 80 cpu threads and 192GB of RAM.... and ESX for VMs. I'm trying to learn as much as I can: https://imgur.com/a/K2QJrlj 07:50 < ctrlbreak> I have gperf installed... but 'perf' tells me I need 'linux-tools-common' (Ubuntu 16.04). 07:50 < ctrlbreak> I'll install that package and try again. 07:53 < ctrlbreak> Also, FWIW... I'm trying to coordinate with molz on testnet to see if I can successfully reproduce the issue Rusty's fix is intended to prevent: https://github.com/rustyrussell/lightning/commit/de2569200d43169caebc0d285e1277816dffd2c5 07:54 <@cdecker> Awesome thanks ctrlbreak, that'd be great 07:55 < ctrlbreak> So far I don't believe anyones been able to reproduce it on demand? I know very little... and I'm not a dev, but I do have a knack for breaking things (sorry-not-sorry) 07:58 < molz> you have my 👍👍 haha.. :D yep i want to see if we can reproduce this crash.. I don't have a c-lightning node on mainnet but i have 3 on testnet and so far they haven't crashed so i'm scratching my head wondering what's going on 07:59 < molz> i don't believe it's a DDOS attack, it was said by a clueless core troll on their slack but i don't believe it is 08:04 < ctrlbreak> Anyone provide me some clarity here? :-/ I do appear to have 2 different binaries for perf and gperf :-S 08:04 < ctrlbreak> https://imgur.com/a/Tr8jNno 08:06 < ctrlbreak> Wow... flame graphs are cool :-) 08:08 <@cdecker> Hm, absolutely no idea what gperf is then :-S 08:08 <@cdecker> Yeah, flamegraphs are amazing, I used them to optimize the blockchain sync last time 08:11 < ctrlbreak> k... I'll mess with this for a bit to see if I can get it working and report the syntax that worked for me? 08:11 < ctrlbreak> I'm now seeing: sudo perf record -F 99 -p $(pgrep -f lightning_gossipd) -q -- sleep 180 08:11 < ctrlbreak> Workload failed: No such file or directory 08:11 < ctrlbreak> which seems much closer and is probably something trivial. 08:13 <@cdecker> Whoops, so the subshell containing `pgrep` is just to get the PID of the gossipd, you can probably get that from `ps aux` as well 08:13 <@cdecker> (just thought provinding a single command might be easier) 08:13 < ctrlbreak> It may be... it may be that my particular install is wonky :-P 08:14 <@cdecker> I found `perf` to be weird, since it attaches to the process specified with `-p` but waits for the command provided after `--` to terminate before exiting 08:14 < ctrlbreak> working through the syntax of "perf help record" now to try and understand it. 08:15 < ctrlbreak> Ahh... Duh, I'm running this straight from the shell and not wrapped in script. 08:16 <@cdecker> I also needed to allow ptrace to attach to a remote process btw: `echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope` 08:18 < ctrlbreak> Hum... switching gears to try and use the gperf binary. What version do you run and what's the intention of the -q param? 08:18 < ctrlbreak> I don't appear to have a -q 08:18 < ctrlbreak> ghtning:~⟫ gperf --version 08:18 < ctrlbreak> GNU gperf 3.0.4 08:19 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 08:19 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 08:21 <@cdecker> Oh wow, gperf is something completely unrelated :-) 08:21 <@cdecker> man: "generate a perfect hash function from a key set" definitely not what we want 08:23 <@cdecker> The needed packages for ubuntu are: linux-tools-common and linux-tools-generic 08:23 < ctrlbreak> lol. I should have noticed that. 08:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 08:23 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 08:25 < ctrlbreak> Hmmm... may want to let George know? " George: I think a profile might be what we're looking for, could you install the `gperf` package (assuming you are using a debian based distro)" 08:26 < ctrlbreak> unless there is a GNU perf package named 'gperf'???!? Arrgghhhh! 08:26 <@cdecker> Lemme see if I can find him on slack 08:27 < ctrlbreak> On my Ubuntu 16.04 instance, I've had to install these so far: 08:27 < ctrlbreak> linux-tools-common.. 08:27 < ctrlbreak> and a package for my specific kernel? 08:27 < ctrlbreak> linux-tools-4.4.0-112-generic 08:28 <@cdecker> Sounds like `linux-tools-generic` is an alias for the kernel specific variant 08:29 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 08:29 < ctrlbreak> Ahh... gotcha. 08:29 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 08:29 < ctrlbreak> I probably missed linux-tools-generic and apt pointed me to the specific pkg I needed. 08:33 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 08:33 < ctrlbreak> Here's a dumb question... 08:34 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 08:34 < ctrlbreak> How many instances of lightning_gossipd should be running? 08:36 < ctrlbreak> Because I've discovered the only reason why your syntax wasn't working for me. perf -p expects a list of 1 or more PIDs *comma separated*. Subshell with pgrep as is would work if there's a single gossipd instance... but I appear to have 2 09:04 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 09:04 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 09:14 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:14 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving] 09:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 09:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:43 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 09:43 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:48 < blockstream_bot> [George Vaccaro, Blockstream] @ctrlbreak thanks for the info. I thought it was maybe something specific to my node. Good to know it's not. 10:04 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 10:04 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 10:08 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 10:08 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 10:19 <@cdecker> ctrlbreak: I see, that's probably because you're missing PR #2224 (which was only merged yesterday). Before that we'd have a test start not being reaped correctly 10:28 < ctrlbreak> So there *shouldn't* be two instances of lightning_gossipd ? Any idea how I can perhaps identify the PID that shouldn't be? 10:29 < ctrlbreak> Hmmm... they both have the same parent PID :-S 10:30 < ctrlbreak> Hmmm... debug logging is only logging messages from one of them. Wonder if I can just kill the other. 10:32 < ctrlbreak> Interesting. It must have been a process I missed when I encountered the last instance of this thread pinning issue. After I called dev-crash, I noticed I had a bunch of PIDs I manually killed before restarting. I must have missed one. 10:42 < ctrlbreak> Ah... I see what you mean now. I *need* to have that PR compiled in to correct this, pretty much. 10:43 < ctrlbreak> Okay. Master compiled and restarted. 10:44 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 10:51 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 11:09 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 11:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 11:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 11:13 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 12:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 12:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 13:03 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 13:03 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 13:08 -!- deusexbeer [~deusexbee@080-250-075-250-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 14:26 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:32 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 14:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:05 < grubles> is spruned still stable enough for c-lightning? 15:15 < rusty> grubles: I've never used it, but cdecker does for some nodes. 15:18 < rusty> niftynei: so, "this time for sure"! https://github.com/ElementsProject/lightning/pull/2215 15:18 < rusty> niftynei: also, #2234 should be good for review. 15:24 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection] 15:25 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 15:37 < blockstream_bot> [George Vaccaro, Blockstream] https://files.sameroom.io/gJmShrptPdoSBRZeNaSGmUNdMWR152stPnDx_IDICV4/perf.data 15:46 < rusty> blockstream_bot: dumb qm where is the blockstream slack you are using? 15:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 15:51 < blockstream_bot> [George Vaccaro, Blockstream] Is that a q for me? if so, http://blocstream.slack.com 15:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:18 < blockstream_bot> [George Vaccaro, Blockstream] oops, typo http://blockstream.slack.com 16:48 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 16:49 < jb55> I couldn't get spruned working... 16:49 < grubles_> hm what happened? 16:49 < jb55> https://github.com/gdassori/spruned/issues/74 17:11 -!- berndj [~berndj@azna.co.za] has quit [Remote host closed the connection] 17:11 -!- berndj [~berndj@azna.co.za] has joined #c-lightning 17:13 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 17:14 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 17:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:01 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 258 seconds] 18:02 < rusty> cdecker, niftynei: many people hitting the 0-CLTV bug now. I think we need to release 0.6.3 ASAP. 0.7 with full plugin arch can come later. 18:08 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 18:14 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2] 18:15 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 18:18 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 18:30 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 18:35 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 18:41 < niftynei> ack 19:31 < rusty> https://github.com/ElementsProject/lightning/pull/2235 19:33 -!- mode/#c-lightning [+o niftynei] by ChanServ 19:34 < rusty> niftynei: think you can deop and ask chanserv to op you now... 19:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 20:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:15 < jb55> Support for pre-2-newline JSON-RPC (<= 0.6.2 lightningd) is deprecated what does this mean? Just want to make sure I don't trip up on anything when upgrading... 20:15 < jb55> oh I see: messages are now separated by 2 consecutive newlines 20:16 < jb55> ohhh use \n\n to terminate responses, for simplified parsing (pylightning now relies on this) 20:16 < jb55> this is handy, I was using a crummy hack before 20:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.2] 20:21 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:22 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 20:25 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:53 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 20:53 -!- grubles__ [~grubles@unaffiliated/grubles] has joined #c-lightning 20:54 -!- gruble___ [~grubles_@unaffiliated/grubles] has joined #c-lightning 21:02 -!- Netsplit *.net <-> *.split quits: k3m, grubles_, farmerwampum, booyah, grubles, runcrypto 21:05 -!- booyah_ is now known as booyah 21:08 < blockstream_bot> [George Vaccaro, Blockstream] Folks, regarding the high CPU thing for lightning_gossipd, I've now captured 8 separate perf.logs from separate instances throughout today that I can provide if someone would like to dig into them. Any takers? 21:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 21:09 < blockstream_bot> [Rusty Russell, Blockstream] OK, that's for Christian when he wakes... is gossipd doing it now? 21:11 < blockstream_bot> [Rusty Russell, Blockstream] Did Christian do a simple backtrace, or is he beyond that already? 21:11 -!- mode/#c-lightning [+o rusty] by ChanServ 21:12 -!- rusty changed the topic of #c-lightning to: Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.6.3rc1 Logs at http://gnusha.org/c-lightning/ 21:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:30 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 21:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 21:35 < blockstream_bot> [George Vaccaro, Blockstream] I haven't received any confirmation of him doing something with it yet. I'll DM him the perf.logs. Thanks Rusty. 21:36 < blockstream_bot> [George Vaccaro, Blockstream] Btw, for me it was always lightning_gossipd: 21:36 < blockstream_bot> [George Vaccaro, Blockstream] george 609 17.7 91.0 9564172 7437348 pts/5 R+ Jan07 375:31 /home/george/Downloads/clightning-v0.6.1/libexec/c-lightning/lightning_gossipd 21:39 -!- deusexbeer [~deusexbee@080-250-075-250-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 22:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 22:13 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 22:13 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 23:56 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] --- Log closed Wed Jan 09 00:00:15 2019