--- Log opened Fri May 03 00:00:01 2019
00:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
00:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
00:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:23 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has joined #c-lightning
02:01 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
02:11 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning
02:59 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
03:01 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:02 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 255 seconds]
03:33 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
03:39 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
03:47 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
04:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning []
04:22 < ironbutt> Hey. Does somebody know what to do when clightning paystatus shows in "local_exclusions" all channels the node has and then can't find the route?
04:28 < molz> ironbutt, hm.. where do you see "local_exclusions" ?
04:39 -!- bitonic-cjp [~bitonic-c@92-111-70-106.static.v4.ziggozakelijk.nl] has quit [Quit: Leaving]
04:41 <@cdecker> ironbutt: that usually means that the channel was attempted for this payment and was excluded because it failed for some reason (wrong fee, wrong CLTV, ...)
04:42 <@cdecker> Are you the one who reported #2611?
04:42 <@cdecker> If yes I'm happy to walk you through the debug steps :-)
04:44 < ironbutt> cdecker: Yes, I am. Sadly, I'm LND user. But I will do everything I can.
04:44 < ironbutt> molz: paystatus
04:45 <@cdecker> Ok, can you confirm that you are trying to send from a c-lightning node (let's call him C) through an lnd node (L) to some target node (T)?
04:45 <@cdecker> And direct payments work correctly?
04:49 < ironbutt> I confirm. Actually C now has several channels (and another LND among them) in various state, i mean some of them have only outbound, some only inbound capacity, none of them work actually . Checking direct payments right now.
04:50 <@cdecker> Next step is to use `getroute` to confirm that c-lightning can actually compute a route from itself to T
04:51 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Quit: Leaving]
04:52 < ironbutt> Direct channel: tried 250896 payment right now. My dashboard estimates remote balance as much as 259775. C says "Could not find a route" 
04:52 < ironbutt> *Direct payment
04:53 <@cdecker> Ok, that would suggest the channel is not active
04:53 < ironbutt> Actually my peer i going to offline meeting with me and has no access to his node, sorry
04:53 <@cdecker> Ah, ok
04:53 < ironbutt> C said all channels are active
04:54 <@cdecker> You can check the status of the peer with `lightning-cli listpeers`, it'll also list channels you have with that peer
04:54 < ironbutt> Output 2 hours ago
04:54 < ironbutt> "num_peers" : 11,
04:54 < ironbutt>    "num_pending_channels" : 0,
04:54 < ironbutt>    "num_active_channels" : 6,
04:54 < ironbutt>    "num_inactive_channels" : 0,
04:54 <@cdecker> Yeah, but what does the `lightnin-cli listpeers [peer-id]` say about whether it is connected or not?
04:55 < ironbutt> I have kind a strange feeling about whole situation like I'm launching LN node like year ago on my RPi
04:55 < ironbutt> cdecker: I can't say anything about it now.
04:56 <@cdecker> Why? Do you not have access to the node atm?
04:56 < ironbutt> i can only say something related to my node LND
04:58 <@cdecker> Hm, that's too bad, since the LND node won't tell us anything helpful in this case (it's just acting as a hop in the route)
04:58 < ironbutt> The channel is active, an update was a day ago
04:59 < ironbutt> okay. I'm glad we can talk here. I'll be back better prepared. Actually I've compiled C client on my laptop already and have ready bitcoins for channel between my LND and my C
05:00 <@cdecker> Ok, I'm curious about what might be causing this
05:01 <@cdecker> My guess is that the gossip is not syncing through the lnd node, or that there is a failure somewhere along the route behind lnd
05:01 <@cdecker> Logs would be really nice if you can pipe them into a file and upload to pastebin
05:01 < ironbutt> I guess It could be very serious problem with different appearances
05:04 <@cdecker> Nah, we are testing for these things on a regular basis, lnd and c-lightning are compatible, we just have some quirks from time to time
05:04 < ironbutt> https://pasteboard.co/IcYYdNS.png my node has very few routing events, sudden drop in april despite 0 fees
05:06 < ironbutt> I'm not 100% sure. But I tested it with several peers I'm in contact
05:06 <@cdecker> That drop can be caused by your peer selection not being attractive for nodes to route through :-)
05:07 < ironbutt> I know. But before I noted good response fee level / routed volume. And in aprill volume vanished
05:08 < ironbutt> So I started to intensively communicate and even test situation by myself.
05:09 < ironbutt> At the github is example with WalletOfSatoshis. I know people complain about custodial wallets but they are damn handy in such situations
05:10 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
05:12 <@cdecker> Yeah, they are really useful for some use-cases, and I personally don't have anything against them :-)
05:14 <@cdecker> Anyway, if you could share the logs of the c-lightning node while you are trying to send a payment, the `listpeers` output, and `getroute [destination-id] 1 1` via a paste (and share the URL of the paste maybe in a DM), I'm sure we can get to the bottom of what is causing the issue
05:35 < molz> I just did some testing between my c-lightning node which has a direct channel with an eclair desktop node and a lnd node, no problem sending and receiving between the 3. Eclair node has a channel with endurance node, my c-lightning node does not but it can pay starblocks. My lnd node has a channel with another lnd node that clightning node does not, but clightning can pay to that second lnd node 
05:37 < molz> usually i've seen issues with "no route" is either one of the node in the middle is inactive or doesn't have enough liquidity to route, and most people aren't aware of the 1 percent reserve rule 
05:42 <@cdecker> Yep, that's my experience as well. The "no route" error really doesn't give all that much information sadly
05:42 < ironbutt> molz: thank you. I also using Eclair for testing purposes. My node is very well connected and I haven't seen anything strange before my peer didn't start its own node and startet to bootstrap it. Then I recognized problems
05:48 < molz> ironbutt, 'very well connected' are just buzz words to me, we have to look at each case of each payment
05:49 < molz> it's been a huge misconception that if you pour in thousands of dollars on ln and open a ton of channels then you're well connected, not so
05:51 < molz> this is why i banned LNBIG's ips, they're just spams mostly
05:52 < ironbutt> I know about it. But saying 'well connected' i mean constant testing sending small payments to every service I find interesting. As soon as having a bunch of various wallets and transacting between them. 
06:04 <@cdecker> You could automate that process by using our `probe` plugin. It reports success of routes to random nodes in the network (pretty much a worst case scenario for routing in lightning) without actually sending any funds :-)
06:21 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
08:16 -!- ulrichard [~richi@dzcpe6300borminfo01-e0.static-hfc.datazug.ch] has quit [Remote host closed the connection]
08:32 < m-schmoock> cdecker: I added the PR for listing payments received via sendinvocieless plugin: https://github.com/lightningd/plugins/pull/14
10:11 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Quit: bbl]
10:47 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning
10:59 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #c-lightning
11:00 < drexl> hi, does c-lightning work with a pruned node?
11:01 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
11:02 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
11:07 <@cdecker> It mostly does with some caveats
11:08 <@cdecker> The main issue is that you shouldn't let c-lightning lag too much behind otherwise it can't sync blocks anymore since bitcoind may have pruned them already
11:12 < drexl> cool ty
11:12 < drexl> also does nanotip work with mainnet?
11:41 <@cdecker> Yep, it absolutely does (it doesn't have network related code at all) :-)
12:23 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
13:14 -!- roasbeef [~root@104.131.26.124] has joined #c-lightning
13:45 -!- Kostenko [~Kostenko@176.78.154.81] has joined #c-lightning
14:39 -!- Netsplit *.net <-> *.split quits: RonNa, @niftynei
14:43 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 255 seconds]
14:43 -!- Netsplit *.net <-> *.split quits: jonasschnelli, kanzure, ungenannter
14:56 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
15:07 -!- Netsplit over, joins: RonNa
15:07 -!- Netsplit over, joins: niftynei
15:07 -!- mode/#c-lightning [+o niftynei] by ChanServ
15:08 -!- Netsplit over, joins: kanzure
15:11 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 255 seconds]
15:17 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
15:21 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:32 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 250 seconds]
18:28 -!- RonNa [~quassel@220-133-223-206.HINET-IP.hinet.net] has quit [Ping timeout: 255 seconds]
18:33 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Remote host closed the connection]
19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection]
20:08 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
20:11 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds]
20:35 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
20:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 255 seconds]
21:10 -!- takinbo [sid19838@gateway/web/irccloud.com/x-lwfcknxyojbcakco] has quit [Ping timeout: 250 seconds]
21:10 -!- takinbo [sid19838@gateway/web/irccloud.com/x-loslwovxbcqjoauq] has joined #c-lightning
21:14 -!- justan0theruser is now known as justanotheruser
21:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
22:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
--- Log closed Sat May 04 00:00:02 2019