--- Log opened Wed Feb 27 00:00:01 2019
01:17 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
02:12 < t0mix> lol, I stopped lightningd 90 minutes ago. I wanted to change fees for channels. I'm not able to start it again since then. gossipd seems to run when I do start, but then after 30 seconds it exit (2) and that's it. what the?
02:25 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:38 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
02:47 < t0mix> actually, even connecd and hsmd (badly named daemon software module) are started .. but only for short time. nothing in log.
02:52 -!- rafalcpp_ is now known as rafalcpp
03:02 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
03:03 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
03:14 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
03:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
03:16 < raucao> hi. i just upgraded my server that is hosting c-lighnting from 16.04 to 18.04. after the upgrade it told me to re-compile lightningd due to a sqlite version mismatch
03:16 < raucao> but compiling now fails with this error:
03:17 < raucao> `/usr/bin/ld: tools/headerversions.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIC`
03:17 < raucao> `/usr/bin/ld: final link failed: Nonrepresentable section on output`
03:17 < raucao> anyone knows what this means?
03:25 < t0mix> holy crap.. lightnind just started after 2,5 hours of repeated attempts. how that's even possible? =D
03:32 < t0mix> the only thing is that I started with log-level=debug. is it possible to disable debug without additional restart? =|
03:34 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 258 seconds]
03:37 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
04:04 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 264 seconds]
04:58 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds]
04:59 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
06:12 < molz> t0mix, is this on a rpi?
06:12 < t0mix> yup
06:13 < molz> i've seen issues happening mostly with rpis
06:16 < t0mix> I hope you are not suggesting to drop rpi </3
06:21 < t0mix> I'll throw more power in rpi and build a cluster. but it would help me a lot if I could pin point the issues. it takes time.. a LOT
06:34 < molz> t0mix, im suggesting to kill all rpis
06:34 < t0mix> I guess you don't care much about code
06:34 < molz> t0mix, what does code have to do with using craps?
06:35 < molz> t0mix, i guess you don't care about the health of the network
06:35 < t0mix> tell me more molz. how is health damaged? I really don't know.
06:36 < molz> your node keeps shutting down, if someone happens to route thru your node, they can't
06:38 < t0mix> oh no, my node is not shutting down. I shut it down intentionally. it was down for 2.5 hours today. then a week without downtime. uptime itself is 140 days.
06:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
06:38 < t0mix> and it didn't crash a once actually.. it was always me bringing it down.
06:39 < t0mix> (then having problems starting it.. yeah.. minor detail =D .. but once UP, then UP )
06:39 < t0mix> also my fees were set so high that nobody routed via my node. that was the reason I restarted. to apply lower fees. any other arguments?
06:46 < molz> t0mix, did you close all channels as a favor to your victims?
06:47 < t0mix> no? connection re-estabilished after restart. is that not sufficient?
06:48 < molz> what if someone needs to send a payment during your down time and your node is in their only route? i guess they can close your channel
06:48 < molz> but this is one of thousands of examples rn on ln
06:49 < molz> nodes are unstable, why, because they're run on rpis
06:49 < t0mix> molz, I'm not pretending my server is production ready. I treat it as development.
06:50 < t0mix> I really don't care about other nodes. .. especially in my case where I'm pretty sure nobody suffered.
06:50 < t0mix> I don't have big network estabilished.. also.. why my node should be central point of failure? that doesn't make sense.
06:51 < t0mix> are you some business owner? I'm trying to understand your view.
06:52 < molz> so your node is on testnet? 
06:52 < t0mix> argument to do development on testnet is BS. how am I suppose to solve real routing issues?
06:53 < molz> ah ok so you're using mainnet to do this.. 
06:54 < t0mix> so? did you payment get stuck on lightning recently? it never happened to me.
06:55 < t0mix> I also don't expect all nodes I'm connected to, to stay up. they are free to join/leave. they are problematic, I won't open connection to them. what is the problem?
06:57 < molz> right, if ln will be just for hobbyists, not serious businesses, so be it, can't argue with you there
06:59 < t0mix> not at all, serious business. but you seems to come into conclusion that some central router will be required. which is not how I see it. I don't expect network not being resilient to nodes failures.
07:00 < t0mix> I see forwards my node did.. and I KNOW that I made zero forwards in last week. why wouldn't I feel safe to shut down my node? paranoid?
07:01 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
07:05 < t0mix> also, if work is not my hobby, then I don't do it. I care about my life! =D
07:33 < grubles> t0mix: you could use the PPA
07:33 < grubles> decker's
07:40 < t0mix> grubles, PPA?
07:41 < molz> t0mix, i've never said "some central router will be required" 
07:42 < molz> t0mix, as a matter of fact, the opposite
07:46 < t0mix> molz, okay. rpi for forwarding works just fine. for routing finding it doesn't. it's very stable from what I experienced.
08:05 < grubles> t0mix: yeah it's a repo you can add so you can just `sudo apt install` instead of building from source
08:47 < fiatjaf> suddenly "invoice" commands are taking over 40 seconds to complete here. why?
08:47 < fiatjaf> if I call it with invalid arguments I get the error immediately. other commands seem also to be completing in normal time.
08:48 < fiatjaf> then suddenly it goes back to the normal behavior
09:12 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
14:29 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
14:30 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
14:40 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
14:40 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
14:44 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:10 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:10 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
16:49 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:22 -!- StopAndDecrypt_ [~StopAndDe@69.12.80.90] has joined #c-lightning
17:22 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 245 seconds]
18:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
19:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
19:11 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Remote host closed the connection]
19:12 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
19:47 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
20:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:13 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
20:15 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 255 seconds]
20:42 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
21:01 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
21:12 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
21:12 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
21:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
21:16 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
21:23 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
21:23 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
21:42 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
21:43 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
23:15 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds]
23:24 -!- StopAndDecrypt_ [~StopAndDe@69.12.80.90] has quit [Ping timeout: 244 seconds]
--- Log closed Thu Feb 28 00:00:02 2019