--- Day changed Fri Feb 23 2018 00:22 -!- aj [aj@cerulean.erisian.com.au] has joined #c-lightning 00:22 -!- meshcollider [meshcollid@gateway/shell/elitebnc/x-tzlqqngeabzyegyn] has joined #c-lightning 00:22 -!- shesek [~shesek@bzq-84-110-53-17.cablep.bezeqint.net] has joined #c-lightning 00:22 -!- shesek [~shesek@bzq-84-110-53-17.cablep.bezeqint.net] has quit [Changing host] 00:22 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 00:33 -!- zib [zib@slick.hkt0.keff.org] has joined #c-lightning 00:33 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-zxvacmrtaxjnnhbt] has joined #c-lightning 00:36 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 00:46 -!- almkglor [9258463b@gateway/web/freenode/ip.146.88.70.59] has quit [Ping timeout: 260 seconds] 01:07 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 01:08 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning 01:12 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 256 seconds] 01:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:45 -!- mode/#c-lightning [+o rusty] by ChanServ 01:46 <@rusty> grafcaps, rotarydialer: if they closed channel, your funds shouldbe available to spend immediately. 01:47 <@rusty> (oops, that was a v. old msg I was reading!) 01:48 -!- 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 01:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning [] 01:48 < p3tr> i'm finding it more and more difficult to open a channel with someone - i'm getting several different errors, like: 01:48 < p3tr> lightning-cli: Malformed response '2018-02-23T09:38:19.941Z lightningd(17227): 02081fc55f6fef6ce216f1e0eb3d717177f9f2fab2281fee1bb14556a742069e78 chan #2 01:49 < p3tr> : Opening channel: received ERROR channel 4105af785b9bd4bd6b9f38087342b19a1a70ad1b95c6ce8dded2167ebf1ed099: Unacceptable channel constraints: minimum HTL 01:49 < p3tr> C value is too large: 0 01:49 < p3tr> or this: 01:49 < p3tr> lightning-cli: Malformed response '2018-02-23T09:32:37.406Z lightningd(17227): 0231eee2441073c86d38f6085aedaf2bb7ad3d43af4c0e2669c1edd1a7d566ce31 chan #1 01:49 < p3tr> : Opening channel: sent ERROR to_self_delay 1201 larger than 432 01:49 < p3tr> Is that perhaps because people are running older revisions of c-lightning ? i'm updating almost every day 01:51 < p3tr> note that i have not changed any settings regarding fees, htlcs or self_delay - i'm using the defaults provided 01:57 < lxer> Same. 02:03 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 02:09 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 268 seconds] 02:32 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 02:37 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 256 seconds] 03:03 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 03:43 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-zxvacmrtaxjnnhbt] has quit [Quit: Connection closed for inactivity] 03:44 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 03:48 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 240 seconds] 04:18 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 04:20 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #c-lightning 04:22 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 260 seconds] 04:26 -!- bloxton [76d041ae@gateway/web/freenode/ip.118.208.65.174] has quit [Ping timeout: 260 seconds] 04:46 < jperau> 5.5hrs and counting - up to "adding block 723xxx". Is this normal? 04:49 < rompert> p3tr: lxer: lucky you, i'm getting bored only getting `sendrawtx exit 25, gave error code: -25?error message:?Missing inputs?` when trying to open a channel. 04:54 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 04:55 < lxer> I always get CHANNELD_AWAITING_LOCKIN, and it just stays like that until I delete the wallet 04:56 < p3tr> i would really like to know if this is due to the fact that people run old nodes or some issues in the latest revisions though 04:57 < rompert> oh cool. at least yesterday i had two confirmed tx:s to fund from. today i fund from a tx that's not even in mempool 04:57 < p3tr> rompert: are you on testnet? i could try opening a channel with you 04:57 < rompert> and the others are gone 04:57 < p3tr> or you with me if you want 04:57 < rompert> nah. testnet is too riskfree, i'm on mainnet 04:57 < p3tr> brave 04:58 < bitonic-cjp> listchannels gives me empty output again. Does this have anything to do with the fact that it's still busy adding blocks? Right now, my nodes are spending the entire day doing that, and still aren't finished at the end of the day. 04:58 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 248 seconds] 04:58 < p3tr> are you connected to any other node? i think my listchannels was empty until i connected to someone else and waited for a while (so they gossiped about the network topology) 04:59 < p3tr> lxer: and you are on testnet? 04:59 < bitonic-cjp> I have four nodes that are connected to each other. 04:59 < p3tr> oh, weird 04:59 < bitonic-cjp> listpeers gives 'connected': True 05:01 < bitonic-cjp> iirc, cdecker told me earlier that something is still missing in c-lightning, and it isn't an issue if you connect to the global network: on the global network, there is so much activity that you'll automatically get synced. 05:03 < bitonic-cjp> I could connect to one of your testnet nodes, see if that makes a difference. Currently I don't have a globally routable IP:port though, so I can only try outgoing connections. 05:05 < p3tr> 02ff725de0dca7565b1a2ed6c60790d88e693d6fd7192e4104bc6ada4b32515e00@62.75.159.158:9735 05:05 < p3tr> bitonic-cjp: ^ feel free to try connecting and opening a channel 05:07 < bitonic-cjp> connected 05:07 < bitonic-cjp> state: GOSSIPING 05:08 < bitonic-cjp> FYI: my ID is 03f3b0a454583f712318a0c9023423b3093ce534dff288907107b3ec337ccda10f 05:09 < p3tr> yes i can see you \o/ 05:10 < bitonic-cjp> I wonder if it ever gets out of GOSSIPING. I'll keep it running for a while. 05:11 < p3tr> um, what state would it be in then? 05:12 < p3tr> i thought gossiping is the "normal" state 05:12 < bitonic-cjp> Wait, listchannels suddenly gives me lots of output. Well, that part succeeded at least. 05:13 < p3tr> good news 05:13 < p3tr> maybe try opening a channel with me? 05:13 < bitonic-cjp> Sure. Will do. 05:16 < bitonic-cjp> CHANNELD_AWAITING_LOCKIN 05:17 < p3tr> now we just have to wait a bit 05:17 < p3tr> but that went surprisingly smooth 05:18 < p3tr> im still trying to find a node that i can open a channel with 05:18 < p3tr> it seems that the issue really might be the fact that people are running some quite old revisions 05:19 < bitonic-cjp> I try to sync with the master branch a couple of times per week, but I'm working full-time on Lightning now. 05:19 < bitonic-cjp> Thanks to you I can continue testing+developing my GUI, https://github.com/bitonic-cjp/fireworks 05:19 < lxer> I have recent versions, but it just stays in CHANNELD_AWAITING_LOCKIN for 30 hours now. 05:20 < bitonic-cjp> The last testnet block is a couple of minutes ago, so that shouldn't be the problem. 05:21 < bitonic-cjp> Can you give me the funding_txid of the failing channel? 05:21 < p3tr> bitonic-cjp: glad to help, if you ever need something just hit me up with a message here on irc i will get to it eventually 05:23 < bitonic-cjp> I don't know if it's appropriate to reward you with some testnet coins, but it'll have to wait anyway, due to CHANNELD_AWAITING_LOCKIN. 05:24 < p3tr> :) 05:28 < bitonic-cjp> Hmm, on payment between my own nodes, it still says it can't find a route. I'll have to dig through the listchannels outputs to see who knows what. 05:33 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 05:37 < bitonic-cjp> Our channel is still CHANNELD_AWAITING_LOCKIN, but it already has more than 6 confs: 05:37 < bitonic-cjp> https://www.blocktrail.com/tBTC/tx/64c13b639391ae273915a2e902624f7c2a2d9ddbed046320a540a9bf2e72aea8 05:37 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Ping timeout: 240 seconds] 05:38 < bitonic-cjp> My guess is that's because my (Lightning) node is still catching up with the block chain, but I'm not sure. 05:43 < bitonic-cjp> BTW my own nodes don't appear yet in their own or each others listchannels output, but the listchannels output is still growing, so I'll wait and see where it ends. 05:45 < p3tr> meanwhile one of my channels managed to get to NORMAL state 05:45 < p3tr> i opened it at about the same time as you did with me 05:47 < bitonic-cjp> How does our channel look in your node? Is it still CHANNELD_AWAITING_LOCKIN? 05:47 < p3tr> yes 05:48 < bitonic-cjp> Your recently-turned-NORMAL channel, how many confirmations does it have? 05:48 < p3tr> just looking at it - only 4! 05:48 < p3tr> https://www.blocktrail.com/tBTC/tx/04f5b7e0baa2dfa25d47ad26fd8cc3068946d42b0f5bce2efc27be726b88c0d6 05:49 < bitonic-cjp> Maybe both peers need to be synced before the state can advance? How long has your node been up? 05:49 < p3tr> you know what is strange? the amount shown - 0.8 btc is quite a lot, i thought max for a channel is 0.1677 05:50 < bitonic-cjp> 'msatoshi_total': 10000000000 05:50 < p3tr> ah but maybe that is the input value 05:51 < p3tr> it probably does not mean that all that is in the channel 05:51 < bitonic-cjp> Yes. The channel capacity is 0.1 tBTC. 05:51 < p3tr> since for my channel it shows 0.08 tbc but capacity is only 0.01 tbtc 05:51 < p3tr> ok makes sense 05:52 < p3tr> and my node is running since yesterday 05:56 < bitonic-cjp> Me: "adding block 646305" while we're at 1284674. I'm roughly halfway, and it's been running for about half a day now. 05:57 < p3tr> that is very strange... i think my LN node synced almost instantly, or at least i dont even remember seeing such messages 06:03 < bitonic-cjp> It used to be like that for me as well, but for the last week or so it's been like this. 06:07 < p3tr> and yes i believe it will go to NORMAL after your node synchronizes, we will se though 06:16 < lxer> true, it needs to complete once 06:37 < mlz> p3tr, i just opened a channel with your node, "id" : "02d0a6dc18a9cad748bc44b6a4f7cec2b4f558b82cee83e665b02d0518cc7d671e" 06:45 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 06:48 < p3tr> mlz: cool! 06:48 < p3tr> yes i can see it 06:57 < mlz> very strange that lnd nodes still can't open channels with c-lightning nodes 06:57 < mlz> i tried to open a channel with your node from an lnd node 3 times and got this same error: 06:57 < mlz> ~$ lncli openchannel 02ff725de0dca7565b1a2ed6c60790d88e693d6fd7192e4104bc6ada4b32515e00 1000000 06:57 < mlz> [lncli] rpc error: code = Unknown desc = peer disconnected 06:58 < mlz> at first your node disappeared from 'listpeers' but then i reconnected, and lnd has this flag '--perm' so i used that and your node ID is still in my 'listpeers' but still can't open a channel with 07:05 < lxer> bitonic-cjp: did it ever get out of status CHANNELD_AWAITING_LOCKIN ? 07:06 < bitonic-cjp> let me check 07:07 < bitonic-cjp> Nope, still CHANNELD_AWAITING_LOCKIN 07:07 < bitonic-cjp> Adding block 768368 07:07 < lxer> https://github.com/ElementsProject/lightning/issues/1063 07:08 < lxer> cdecker: ^^ 07:11 < bitonic-cjp> I have the feeling that, in this case, I have the "faulty" node, since it's still catching up with the block chain. 07:12 < lxer> I have the same, with 2 synced nodes. 07:13 < bitonic-cjp> My log contains chan #2: Got funding_locked 07:13 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 07:15 < bitonic-cjp> Based on what I read in the issue, I think it means my peer told me the funds are locked, but I haven't said the same to my peer yet. So my node is the slow one. 07:29 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 07:31 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 07:35 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has joined #c-lightning 07:51 -!- lxer [~lx@x4db3bc35.dyn.telefonica.de] has joined #c-lightning 08:25 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds] 08:54 -!- grafcaps [~haroldbr@50.90.26.145] has joined #c-lightning 09:02 -githubby:#c-lightning- [lightning] cdecker closed pull request #1076: Billboard (master...billboard) https://git.io/vA2a7 09:14 -!- grafcaps [~haroldbr@50.90.26.145] has quit [Ping timeout: 248 seconds] 09:17 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 276 seconds] 09:20 -!- grafcaps [~haroldbr@50.90.26.145] has joined #c-lightning 09:21 -!- lxer [~lx@x4db3bc35.dyn.telefonica.de] has quit [Ping timeout: 248 seconds] 09:31 -!- grafcaps [~haroldbr@50.90.26.145] has quit [Ping timeout: 268 seconds] 09:44 < rotarydialer> If I open a channel, and I want to add more to it with an add'l transaction, is that possible? 09:48 < rotarydialer> Want to re-try purchase from the store... how to choose a node to open channel with? The last 2 times I tried things didn't work out. 09:51 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has joined #c-lightning 09:58 -githubby:#c-lightning- [lightning] cdecker opened pull request #1081: wallet: Fix an off by one error in dev-listaddrs (master...off-by-one-addr) https://git.io/vAa6m 10:10 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vAaio 10:10 -githubby:#c-lightning- lightning/master ae6b901 ZmnSCPxj, ZmnSCPxj jxPCSmnZ: README: add link to our shiny new mailinglist 10:10 -!- amp__ [~amp@24.136.5.183] has joined #c-lightning 10:14 -!- Amperture [~amp@24.136.5.183] has quit [Ping timeout: 265 seconds] 10:46 -!- cncr04s_ [~cncr04s@afxr.net] has joined #c-lightning 11:02 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 11:11 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving] 11:17 -!- jperau [~jason@re.permietech.com.au] has quit [Ping timeout: 260 seconds] 11:32 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has joined #c-lightning 12:13 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has quit [Ping timeout: 260 seconds] 12:27 -!- cncr04s_ [~cncr04s@afxr.net] has quit [Quit: See you real soon!] 12:30 -!- CubicEarths [~cubiceart@50-0-95-188.dsl.dynamic.fusionbroadband.com] has quit [Remote host closed the connection] 12:31 -!- cncr04s [~cncr04s@unaffiliated/cncr04s] has joined #c-lightning 13:02 -!- csvihta [~vpdxmce@179.176.225.125.dynamic.adsl.gvt.net.br] has joined #c-lightning 13:02 < csvihta> _ _ _ _ _ _ 13:02 < csvihta> _ _ _ _ _ _ 13:02 < csvihta> _| || |_ _| || |_| | | 13:02 < csvihta> _| || |_ _| || |_| | | 13:02 < csvihta> |_ __ _|_ __ _| | | __ _ _ __ ___ __ _ ___ 13:02 < csvihta> |_ __ _|_ __ _| | | __ _ _ __ ___ __ _ ___ 13:02 < csvihta> _| || |_ _| || |_| | |/ _` | '_ ` _ \ / _` / __| 13:02 < csvihta> _| || |_ _| || |_| | |/ _` | '_ ` _ \ / _` / __| 13:02 < csvihta> |_ __ _|_ __ _| | | (_| | | | | | | (_| \__ \ 13:02 < csvihta> |_ __ _|_ __ _| | | (_| | | | | | | (_| \__ \ 13:03 < csvihta> |_||_| |_||_| |_|_|\__,_|_| |_| |_|\__,_|___/ 13:03 < csvihta> |_||_| |_||_| |_|_|\__,_|_| |_| |_|\__,_|___/ 13:03 < csvihta> c n c r 0 4 s g r a f c a p s a m p _ _ l x e r d o u g l a s _ _ e b x z i b s h e s e k m e s h c o l l i d e r a j j u s t a n o t h e r u s e r w i n d s o k t w e a k s c o n t r a p u m p k i n s i m l a y h s m i t h s j o n a s s c h n e l l i g r u b l e s p r o v o o s t e n a t o r b o o y a h k a n z u r e d l a n d r e n l o r d c r y p t a p u s r o t a r y d i a l 13:03 < csvihta> cncr04s grafcaps amp__ lxer douglas__ ebx zib shesek meshcollider aj justanotheruser windsok tweaks contrapumpkin simlay hsmiths jonasschnelli grubles provoostenator booyah kanzure dland renlord cryptapus rotarydialer Mark____ aproc cdecker buZz asoltys_ ctrlbreak Bunnyh graphite rodarmor rompert mlz lio17 devachandra takinbo ianthius udiWertheimer berndj arowser danielh_ shenglong mdrollette pigeons fizzwont p3tr cluelesspers 13:03 -!- csvihta [~vpdxmce@179.176.225.125.dynamic.adsl.gvt.net.br] has quit [Client Quit] 13:04 < rotarydialer> Mind.... Blown. 13:06 < buZz> yes thankyou 13:07 < grubles> lol wut 13:07 < grubles> what does it say? 13:28 < buZz> no clue :P 13:28 < buZz> ooooo 13:28 < buZz> doesnt it say #anus 13:28 < buZz> ? 13:29 < buZz> or is that wishfull thinking :D 13:32 -!- hop3y [1000@valtio.org] has joined #c-lightning 13:49 < grubles> ohh that's a # in the front 13:49 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vAVUZ 13:49 -githubby:#c-lightning- lightning/master 73fab9e arowser: move library path to LDLIBS 13:53 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #1081: wallet: Fix an off by one error in dev-listaddrs (master...off-by-one-addr) https://git.io/vAa6m 13:58 < rotarydialer> Any tips for when this happens: "failed: WIRE_FEE_INSUFFICIENT (reply from remote)" 13:58 < rotarydialer> ? 14:06 -!- dongcarl [~dongcarl@2601:645:8201:a6f8:ec4:7aff:fee5:3ab0] has joined #c-lightning 14:07 < dongcarl> Any way to add funds to a channel that's CHANNELD_AWAITING_LOCKIN? 14:09 < grubles> i don't believe so 14:10 < grubles> maybe if you open another channel and send some to yoursel? 14:10 < grubles> yourself, even 14:10 < grubles> (after that one is open, i mean) 14:11 < dongcarl> Is there a way to add funds to a channel that's CHANNELD_NORMAL then? 14:12 < grubles> afaik the only way currently is to have another channel open and send some to yourself 14:13 < dongcarl> grubles: So... I'd do ./cli/lightning-cli fundchannel ? 14:14 < grubles> no the amt would be how much you want to dedicate to the channel, and then some amount would need to stay in the channel for the commit fee 14:15 < grubles> or reserve fee i think it's called? 14:15 < grubles> you could maybe find someone and pay them to top you up 14:20 -githubby:#c-lightning- [lightning] cdecker opened pull request #1082: contrib: Add flake8 and pytest-rerunfailures to builder image (master...flake8-builders) https://git.io/vAVIt 14:25 < rotarydialer> How do you increase the wire fee? Getting this error when trying to pay... "message" : "failed: WIRE_FEE_INSUFFICIENT (reply from remote)" 14:25 -!- CubicEarths [~cubiceart@2600:1010:b012:1dab:5585:3e29:2d3a:603c] has joined #c-lightning 14:48 -!- booyah [~bb@193.25.1.157] has quit [Quit: Konversation terminated!] 14:49 -githubby:#c-lightning- [lightning] ZmnSCPxj deleted ZmnSCPxj-patch-1 at 2cc1be3: https://git.io/vAVt4 14:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:56 -!- CubicEarths [~cubiceart@2600:1010:b012:1dab:5585:3e29:2d3a:603c] has quit [Remote host closed the connection] 15:04 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-jfqtlsfqbpqnphmp] has joined #c-lightning 15:07 -!- CubicEarths [~cubiceart@2600:1010:b012:1dab:51ef:e02a:bba1:6810] has joined #c-lightning 15:11 -!- aproc [~aproc@2605:6000:e503:8300:29b1:9378:3cff:759a] has quit [Ping timeout: 265 seconds] 15:22 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 15:24 -!- aproc [~aproc@2605:6000:e503:8300:6de0:2ae7:f9f1:d1f3] has joined #c-lightning 15:30 -!- CubicEarths [~cubiceart@2600:1010:b012:1dab:51ef:e02a:bba1:6810] has quit [Remote host closed the connection] 15:31 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Ping timeout: 255 seconds] 15:53 -!- amp__ [~amp@24.136.5.183] has quit [Quit: Leaving] 15:53 -!- amp__ [~amp@24.136.5.183] has joined #c-lightning 15:53 -!- amp__ [~amp@24.136.5.183] has quit [Remote host closed the connection] 15:54 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 16:08 -!- lxer [~lx@ip5f5bd657.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds] 16:09 < mlz> how can i make my peers to be permanent with c-lightning? 16:11 < mlz> LND has the flag '--perm' to connect permanently to a peer, does c-lightning have something similar? 16:15 -!- BearShark [~BearShark@155.93.208.90] has joined #c-lightning 16:16 < grubles> hmm not sure 16:19 -!- almkglor [b4be239b@gateway/web/freenode/ip.180.190.35.155] has joined #c-lightning 16:26 -!- jojeyh [~delphi@2602:306:b8b6:b970:41cc:8d6f:4e2b:2830] has joined #c-lightning 16:35 < rusty> BearShark: so you're saying that c-lightning doesn't catch up with blockheight? 16:36 < rusty> It should be polling every 30 seconds... 16:37 < BearShark> yea, its really difficult to explain 16:37 < BearShark> When looking over logs, theres nothing to report 16:38 < BearShark> I was wondering a easy way to solve something like this could be to make something like dev-force-blockheight in order to try sync 16:39 < BearShark> I might want to also throw in the fact that, I'm using multiple daemons for a single bitcoind node, could this play a factor? Although the out-sync times does not correlate with the amount of lightning daemons active, this would disprove that theory 16:43 < rusty> BearShark: Hmm, can I give you a debug build? We had a previous bug where one failure would stop all bitcoind communication, but that was a while ago. 16:44 < BearShark> Yes, although it would be best if I could experiment tomorrow with it. It's really late by me 16:45 < rusty> NP, I'll create a BearShark branch on https://github.com/rustyrussell/lightning for you to run whenever; it'll be spammy on the logs, so use logfile to send it somewhere. 17:01 < BearShark> ok thank you for the help. I'll keep in touch tomorrow 17:07 -!- BearShark [~BearShark@155.93.208.90] has quit [Quit: Leaving] 17:08 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 17:30 -!- zib [zib@slick.hkt0.keff.org] has quit [Ping timeout: 264 seconds] 17:33 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-jfqtlsfqbpqnphmp] has quit [Quit: Connection closed for inactivity] 17:43 < jojeyh> Got the error 2018-02-24T01:42:28.782Z lightningd(31643): Updating database from version 33 to 41 17:43 < jojeyh> db_migrate:SQL logic error or missing database:ALTER TABLE payments ADD COLUMN route_nodes BLOB;:duplicate column name: route_nodes 17:43 < jojeyh> when running 'lightningd --network=testnet --log-level=debug' after fresh git pull 18:12 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-mqjbnafjwdizgrzp] has joined #c-lightning 18:13 -!- meshcollider is now known as mesh_ 18:14 -!- meshcollider_ [uid246294@gateway/web/irccloud.com/x-mqjbnafjwdizgrzp] has quit [Client Quit] 18:14 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fjrznvzqvcuoxzwj] has joined #c-lightning 18:30 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 264 seconds] 18:50 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 18:54 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 240 seconds] 19:04 -!- zib [zib@slick.hkt0.keff.org] has joined #c-lightning 19:47 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 260 seconds] 19:53 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 20:06 < rusty> jojeyh: hmm, got a copy of your db you can send me? Will lose you privacy, but not bitcoins. rusty@rustcorp.com.au 20:07 < rusty> Hmm, my lightningd node was also out to lunch; I stopped bitcoind and it didn't notice. "This time for sure!" I've fixed it for real, now need to write some test for this somehow. 20:56 < jojeyh> rusty, is my lightningd.sqlite3 the db ? 20:57 < rusty> jojeyh: ack! 20:57 < jojeyh> how do i send a file in IRC ? 20:57 < rusty> jojeyh: heh... you email it :) 20:57 < jojeyh> lulz 20:57 < jojeyh> whats ur email 20:58 < rusty> jojeyh: still rusty@rustcorp.com.au :) 20:58 < jojeyh> ok lemme send 20:58 < jojeyh> anything else besides sqlite file ? 20:59 < jojeyh> that you need? 20:59 < rusty> jojeyh: officially, we don't support db upgrade except between major versions (which there aren't any yet!) so it's pretty untested, but I can fix this one I'm sure. 20:59 < jojeyh> ok however i can help 20:59 < rusty> jojeyh: naah, I should be able to load that and get the same fail you did. 20:59 < jojeyh> okee 20:59 < rusty> jojeyh: thanks! 21:03 < jojeyh> rusty, send and bitte 21:03 < jojeyh> rusty, if you need any help feel free to ask 21:03 < jojeyh> rusty, i'd really like to contribute as much as i can but i'm still on my way up the learning curve 21:03 < jojeyh> and eet ees suh steep 21:17 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1084: Better handling bitcoin cli fail (master...better-handling-bitcoin-cli-fail) https://git.io/vAV2c 21:18 < rusty> ^ That should fix BearShark's issue. 21:19 < rusty> Now to get to jojeyh's... my son is happy watching Paw Patrol for the moment, but it's a race :) 21:45 < rusty> jojeyh: any chance you know what the version was you were running before? 21:46 < rusty> It *shouldn't* be possible to upgrade the db without changing the version in the db, but somehow yours got out of sync. Is this inside a VM? 22:04 < jojeyh> rusty, you mean the version of lightningd ? 22:14 < jojeyh> rusty, i'm running it in ubuntu 16.04 xenial 22:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 23:00 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 23:28 -githubby:#c-lightning- [lightning] practicalswift opened pull request #1085: Avoid using undefined variable "name" in print_printwire_array(...). Fix PEP-8 violation. (master...undefined-variable-used-in-print_printwire_array) https://git.io/vAVo3 23:34 -!- CubicEarths [~cubiceart@2601:647:cc00:8899:b84e:e48:2fa5:a689] has joined #c-lightning 23:46 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 252 seconds]