--- Log opened Mon Jan 28 00:00:33 2019 00:37 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning 01:29 -!- tuxx [~tuxx@static.80.154.9.176.clients.your-server.de] has quit [Remote host closed the connection] 02:02 -!- kexkey [~kexkey@199.229.249.116] has quit [Read error: Connection reset by peer] 02:10 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:16 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:56 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 04:48 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 06:21 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 08:20 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving] 10:04 -!- deusexbeer [~deusexbee@080-250-075-168-dynamic-pool-adsl.wbt.ru] has quit [Read error: Connection reset by peer] 10:46 -!- AmikoPay_CJP [~AmikoPay_@a83-163-77-195.adsl.xs4all.nl] has joined #c-lightning 10:51 -!- deusexbeer [~deusexbee@093-092-176-118-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 11:18 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning 12:14 -!- AmikoPay_CJP [~AmikoPay_@a83-163-77-195.adsl.xs4all.nl] has quit [Quit: Leaving] 12:59 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 13:05 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 13:44 < t0mix> any idea why sometimes I get disconnected from peer that I have channel opened with? when I try to run "lightning-cli connect " command takes ages and never finish. but it is interruptable at least. I'm not sure if that's c-lightning problem or network problem. 13:45 < t0mix> strace show it's stuck on some read =| not helping me much 13:48 < t0mix> hm, actually it finished.. "Connection timed out" 14:10 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:16 -!- adam3us [~adam3us@unaffiliated/adam3us] has joined #c-lightning 14:19 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 14:28 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 250 seconds] 15:08 < molz> t0mix, probably that peer is offline 15:08 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has quit [Ping timeout: 246 seconds] 15:09 -!- keymone [~keymone@ip1f10c1a7.dynamic.kabel-deutschland.de] has joined #c-lightning 15:29 < t0mix> it's a big node, https://lightblock.me/lightning-node/0331f80652fb840239df8dc99205792bba2e559a05469915804c08420230e23c7c 15:30 < t0mix> it seems to be up, based on that web. but I still can't connect. 15:39 < molz> eh.. big node or not, their server can be down, and ofc even if their server is toasted, their pubkey and info are still shown on any explorer 15:56 < molz> $ lncli connect 0331f80652fb840239df8dc99205792bba2e559a05469915804c08420230e23c7c@74.108.13.152:9735 15:56 < molz> [lncli] rpc error: code = Unknown desc = dial tcp 74.108.13.152:9735: connect: connection timed out 15:57 < molz> i think it's pierre rochard's node, let me ask him 16:01 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 16:01 < molz> confirmed the node got knocked off 16:03 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 16:15 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 16:19 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection] 16:34 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 16:35 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds] 16:38 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 17:04 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 17:11 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 17:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds] 17:18 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 17:25 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 17:29 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 17:39 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 17:43 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 17:47 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds] 17:49 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 17:53 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 17:54 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 18:01 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 18:03 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 18:19 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds] 18:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 18:26 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 18:31 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 20:23 -!- grubles_ [~grubles@unaffiliated/grubles] has joined #c-lightning 21:04 -!- grubles_ [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection] 21:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 21:35 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 245 seconds] 23:58 < t0mix> thanks molz, I wrote to him. I got that confirmation, too. sure big server can go down, I was just expecting redlights blinking all over the internet =) --- Log closed Tue Jan 29 00:00:34 2019