--- Log opened Wed Feb 13 00:00:49 2019 01:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 01:09 < m-schmoock> ctrlbreak: wb, im currently doing the opposite, trying to get out of the regular job and doing real things :D 01:09 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning 01:12 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 01:13 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 01:19 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning 01:37 < bitonic-cjp> I am confused about the wire format of the JSON interfaces. The plugin interface seems to use double-newline separators; the RPC code is ambiguous. 02:01 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:10 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 02:41 -!- deusexbeer [~deusexbee@093-092-176-118-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 04:52 < m-schmoock> cdecker: does the channel specific fees apply for both half channel direction? Or is only outgoing direction relevant in this case? 04:53 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 05:12 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 05:18 < t0mix> here, I fixed the crashing clighning ='D executed by cron every 5 minutes "ps -e|grep lightningd > /dev/null; if [ "$?" = "1" ]; then /usr/local/bin/lightningd; fi" 05:28 < m-schmoock> lol'ed 05:29 < m-schmoock> The configure script raises a core dump on both of my development machines: checking for passing pointers via makecontext()... sh: line 1: 8792 Segmentation fault (core dumped) ./configurator.out 2>&1 05:29 < m-schmoock> nois this known 05:29 < m-schmoock> *is 06:18 <@cdecker> ctrlbreak: that is a somewhat annoying pattern we fixed recently: when one funding fails for some reason (fees for example) we may end up chaining more fundings on that by using its change output, hence none of the fundings is valid. 06:19 <@cdecker> Sometimes it helps to grab the TXs from the sqlite3 database, but it's often not worth it if the other end already forgot that channel you'll end up having to close since they wont resume the channel 06:21 <@cdecker> `dev-rescan-outputs` and `def-forget-channel` are your friends in this case. But really make sure the transactions can't confirm. I usually consolidate all my outputs by doing a `lightning-cli dev-rescan-outputs; lightning-cli withdraw $(lightning-cli newaddr | jq .address) all` :-) 06:22 <@cdecker> t0mix: can you share the crash backtrace? 06:23 <@cdecker> bitonic-cjp: the RPC python code needs to support older versions as well, which is why we aren't fully relying on \n\n just yet 06:23 <@cdecker> m-schmoock: only the forwarding side leverages fees, so only the outgoing side's fees apply 06:24 <@cdecker> m-schmoock: re crash in configure can you report that on the tracker? That seems new to me :-) 06:25 < bitonic-cjp> I made my own implementation strict in what it sends (always \n\n) and relaxed in what it accepts (I think no separator is currently required, but any whitespace is accepted). 06:28 < m-schmoock> cdecker: by tracker you mean to raise a github issue? 06:29 < bitonic-cjp> Oh, and if you're interested: I may have found a potential security issue. Not sure yet if it's a big deal. 06:29 < m-schmoock> bitonic-cjp: /msg cdecker, not public 06:29 < m-schmoock> maybe it is a big deal :> 06:31 < bitonic-cjp> I'll do a PGP mail to cdecker. 06:42 < t0mix> cdecker, here is the log file (if that's what you mean) https://www.dropbox.com/s/rsczf7bvgtdv32s/lightning.log.2.gz?dl=0 06:43 < t0mix> it ends with lightningd crash 06:51 < m-schmoock> cdecker: https://github.com/ElementsProject/lightning/issues/2351 06:55 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 07:05 <@cdecker> Thanks everybody :+1: 07:08 <@cdecker> t0mix: what chain is that? It has > 17301655 blocks (can't be bitcoin or testnet) and it seems to have loads of channels which is causing the crash afaik 07:12 <@cdecker> It might also be related to #2268, but that'd be surprising 07:29 < t0mix> hmm.. it is mainnet 07:34 < t0mix> I have 19 channels listed in listpeers. https://pastebin.com/9j0M0kbz 07:35 < t0mix> can you tell me more about #2268? 07:38 < t0mix> block 17303999 is indeed very strange =| 07:57 -!- Amperture [~amp@24.136.5.183] has quit [Read error: Connection reset by peer] 08:24 <@cdecker> So #2268 is a fix where peers where asking for channels from 0...UINT64_MAX, which caused us to split the range over and over again for the ranges > blockheight 08:24 <@cdecker> So we'd be creating a lot of useless splits 08:25 <@cdecker> Can you maybe start your node with gdb to see where it fails? 08:26 <@cdecker> If you start with --dev-debugger=gossipd you get instructions on how to attach gdb 08:49 < t0mix> "lightningd --dev-debugger=gossipd" ? seems like unrecognized option 09:00 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving] 09:10 < t0mix> seems I need to rebuild c-lightning with dev option 09:16 < t0mix> ..recompiling 10:09 <@cdecker> Oh yeah, sorry forgot to mention that 10:12 < t0mix> hmm.. now when I run I don't get error, but it doesn't seems to start. lightningd starts correctly, but with mentioned options: 10:12 < t0mix> lightning_hsmd(28989): Status closed, but waitpid 28989 says No child processe 10:15 < t0mix> I mean, lightningd start correctly without --dev-debugger. with that, I get the error above =/ 10:16 < t0mix> while "lightningd --dev-debugger=gossipd" finish successfully (zero is returned) 10:19 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 10:33 <@cdecker> Oh I see, the debugger now starts a new terminal by itself 10:33 <@cdecker> You need to `echo 1 | sudo tee /proc/sys/kernel/yama/ptrace_scope` so it can attach to the running process 10:35 <@cdecker> Sorry, that should `echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope` 10:35 <@cdecker> Then you can start with dev-debugger and a new shell should pop up 10:35 <@cdecker> In that shell you need to type `continue` a couple of times and it'll continue running gossipd 10:36 < t0mix> shall I run in screen? 10:38 < t0mix> also /proc/sys/kernel/yama doesn't exist 10:39 < t0mix> and.. thanks for helping cdecker 10:55 <@cdecker> Hm, if you don't have a UI on that machine launching the debugger may be hard (never tried it myself) 10:57 <@cdecker> I think if you set `DEBUG_TERM=screen` you might get a new screen session to which you can then attach using `screen -r` 10:57 -!- spinza [~spin@155.93.246.187] has quit [Ping timeout: 268 seconds] 10:59 <@cdecker> Doesn't seem to work for me, but the logs will print something like this: Running ${DEBUG_TERM:-gnome-terminal --} gdb -ex 'attach 10773' /home/cdecker/dev/lightning/lightningd/lightning_gossipd >/dev/null & 10:59 <@cdecker> You can use that `gdb -ex 'attach 10773' /path/to/lightning_gossipd` command to attach to the process 11:01 <@cdecker> That's interesting `DEBUG_TERM='tmux new-window' lightningd/lightningd --dev-debugger=gossipd` works like a charm for me in tmux :-) 11:02 < t0mix> I do have tmux, too :) 11:03 <@cdecker> Nice, so DEBUG_TERM="tmux split-window" is great 11:04 <@cdecker> That'll just split the window and attach the debugger in the new pane 11:04 <@cdecker> That just made it into my dotfiles ;-) 11:07 < t0mix> cool, I feel like adding some value to you =D 11:14 < t0mix> but I still don't know how to run it 11:15 < t0mix> running `DEBUG_TERM='tmux new-window' lightningd --dev-debugger=gossipd` in tmux does the very same "Status closed, but waitpid 30816 says No child processes" 11:25 <@cdecker> You definitely are adding value ^^ 11:25 <@cdecker> Hm, for me that pops up a new pane and attaches the debugger 11:42 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 11:45 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 11:46 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 11:59 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 12:43 < t0mix> I might try to re-compile.. I did get some error which I ignored during "make install" :) 12:51 < m-schmoock> cdecker: how can I debug a sub-daemon that constantly crashes like this?: 2019-02-13T20:49:34.308Z lightningd(16973): 02004c625d622245606a1ea2c1c69cfb4516b703b47945a3647713c05fe4aaeb1c chan #213: Peer transient failure in CHANNELD_NORMAL: lightning_channeld: Owning subdaemon lightning_channeld died (62208) 12:51 < molz> t0mix, git fetch; git checkout origin/master; ./configure --enable-developer; make clean; make && make install 12:52 < t0mix> molz, yup 12:56 < t0mix> actually, I skipped "make clean". but that should not be a problem 12:58 < m-schmoock> cdecker: got, nvm 12:58 < m-schmoock> *got it 13:27 < t0mix> 2nd compile without error, debug is running! feels like (∩`-´)⊃━☆゚.*・。゚m a g i c 13:28 < t0mix> (not that I know what to do now) 14:03 -!- 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 16:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 16:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:19 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 17:27 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 17:30 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 19:12 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 19:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 19:50 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 19:51 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 19:59 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 258 seconds] 20:06 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 20:22 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 258 seconds] 20:24 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 20:45 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 20:48 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 21:10 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Ping timeout: 250 seconds] 21:12 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning 21:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds] 21:28 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:29 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 21:37 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning --- Log closed Thu Feb 14 00:00:49 2019