--- Log opened Sat Nov 07 00:00:09 2020 00:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 00:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 00:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 00:38 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 00:39 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has joined #c-lightning 00:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 01:42 -!- reallll is now known as belcher 01:53 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 02:04 -!- kexkey [~kexkey@static-198-54-132-169.cust.tzulo.com] has quit [Ping timeout: 244 seconds] 02:08 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 02:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 02:12 -!- vasild_ is now known as vasild 02:19 < m-schmoock> cdecker: thx :D merged state can still be optimized. we still have remote force closed as 'onchain' (which is better for now). But I was thinking about that it might be possible to detect a remote force close somehow by checking if there has been a faile closing fee negotiation before we see the closing TX... If you have an idea about it I can make a follow up. I think it would be a benefit to 02:19 < m-schmoock> have a good knowledge about if a remote force close was intentional or not 02:32 < m-schmoock> cdecker: Also, can we merge this plugin PR? https://github.com/lightningd/plugins/pull/153 02:32 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 03:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:07 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 256 seconds] 03:08 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:53 < m-schmoock> also I found that lightningd/peer_htlcs.c line 1778 should resolve to reason 'protocol' and not 'local' as this code contains a boltspec comment why we must close here... If you dont mind there will be compatible follow up 03:54 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 03:58 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 04:41 < m-schmoock> In order to identify intentional force close fee negotiation failures, we could check that closingd/closingd.c line 527 was reached before we were force closed... 04:55 < HelloShitty> Hello 04:55 < HelloShitty> Is there a command to check how much inbound capacity we have in our node? 04:56 < m-schmoock> HelloShitty: the summary plugin does a pretty good job on these kind of stuff 04:56 < m-schmoock> https://github.com/lightningd/plugins/tree/master/summary 04:56 < HelloShitty> ok 04:56 < m-schmoock> Though the fiat price lookup is currently failing for external API errors. Still works great 04:57 < m-schmoock> (in case you want to fix this :D 04:57 < m-schmoock> easy thing I guess 05:15 < HelloShitty> I'll first need to learn how to install plugins 05:15 < HelloShitty> never used any 05:15 < HelloShitty> plugins are all python, right? 05:16 < HelloShitty> Oh, I see then can be in any language 05:16 < HelloShitty> and can't we load plugins from within lightning config file? 05:26 < HelloShitty> oh, I see... It loads plugins automatically that are inside plugins directory 05:31 < HelloShitty> But how do we install plugins? 05:36 < HelloShitty> m-schmoock: this is not good, is it: 05:36 < HelloShitty> https://pastebin.com/xZSih2LP 05:37 < HelloShitty> I cloned the plugins repository inside ~/.lightning 05:37 < HelloShitty> and then restarted lightnind 05:37 < HelloShitty> I got that 05:42 < m-schmoock> just missing dependencies I guess 05:42 < m-schmoock> I would not recommend to install any plugin in this repo 05:42 < m-schmoock> but just the ones you want/understand/need 05:43 < m-schmoock> in this case a single link/file to "summary.py" is required in params or ~/.lightning/plugins 05:43 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:45 < HelloShitty> You don't recommend to install any? 05:46 < HelloShitty> What you mean? Summary is from that repo, right? 05:47 < m-schmoock> *all not *any 05:47 < m-schmoock> wrong word :D 05:48 < m-schmoock> I would would pick the plugins I want. From the pastebin looks like you installed all plugins in that repo at once 05:48 < m-schmoock> what I do: 05:48 < m-schmoock> - clone the repo 05:48 < m-schmoock> - mkdir ~/.lightning/plugins 05:49 < m-schmoock> - symlink the plugins you need: either a link to their directory or the .py file (if its just one). directly symlink is better I guess 05:49 < m-schmoock> - restart the node 05:49 < HelloShitty> ok 05:49 < HelloShitty> going to try that 05:50 < HelloShitty> because the file alone is not working 05:50 < HelloShitty> even after restarting the node 05:50 < m-schmoock> logs for that? 05:50 < HelloShitty> Let me try first your suggestion 05:50 < m-schmoock> because the last logs contained all bunch of other errors from other plugins. mainly dependencies that are not isntalled. easy to fix 05:51 < HelloShitty> ok 05:53 < m-schmoock> try doing > pip3 install -r summary/requirements.txt 05:53 < m-schmoock> (in the plugin repo, this installs just the summary deps 05:53 < m-schmoock> (maybe also use the --user switch) 05:54 < m-schmoock> this way: pip3 install --user -r summary/requirements.txt 05:54 < m-schmoock> but this depends a bit how you use cln and how your system works with python deps. normally this should work I guess 05:55 < HelloShitty> I have made the symlink for the summary folder 05:55 < HelloShitty> inside ~/.lightning/plugins 05:55 < m-schmoock> good 05:55 < m-schmoock> so when you do > ls ~/.lightning/plugins/summary/ 05:55 < HelloShitty> now, inside there, pip3 install --user requiremetns.txt, yes ? 05:55 < m-schmoock> then the .py file shows up? 05:55 < m-schmoock> in ~/.lightning/plugins/summary/ yes 05:55 < HelloShitty> yes. among a few others 05:55 < m-schmoock> nice 05:56 < m-schmoock> should be it 05:56 < HelloShitty> Do I still need the pip3 install ? 05:56 < m-schmoock> restart node, try lightning-cli summary 05:56 < m-schmoock> be amazed :D 05:56 < m-schmoock> > Do I still need the pip3 install ? yes 05:56 < HelloShitty> ok 05:56 < m-schmoock> or you mean w/o the "--user" ? then no 05:56 < m-schmoock> only once with "--user" should be fine 05:57 < m-schmoock> you cant do much wring anyway :D 05:57 < m-schmoock> *wrong 05:57 < HelloShitty> I mean if I need to run the pip3 install --user requiremetns.txt from within summary folder 05:57 < m-schmoock> yes, that needs to be done once 05:57 < HelloShitty> ok 05:58 < m-schmoock> (for any plugin that needs special deps) 05:58 < HelloShitty> Could not install packages due to an EnvironmentError: 404 Client Error: Not Found for url: https://pypi.org/simple/requirements-txt/ 05:58 < m-schmoock> in theory you could use pip virtualenv to use deps per plugin or for only cln, but thats overkill I guess 05:58 < m-schmoock> -.- 05:59 < HelloShitty> :s 05:59 < HelloShitty> So, what am I missing ? 05:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 260 seconds] 05:59 < m-schmoock> cat requirements.txt | while read PACKAGE; do pip install --user "$PACKAGE"; done 05:59 < m-schmoock> so you have the others at least 05:59 < HelloShitty> Others what? 06:00 < m-schmoock> the ones that didnt fail 06:00 < HelloShitty> other plugins? 06:00 < HelloShitty> I never installed any 06:00 < m-schmoock> the deps that do not fail 06:00 < HelloShitty> ah ok 06:00 < m-schmoock> pyln-client should be in your env anyway I hope 06:01 < HelloShitty> Requirement already satisfied: pyln-client>=0.7.3 in /usr/local/lib/python3.7/dist-packages (0.8.2) 06:01 < HelloShitty> Requirement already satisfied: requests>=2.0.0 in /home/narayan/.local/lib/python3.7/site-packages (2.18.4) 06:01 < m-schmoock> kk 06:01 < HelloShitty> Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/lib/python3/dist-packages (from requests>=2.0.0) (3.0.4) 06:01 < m-schmoock> try restarting 06:01 < HelloShitty> Requirement already satisfied: urllib3<1.23,>=1.21.1 in /home/narayan/.local/lib/python3.7/site-packages (from requests>=2.0.0) (1.22) 06:01 < HelloShitty> Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests>=2.0.0) (2018.8.24) 06:01 < HelloShitty> Requirement already satisfied: idna<2.7,>=2.5 in /usr/lib/python3/dist-packages (from requests>=2.0.0) (2.6) 06:01 < HelloShitty> Requirement already satisfied: packaging>=14.1 in /home/narayan/.local/lib/python3.7/site-packages (20.1) 06:01 < HelloShitty> Requirement already satisfied: pyparsing>=2.0.2 in /home/narayan/.local/lib/python3.7/site-packages (from packaging>=14.1) (2.4.6) 06:01 < HelloShitty> Requirement already satisfied: six in /usr/lib/python3/dist-packages (from packaging>=14.1) (1.12.0) 06:01 < HelloShitty> They are all satisfied 06:01 < m-schmoock> ... :) 06:01 < HelloShitty> ok 06:02 < m-schmoock> does cln start now with the plugin? 06:02 < HelloShitty> I see this when lightningd resarts: 06:02 < HelloShitty> plugin-bcli: bitcoin-cli initialized and connected to bitcoind. 06:02 < HelloShitty> but can't see anything related to summary 06:02 < HelloShitty> yes 06:02 < HelloShitty> lightningd starts 06:02 < m-schmoock> hm. think the directory symlink didnt work 06:02 < HelloShitty> But do I still need to pass it --plugins=summary parameter when starting lightningd ? 06:02 < m-schmoock> try removing it and place just a symlinik to the .py file 06:03 < m-schmoock> nope, if you use the plugindir and symlinks this makes the --plugin params not needed 06:03 < HelloShitty> ohh wait 06:03 < HelloShitty> it's working 06:03 < m-schmoock> which I find better 06:03 < m-schmoock> ah good :d 06:03 < m-schmoock> does it show you your state and available capacity? 06:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 06:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 06:04 < HelloShitty> yes 06:04 < HelloShitty> nice 06:04 < HelloShitty> thank you m-schmoock 06:05 < m-schmoock> no worries. have fun trying plugin 06:07 < m-schmoock> cool thing, you can easily change and extend stuff w/c c code 06:08 < HelloShitty> yeah 06:08 < HelloShitty> I'll see how the code of this plugin looks like 06:08 < m-schmoock> you can try fixing the fiat price API issue :D 06:09 < m-schmoock> currently it log prints "[PriceThread] Expecting value: line 1 column 1 (char 0)" 06:09 < m-schmoock> which means they turned off/changed the API we query for price 06:09 < m-schmoock> no big deal 06:11 < HelloShitty> I don't see any fiat output 06:12 < m-schmoock> yes, because the API we use to get the price responds in a broken way 06:12 < m-schmoock> hence the log error "[PriceThread] Expecting value: line 1 column 1 (char 0)" 06:12 < HelloShitty> ahh logs 06:12 < m-schmoock> quite sure the respose from line 63 fails: 06:12 < m-schmoock> r = requests.get('https://www.bitstamp.net/api/v2/ticker/BTC{}'.format(plugin.currency)) 06:13 < HelloShitty> But where do you see the error? Is it in lightningd gossip messages? 06:14 < m-schmoock> hm I see its only when you use "EUR" price 06:14 < m-schmoock> curl https://www.bitstamp.net/api/v2/ticker/BTCEUR this gives (sometimes 404) 06:14 < HelloShitty> I'm lost in the conversation 06:14 < m-schmoock> anyway. 06:14 < m-schmoock> if you find the message or see no price, you will know :D 06:15 < HelloShitty> but when you run the command lightning-cli -H summary? 06:15 < m-schmoock> the bistamp API sometimes gives 404 and sometimes not. I assume a broken proxy mirror 06:15 < HelloShitty> Is that supposed to show that error? 06:15 < m-schmoock> nope 06:15 < m-schmoock> but if it shows no $ USD price then you should have the log error in your cln logs 06:17 < HelloShitty> I don't even know where are my lightning node logs 06:17 < HelloShitty> lol 06:17 < HelloShitty> crap 06:18 < m-schmoock> :D 06:18 < HelloShitty> I don't have a specific log file in config 06:18 < HelloShitty> Where should it save the logs by default? 06:18 < m-schmoock> kk. maybe you just have stdout if you dont set it via config or params 06:19 < m-schmoock> I tend to use ~/.lightning/debug.log 06:20 < m-schmoock> gotta go. cu later 06:21 < HelloShitty> thank you m-schmoock 08:21 -!- alko89 [~alko89@unaffiliated/alko89] has quit [Quit: ZNC 1.7.5 - https://znc.in] 08:22 -!- alko89 [~alko89@unaffiliated/alko89] has joined #c-lightning 08:47 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 08:48 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 09:55 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has quit [Ping timeout: 272 seconds] 10:17 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 11:47 -!- kexkey [~kexkey@static-198-54-132-121.cust.tzulo.com] has joined #c-lightning 12:06 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 12:07 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 12:49 -!- jonatack [~jon@213.152.161.30] has quit [Ping timeout: 272 seconds] 13:10 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 13:10 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has joined #c-lightning 13:14 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning 13:19 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 246 seconds] 13:19 -!- jonatack [~jon@134.19.179.27] has joined #c-lightning 14:08 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 14:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 14:12 -!- vasild_ is now known as vasild 14:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 14:22 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 15:02 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:02 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:19 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 15:39 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 15:39 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 15:42 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 15:42 -!- kristapsk___ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 16:19 -!- zmnscpxj__ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 16:27 -!- mrostecki_ [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 16:28 -!- vadorovsky__ [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 16:30 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 17:20 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 17:20 -!- sr_gi [~sr_gi@static-77-88-225-77.ipcom.comunitel.net] has joined #c-lightning 18:10 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 18:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection] 18:42 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 19:19 -!- fiatjaf [~fiatjaf@2804:7f2:2986:a022:ea40:f2ff:fe85:d2dc] has quit [Quit: WeeChat 2.9] 19:23 -!- fiatjaf [~fiatjaf@2804:7f2:2986:a022:ea40:f2ff:fe85:d2dc] has joined #c-lightning 19:53 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 19:55 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 21:02 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 21:11 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 21:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 21:58 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 22:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 22:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning --- Log closed Sun Nov 08 00:00:10 2020