--- Log opened Sat Jan 05 00:00:12 2019
01:04 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
01:04 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
01:08 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
01:08 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
02:58 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:58 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
03:14 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:00 < ungenannter> grubles_: yes, It's hard to debug as A is an android device :). Since b could not make payments back to a, b opened a new channel to ACINQ (20 usd). Should be enough to send 1 sat :) 
05:52 <@cdecker> ungenannter: probably :-)
05:52 <@cdecker> ungenannter: depending on the balances you might be hitting against the 1% reserve value
05:53 <@cdecker> ungenannter: that's a minimum balance that you're not allowed to tap into
05:54 <@cdecker> So if you have a 100sat channel A->B in which A owns all 100sat, then A can send up to 99 to B, but B can subsequently only send 98 back, otherwise he'd dip below the 1sat reserve
05:54 <@cdecker> It's an ugly corner case that people keep running into
05:57 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
06:02 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
06:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 272 seconds]
07:32 -!- deusexbeer [~deusexbee@080-250-077-203-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 258 seconds]
07:38 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
08:02 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 272 seconds]
08:24 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Quit: farmerwampum]
08:24 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
08:28 -!- farmerwampum [~farmerwam@184.75.210.234] has quit [Client Quit]
08:28 -!- farmerwampum [~farmerwam@184.75.210.234] has joined #c-lightning
08:34 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds]
08:39 < grubles_> by "android device" do you mean you're using the eclair android app? i don't think that can receive payments yet.
09:00 < ctrlbreak> Oh oh....
09:00 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection]
09:01 < ctrlbreak> something is definitely up with my (master) CL node.  I have a hung lightning_gossipd that has pinned a CPU and has consumed ~14GB of RAM :-S
09:02 < ctrlbreak> Is there some way I can grab useful debug information?  I have dev options compiled in, btw...
09:04 < ctrlbreak> call dev-crash and collect a crashdump?
09:04 < ctrlbreak> Hmmm, dev-memdump and dev-memleak too....
09:11 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning
09:18 < ungenannter> cdecker: a has a channel with a capacity of 428064 sat, can send 60186 sat and receive 358412 sat
09:19 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection]
09:19 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning
09:20 < ungenannter> grubles_: with android devic I mean lightning-wallet.com. btw: a and b did a lot of transactions in the past (back and forth), so it works basically
09:21 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection]
09:22 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning
09:28 < ungenannter> https://i.postimg.cc/4xQzPBF6/photo-2019-01-05-13-14-08.jpg
09:28 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
09:50 < ctrlbreak> Okay... that was a bad one.  Had many hung child PIDs that needed to be killed manually :-S.  I seem to have been able to restart without issue and all *appears* well.  However, I'd really appreciate if maybe someone could outline some steps I could take if the situation happens again to try and gather some useful debug information to assist the project in finding out what's breaking and where.  I have dev options compiled in, but apparently I'm 
09:50 < ctrlbreak> missing something for dev-memleaks to work properly (I didn't note the reponse from lightningd; sorry).  I also run with full DEBUG logging if that's of any help?  Just let me know if there's specific steps I could take to help catch whatever this is.  Cheers :-)
10:11 -!- deusexbeer [~deusexbee@079-170-137-113-dynamic-pool-adsl.wbt.ru] has joined #c-lightning
10:49 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection]
11:01 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning
12:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
14:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:39 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 252 seconds]
15:00 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:04 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
15:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
15:31 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
16:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds]
16:38 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
19:31 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds]
20:48 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
20:52 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
21:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning []
21:51 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning
23:14 -!- nothingmuch [~user@62.102.148.164] has quit [Ping timeout: 250 seconds]
--- Log closed Sun Jan 06 00:00:13 2019