--- Day changed Thu Aug 16 2018
00:16 < zzzADC7>  ­ ­ ­ ­ ­  http://magaimg.net/img/wqz.jpg  ­  ­ ­ ­ ­ ­ ­ ­ ­ ­ http://magaimg.net/img/wqz.jpg  ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­
00:25 -!- mode/#lnd [+n] by ChanServ     
00:57 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd     
01:11 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-hstnawdnbbsfaunc] has quit [Remote host closed the connection]     
01:12 -!- kkt2MartinPospch [kkt2matrix@gateway/shell/matrix.org/x-gogsybjbcqyugoiv] has quit [Remote host closed the connection]     
01:12 -!- pierce[m] [x43matrixo@gateway/shell/matrix.org/x-xwlcqwdzrxmblpzi] has quit [Remote host closed the connection]     
01:12 -!- cjd[m] [cjdponiesi@gateway/shell/matrix.org/x-hfufafpywgnrrqph] has quit [Read error: Connection reset by peer]     
01:37 -!- reallll [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]     
01:38 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #lnd     
02:32 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd     
02:36 < Talkless> hi. In order to increace funds to a specific channel, I have to disable autopilot, add funds, create channel with wanted satoshis, and enable autopilot again for other channel creation?
02:40 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Remote host closed the connection]     
02:48 <@roasbeef> atm you can't yet increase funds to a specific channel, however you _can_ open another channel to that same node 
02:52 < Talkless> oh, and later I can close the old one?
02:52 <@roasbeef> yeh     
02:52 < Talkless> but still, I should disable autopilot (by restarting) and than do manual stuff, and then re-enable autopilot?
02:53 < Talkless> it would be nice to have lndcli command line to temporary disable it :)
03:12 < Talkless> roasbeef: ack?
03:13 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #lnd     
03:31 -!- Sigyn [sigyn@freenode/utility-bot/sigyn] has quit [Quit: People always have such a hard time believing that robots could do bad things.]     
03:32 -!- Sigyn [sigyn@freenode/utility-bot/sigyn] has joined #lnd     
03:35 < waxwing> roasbeef, PSBT: no, not yet. it's just a serialized tx for now, with sigs provided by the remote counterparty.
03:35 < waxwing> roasbeef, why tweak, to generate a new destination address without interacting with the counterparty
05:23 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #lnd     
06:08 -!- dognip [8067f411@gateway/web/freenode/ip.128.103.244.17] has joined #lnd     
06:10 < dognip> hello. i have a LND node up and running on a raspi using raspibolts stadicus guide. I sent some BTC to it yesterday and it autogenerated some channels for me. Today I used the same address to send more and it is not showing a balance in the wallet OR in any pending channel
06:11 < dognip> it is not listing anythig in unconfirmed or confirmed wallet, despite the tx i sent today having ~10 confirms
06:19 < molz> dognip, you sent some btc to your lnd wallet?
06:21 < dognip> i sent BTC to the address created yesterday via this command: lncli newaddress np2wkh
06:21 < dognip> it worked yesterday, but the wallet balance is not updating today
06:21 < molz> ok, have you checked to make sure you send the second amount to that same address? 
06:22 < dognip> yes, identical address
06:22 < molz> try this to see if it's there: lncli listchaintxns 
06:23 < dognip> no record of todays txn
06:24 < molz> try restart lnd?
06:26 < dognip> whats the proper way to restart lnd
06:27 < dognip> i've been restarting the pi: sudo shutdown -r now
06:31 -!- dognip_ [41700803@gateway/web/freenode/ip.65.112.8.3] has joined #lnd     
06:31 < dognip_> got disconnected, what is proper shutdown of LND
06:31 -!- dognip [8067f411@gateway/web/freenode/ip.128.103.244.17] has quit [Ping timeout: 252 seconds]     
06:32 -!- ocnlightnode [8067f411@gateway/web/freenode/ip.128.103.244.17] has quit [Ping timeout: 252 seconds]     
06:32 < p3tr> lncli stop
06:32 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
06:32 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd     
06:36 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has quit [Ping timeout: 268 seconds]     
07:01 < Talkless> how do I get txid of a pending channel being created? If I creat manually, txid is printed, but in autopilot mode, I do not see txid.  listchaintxns does not show of that unconfirmed tx.
07:08 < tumi> Talkless: not 99% sure, but I believe channel_point part before : is the funding tx
07:08 < Talkless> oh     
07:09 < Talkless> yes tumi your are right, getrawtransaction showed it
07:09 < Talkless> thanks
07:15 < dognip_> my wallet balance is still not showing BTC that i sent there. I have tried restarting LND. should I attempt to restore from seed?
07:16 < dognip_> if so, whats the proper procedure for that?
07:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]     
07:22 < lndbot> <joaoalmeida> is the tx confirmed ?
07:25 < dognip_> i dont think you are talking to me, but if so, yes over 15 confirms
07:26 < molz> dognip_, seed recovery only restors coins in lnd wallet (onchain utxos) and it doesn't restore channels, if you want to do this you need to close all channels, wait for coins to come back to lnd wallet first
07:31 < dognip_> thank you molz
07:31 < dognip_> so closeallchannels
07:31 < dognip_> then whats next step for restore
07:31 < Talkless> dognip_: maybe it's worth considering reporting bug, maybe there's issue on re-using address. (you should never reuse addresses :) )
07:32 < dognip_> ya, i shouldnt have reused
07:32 < Talkless> dognip_: I guess sendcoids will send to your wanted wallet
07:32 < Talkless> back to electrum or whatever you use
07:32 < dognip_> what do you mean?
07:33 < dognip_> try to send over the amount shown in walletbalance?
07:33 < Talkless> after closeallchannels you could try to bring back all coins
07:33 < Talkless> though maybe after closeallcannels youl'see all the balance. 
07:34 < molz> Talkless, maybe he's running a very old commit
07:34 < molz> and btw, from what i've seen so much here, Stadicus's guide isn't for newbies, more for advanced LND users
07:35 < Talkless> dognip_: whats your lnd --version output?
07:35 < dognip_> lnd version 0.4.2-beta commit=7cf5ebe2650b6798182e10be198c7ffc1f1d6e19
07:35 < molz> that's the release version, very outdated
07:36 < molz> im wondering if you upgrade to the latest master, your coin will show up
07:37 < dognip_> id have to build it from the master, correct?
07:38 < Talkless> this commit is of May...
07:38 < Talkless> yeah dognip_, try to reinstall with up to date master
07:39 < dognip_> how do i go about that?
07:39 < Talkless> dognip_: cd _somewhere_/src/github.com/lightningnetwork/lnd/
07:39 < Talkless> git pull
07:40 < Talkless> make && make install
07:40 < Talkless> you have to set GOPATH I believe too, as it was in your tutorial I guess.
07:41 < Talkless> dognip_: if you built it from tag, do git checkout master , git pull, then make...
07:41 < Talkless> dognip_: I hade to use master too due to some problems. 0.4.2 is really buggy.
07:41 < dognip_> i dont know what 'built from tag' means
07:42 < dognip_> i used the release version on first install
07:43 < Talkless> did to perfomed git clone or downlaoded an tar/zip archive?
07:43 < dognip_> dl tar
07:43 < molz> i don't know how you can update from using Stardicus guide either, doesn't he have a guide to update on his github?
07:44 < dognip_> https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_faq.md#how-to-upgrade-lnd-bin-
07:44 < dognip_> he only shows how to update from release
07:44 < dognip_> not a git pull
07:45 < Talkless> " wget https://github.com/lightningnetwork/lnd/releases/download/v0.4.2-beta/lnd-linux-arm-v0.4.2-beta.tar.gz" yeah...
07:45 < molz> Talkless, that is the same version he's using
07:46 < Talkless> yes, I Just copy pateset from tutorial
07:46 < Talkless> I mean, he downloaded an archive, it's not git clone
07:46 < Talkless> and it's pre-built binary
07:49 < Talkless> I dunno dognip_, I guess you should build lnd with it's INSTALL.md manual https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md
07:49 < dognip_> ahh thank you
07:49 < dognip_> admin@raspberrypi:~/download/lndsource/lnd $ make && make install /bin/sh: 1: go: not found /bin/sh: 1: go: not found  Fetching dep. go get -u github.com/golang/dep/cmd/dep make: go: Command not found Makefile:94: recipe for target '/bin/dep' failed make: *** [/bin/dep] Error 127 admin@raspberrypi:~/download/lndsource/lnd $
07:49 < dognip_> that page explains first error
07:50 < Talkless> dognip_: if youre' on Debian, you'll have to install golang-1.10 from backports repository
07:51 < Talkless> dognip_: what's your disro?
07:51 < Talkless> lsb_release -a
07:52 < dognip_> No LSB modules are available. Distributor ID: Raspbian Description:    Raspbian GNU/Linux 9.4 (stretch) Release:        9.4 Codename:       stretch
07:52 < Talkless> ok it's stretch
07:53 < dognip_> so would this be fine?  sudo apt-get install golang-go
07:53 < Talkless> default go is too old, lnd needs 1.10 I believe
07:53 < dognip_> https://github.com/golang/go/wiki/Ubuntu
07:53 < Talkless> it's available in  stretch-backports reposiotry, but I am not sure if it's compatible with your raspberry arm.
07:54 < Talkless> dognip_: lets try to setup bakcports:
07:54 < Talkless> echo "deb http://ftp.debian.org/debian stretch-backports main" | sudo tee /etc/apt/sources.list.d/backports.list
07:55 < Talkless> sudo apt update
07:55 < Talkless> apt policy golang-1.10
07:56 -!- drrty [drrty@gateway/vpn/privateinternetaccess/drrty] has joined #lnd     
07:56 < dognip_> so im not spamming text: https://imgur.com/a/LsId4lf
07:57 < dognip_> have to ignore the unverified sig?
07:58 < Talkless> wait
07:59 < Talkless> not sure why there's no keys, maybe installing debian-keyring would help? but that's a wild guess
08:00 < Talkless> dognip_:  https://raspberrypi.stackexchange.com/questions/12258/where-is-the-archive-key-for-backports-debian-org#12266
08:00 < Talkless> install key and do apt update and policy one.
08:03 < dognip_> how do i install key? did i miss a step?
08:03 < dognip_> admin@raspberrypi:/ $ gpg --keyserver pgpkeys.mit.edu --recv-key 7638D0442B90D010 gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory gpg: connecting dirmngr at '/run/user/1001/gnupg/S.dirmngr' failed: No such file or directory gpg: keyserver receive failed: No dirmngr
08:05 < Talkless> it's missing some sort of dirmngr, whatever that is
08:06 < Talkless> dognip_: sudo apt install dirmngr ?
08:06 < Talkless> then try again adding keys
08:07 < dognip_> i think it worked: https://imgur.com/a/qZ0h4oK
08:08 < dognip_> didnt change sudo apt update response though
08:10 < Talkless> still missing key?
08:10 < Talkless> are you sure `gpg -a --export 8B48AD6246925553 | sudo apt-key add - ` was executed ?
08:11 < Talkless> dognip_: you also need that 763... key
08:12 < dognip_> i forgot the second step
08:13 < dognip_> update worked
08:13 < Talkless> apt policy golang-1.10
08:13 < dognip_> golang-1.10:   Installed: (none)   Candidate: 1.10.3-1~bpo9+1   Version table:      1.10.3-1~bpo9+1 100         100 http://ftp.debian.org/debian stretch-backports/main armhf Packages
08:14 < Talkless> ok, no install it
08:14 < Talkless> now*
08:15 < dognip_> installed
08:16 < Talkless> ok     
08:16 < Talkless> now tell me the path where do yo uwant to store lnd sources and all it's GO requirements?
08:16 < Talkless> like /home/lnd/lnd.go or whatever
08:16 < Talkless> it will contain many directories, compiled lnd binarsies, etc.
08:16 < Talkless> so-call GOPATH
08:17 < Talkless> so-called*
08:19 < dognip_> ~/download/lnd.go
08:19 < Talkless> ok     
08:19 < Talkless> not sure if I wil lget it right, but lets' try
08:19 < Talkless> go is installed in it's directory.. so
08:19 < dognip_> thanks so much for all this help btw
08:19 < Talkless> k :)
08:19 < Talkless> export GOROOT=/usr/lib/go-1.10/
08:19 < Talkless> export GOPATH=~/download/lnd.go
08:20 < Talkless> export PATH=${GOROOT}/bin:${GOPATH}/bin:$PATH
08:20 < Talkless> no executh "which go" to make sure...
08:20 < Talkless> execute
08:21 < dognip_>    /usr/lib/go-1.10//bin/go
08:21 < Talkless> k     
08:21 < Talkless> go get -d github.com/lightningnetwork/lnd
08:21 < Talkless> it should instal linto lnd.go
08:21 < Talkless> whell not install, just fetch sources
08:22 < dognip_> so far its hanging on that command
08:22 < Talkless> wait a bit
08:22 < Talkless> it's Pi :)
08:22 < dognip_> will do :)
08:24 < dognip_> ok     
08:24 < dognip_> there was no response but it went through
08:24 < Talkless> no you have to go into src/github.com/lightningnetwork/lnd/ which is somewhere inside lnd.go
08:25 < Talkless> maybe ~/downloads/lnd.go/src/github.com/lightningnetwork/lnd/
08:25 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has quit [Remote host closed the connection]     
08:25 < dognip_> there
08:25 < Talkless> ok     
08:25 < Talkless> I guess just "make && make install"
08:25 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has joined #lnd     
08:25 < Talkless> you can make sure that it's master by "git status"
08:26 < dognip_> its fetching dep
08:26 < Talkless> ok it will work for some time
08:26 < dognip_> awesome
08:26 < dognip_> thanks again
08:26 < Talkless> no problem :)
08:26 < dognip_> if this works i wont beat myself up over resuing the address
08:27 < Talkless> if you wish you could tip  me one satoshi via Lignthing to test it out :D
08:27 < dognip_> at least this way i was forced to update and learn some things
08:27 < dognip_> i most certainly will talkless
08:27 < Talkless> :))     
08:27 < dognip_> once im back up and running :)
08:28 < molz> Talkless, does he need to install dep first?
08:28 < Talkless> dognip_: the hardest part is with these nevironment variables, when you'll need to update ldn, you'll have to setup them again.
08:28 < Talkless> maybe, I do not recall
08:28 < Talkless> I believe it should install it automatically
08:29 < Talkless> molz: is make still running?
08:29 < Talkless> oh sorry not that nick
08:29 < dognip_> ya still going
08:29 < Talkless> dognip_: did you get error about dep?
08:29 < Talkless> oh ok
08:29 < dognip_> it wasnt an error about dep
08:30 < dognip_> just let me know it was fetching it automatically
08:30 < dognip_> sorry i missed molz comment
08:30 < molz> from the install guide you need to install dep:  go get -u github.com/golang/dep/cmd/dep
08:31 < Talkless> yeah try that
08:31 < dognip_> ya, the guide also says: dep is automatically installed via the make
08:31 < dognip_> and it seemed to do so
08:32 < molz> oh really
08:32 < dognip_> ya, i think so anyways
08:32 < dognip_> just finished with:  Installing lnd and lncli. go install -v -ldflags "-X main.Commit=90cdc9da8f60dd94d99d61fd9e86a7ffd39b3b1b" github.com/lightningnetwork/lnd github.com/lightningnetwork/lnd/htlcswitch/hodl github.com/lightningnetwork/lnd/htlcswitch github.com/lightningnetwork/lnd/routing github.com/lightningnetwork/lnd go install -v -ldflags "-X main.Commit=90cdc9da8f60dd94d99d61fd9e86a7ffd39b3b1b" github.com/lightningnetwork/lnd/cmd/lnc
08:32 < Talkless> dognip_: I did make and make install, didn't do that "go install"
08:33 < Talkless> oh you mean make did it?
08:33 < Talkless> dognip_: go to @{GOPATH}/bin
08:33 < Talkless> cd ${GOPATH}/bin
08:33 < Talkless> sorry not @
08:33 < dognip_> my last command was make && make install
08:33 < Talkless> you should see lnd and lncli
08:33 < Talkless> ok     
08:33 < Talkless> check if you see binaries there
08:33 < Talkless> ./lnd --version
08:33 < Talkless> also dognip_ you have to update lnd.conf
08:34 < Talkless> dognip_: remove zmqpath and add these instead:
08:34 < Talkless> bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
08:34 < Talkless> bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333
08:34 < dognip_> lnd version 0.4.2-beta commit=90cdc9da8f60dd94d99d61fd9e86a7ffd39b3b1b
08:34 < Talkless> if you have bitcoind in localhost.
08:34 < dognip_> ok, what are those lines doing?
08:34 < dognip_> for my own edification
08:34 < Talkless> they setup conenction to the bitcoind
08:35 < Talkless> so it can monitor transactions
08:35 < dognip_> ok     
08:35 < Talkless> I guess ldn get's blocks and transacitions, I hope you have built bitcoind with ZMQ enabled...
08:35 < Talkless> dognip_: execute:
08:35 < Talkless> ss -ptln | fgrep 2833
08:36 < dognip_> no response
08:36 < Talkless> :/     
08:36 < Talkless> ss -ptln | fgrep bitcoin
08:36 < Talkless> oh I beleive you have to enable it in bitcoin config
08:36 < dognip_> no response
08:36 < dognip_> ok.. my previous install was communicating
08:36 < Talkless> do you have bitcoind running?
08:37 < dognip_> let me adjust my ln and bitcoind configs
08:37 < Talkless> dognip_: bitcoind.conf has to have 
08:37 < Talkless> zmqpubrawblock=tcp://127.0.0.1:28332
08:37 < Talkless> zmqpubrawtx=tcp://127.0.0.1:28333
08:37 < Talkless> dognip_: if ss -ptln | fgrep bitcoin does nothing, I guess bitcoind is not running..?
08:37 < dognip_> zmqpubrawblock=tcp://127.0.0.1:29000 zmqpubrawtx=tcp://127.0.0.1:29000
08:38 < Talkless> oh maybe youre are not a root, so do `sudo ss -ptln...`
08:38 < dognip_> i have that in my bitcoin.conf
08:38 < Talkless> i dunno, they are the same port, not sure if that's OK
08:38 < Talkless> try change how lnd suggests, using 28332 and 28333
08:38 < Talkless> and restart bitcoind
08:39 < dognip_> admin@raspberrypi:~/download/lnd.go/bin $ sudo ss -ptln | fgrep bitcoin LISTEN     0      100    127.0.0.1:29000                    *:*                   users:(("bitcoind",pid=722,fd=17)) LISTEN     0      128    127.0.0.1:8332                     *:*                   users:(("bitcoind",pid=722,fd=10)) LISTEN     0      128          *:8333                     *:*                   users:(("bitcoind",pid=722,fd=144)) LISTEN     0      128
08:40 < Talkless> after restart you should see 28332/3 listening sockets
08:43 < dognip_> everything seems to be working
08:43 < dognip_> it saved my previous lightning config
08:43 < Talkless> ok     
08:43 < Talkless> wait
08:43 < dognip_> bad news, however, my balance is still short todays txn
08:44 < Talkless> you need to update lnd.service systemd unit file to look ant new lnd.go/bin...
08:44 < dognip_> ok     
08:44 < Talkless> stop old service
08:44 < Talkless> edit /etc/sytemd/system/lnd.service
08:44 < Talkless> and edit ExecStart to launch new lnd
08:45 < Talkless> after editing, you have to make system reload unit file with systemctl daemon-reload
08:48 < Talkless> dognip_: consider renaming /usr/local/bin/lnd[cli] so you would not execute old programs
08:49 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
08:50 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd     
09:05 < Talkless> ping dognip_ ?
09:05 < dognip_> i was editting the .service file and didnt properly exit
09:06 < dognip_> had to delete swap file
09:06 < dognip_> then i made the changes
09:06 < dognip_> went to rs lnd and it had an error
09:06 < dognip_> rebooting the pi now
09:07 < dognip_> bitcoind is still booting
09:07 < dognip_> bitcoind is up to date..
09:07 < dognip_>  ● lnd.service - LND Lightning Daemon    Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)    Active: activating (auto-restart) (Result: exit-code) since Thu 2018-08-16 12:06:58 EDT; 39s ago   Process: 720 ExecStart=/home/admin/download/lnd.go/bin/lnd --externalip=${PUBLICIP} (code=exited, status=1/FAILURE)  Main PID: 720 (code=exited, status=1/FAILURE)
09:08 < dognip_> my edit to the service was wrong
09:09 < Talkless> runing manually /home/admin/download/lnd.go/bin/lnd works ?
09:10 < Talkless> you should run as same user as defined in lnd.service by the way
09:10 < Talkless> dognip_: after editing .service file you have to execute `systemctl daemon-reload`
09:13 < dognip_> i dont think it likes the way ive referenced that folder..
09:14 < dognip_> ill mess with changing users..
09:16 < Talkless> you mean "lnd" user (or hatever) is unable to access that executable? could be.
09:16 < Talkless> I installed everything in /home/lnd/lnd, and lnd is lauched with lnd user.
09:17 < dognip_> i have lnd being launched by bitcoin? according to that .service?
09:17 < dognip_> and im not sure they can access that folder?
09:18 < Talkless> uhm     
09:18 < Talkless> su - bitcoin, stat bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
09:18 < dognip_> ins tadicus guide
09:18 < Talkless> oh     
09:18 < dognip_> Now that LND is installed, we need to configure it to work with Bitcoin Core and run automatically on startup.  Open a "bitcoin" user session $ sudo su bitcoin  Create the LND working directory and the corresponding symbolic link $ mkdir /mnt/hdd/lnd $ ln -s /mnt/hdd/lnd /home/bitcoin/.lnd $ cd $ ls -la
09:18 < Talkless> su - bitcoin, stat /home/admin/download/lnd.go/bin/lnd
09:19 < dognip_> is that a command?
09:19 < Talkless> two commands
09:20 < Talkless> I guess you could try to copy lnd and lncli to /usr/local/bin and so make it visible by everybody
09:20 < Talkless> not sure if it needs any other files...
09:20 < Talkless> dognip_: I would create lnd user and move all that stuff there
09:21 < dognip_> what am i expecting from stat command?
09:21 < Talkless> it should not complain like "access denied" or whatever
09:21 < dognip_> it didnt
09:21 < Talkless> it should print some infou about that file
09:21 < Talkless> ok ho about launching lnd within bitcoin user?
09:21 < Talkless> just /home/admin/download/lnd.go/bin/lnd
09:21 < Talkless> while within "su - bitcoin"
09:22 < Talkless> your lnd.conf is within /home/bitcoin/.lnd right?
09:24 < dognip_> would it be possible to take the build file we created from make
09:24 < dognip_> and install it over the old installation?
09:24 < dognip_> yes thats where my conf is
09:25 < Talkless> dognip_: I would suggest what's the rpoblem, why damon doesn't start
09:25 < Talkless> first you could launch lnd manually, and take a look into lnd logs too
09:25 < Talkless> I had issues with lnd.conf
09:25 < Talkless> `journalctl -u lnd.service` didn't help, had to look at logs I believe
09:27 < dognip_> im not able to manually run it now..
09:27 < dognip_> https://imgur.com/a/LsId4lf
09:28 < Talkless> dognip_: this is not whai I've ment with manual
09:28 < Talkless> manual is you enter to bitcoin user
09:29 < Talkless> if you are not rood, the `sudo su - bitcoin` I guess, or `su - bitcoin` if you are root
09:29 < Talkless> then execute /home/admin/download/lnd.go/bin/lnd
09:29 < Talkless> if this works, and `systemctl start` does not, you just have to fix lnd.service
09:30 < dognip_> loadConfig: debug-htlc mode cannot be used on bitcoin mainnet
09:30 < Talkless> also no sure if that --externalip= is needed, you can set it in lnd.conf
09:30 < Talkless> oh you see
09:30 < Talkless> I got same problem by the way
09:30 < dognip_> maybe i editted the wrong conf
09:30 < Talkless> just remove that
09:30 < Talkless> no     
09:30 < Talkless> just delee debug-htlc
09:30 < Talkless> from lnd.conf
09:31 < molz> yay... can't log into slack
09:31 < dognip_> where is the conf i want to edit located
09:32 < Talkless> in /home/bitcoin/.lnd/lnd.conf I believe
09:32 < Talkless> you said it's there
09:32 < dognip_> that was from my original install
09:32 < Talkless> doeans't matter
09:32 < dognip_> i just want to make sure that its still the valid one
09:32 < Talkless> daemon just uses $HOME/.lnd/lnd.conf
09:33 < Talkless> if you run lnd as bitcoin user, it will use $HOME/.lnd/lnd.conf
09:33 < Talkless> it doesn't matter where executable is, in /usr/local/bin or ~/donwloads/lnd.go/bin
09:33 < Talkless> program and program data are different things
09:34 < Talkless> dognip_: just modify /home/bitcoin/.lnd/lnd.conf to comment-out (with #) or delete `debug-htlc..` line
09:34 < Talkless> and then try starting again
09:37 < dognip_> ok it said i need to have different ports like you said
09:37 < dognip_> so i should restart bitcoind?
09:37 < Talkless> you did reboot Pi at some point
09:38 < Talkless> sudo ss -ptln | fgrep 283
09:38 < Talkless> check if you see these 2833.. ports listening
09:39 < Talkless> or just `sudo ss -ptln | fgrep bitcoin`
09:39 < dognip_> cant logged in as bitcoin
09:39 < dognip_> one sec
09:39 < Talkless> exit
09:39 < Talkless> you should use tmux to create multiple terminal panes
09:40 < Talkless> and it remebers if your connections drops or you accidentaly close your terminal
09:40 < dognip_> as opposed to putty?
09:40 < Talkless> no, you do on connection with putty
09:40 < Talkless> launch tmux
09:40 < Talkless> youl'see green bottom line
09:40 < Talkless> and in that you can split terminal into few
09:40 < Talkless> one for root and one for bitcoin or whatever
09:41 < Talkless> and if you close putty, that session stays alive
09:41 < Talkless> and you can connect with putty again, and "tmux a" will attach last session
09:45 < dognip_> ill look into this
09:45 < dognip_> that sounds nice
09:45 < Talkless> ok now that are you doing now?
09:45 < Talkless> did you check listening ports?
09:46 < Talkless> are bitcoinc.conf updated?
09:46 < dognip_> im rebooting pi atm
09:46 < dognip_> after updating bitcoin conf
09:47 < Talkless> you coul just do `systemctl restart bitcoind`
09:47 < Talkless> no need to reboot everythng, really
09:52 < molz> Talkless, you are de man!
09:52 < Talkless> molz: we didn't achieve it yet really
09:52 < molz> all that is worth it to read, and no spam from the idiotic spammers for a change, wow
09:54 < Talkless> dognip_: ping
09:55 < dognip_> haha
09:56 < dognip_> well this is embarassing but after the rs i managed to get blocked out of ssh by trying to login in as admiin
09:56 < dognip_> not admin
09:56 < dognip_> so i hooked up a keyboard and monitor directly to pi
09:56 < dognip_> but i cant type | on that keyboar
09:56 < Talkless> you mean fail2ban banned you?
09:56 < dognip_> it comes out as a colon
09:56 < dognip_> yes, i think i have to wait a bit longer
09:57 < Talkless> dognip_: change your computer ip address then
09:57 < Talkless> or wait 15 minutes I guess, not sure how mutch
09:58 -!- dognip [8067f411@gateway/web/freenode/ip.128.103.244.17] has joined #lnd     
10:01 -!- dognip_ [41700803@gateway/web/freenode/ip.65.112.8.3] has quit [Ping timeout: 252 seconds]     
10:02 < dognip> what is the command to run it manually
10:03 < Talkless> just path to the ldn file, like /home/admin/downlodas/lnd.go/bin/lnd
10:03 < Talkless> I did a typo
10:03 < Talkless> that's if youre as `bitcoin` user
10:03 < Talkless> if not, just try `systemctl start lnd`
10:05 < dognip> ok its up
10:06 < Talkless> dognip:  /home/admin/download/lnd.go/bin/lnd getinfo | fgrep version
10:08 < dognip> loadConfig: either bitcoin.active or litecoin.active must be set to 1 (true)
10:10 < dognip> i think lnd crashed...
10:10 < dognip> admin@raspberrypi:~ $ systemctl status lnd ● lnd.service - LND Lightning Daemon    Loaded: error (Reason: Invalid argument)    Active: inactive (dead)
10:10 < dognip> trying to restart it
10:10 < dognip> bitcoin@raspberrypi:~ $ /home/admin/download/lnd.go/bin/lnd Attempting automatic RPC configuration to bitcoind Automatically obtained bitcoind's RPC credentials 2018-08-16 13:09:43.764 [INF] LTND: Version 0.4.2-beta commit=90cdc9da8f60dd94d99d61fd9e86a7ffd39b3b1b 2018-08-16 13:09:43.764 [INF] LTND: Active chain: Bitcoin (network=mainnet)
10:10 < dognip> hanging there
10:11 < Talkless> dognip: you have to fix config, id did not crash, it exited
10:11 < Talkless> or you just fixed it?
10:11 < dognip> which config are you referencing currently?
10:11 < Talkless> lnd.conf
10:11 < Talkless> " loadConfig: either bitcoin.active or litecoin.active must be set to 1 (true)" is about lnd.conf
10:12 < Talkless> "hanging there" well just wait until it fully starts
10:12 < Talkless> dognip: if you didn't lauchned lnd with systemctl, do not use `status`.
10:13 < Talkless> if you think it's now working, ctr-c it to stop, and then start with `systemctl start lnd` as a background daemon.
10:14 < dognip> i am quite certain my lnd.service is still wrong
10:15 < Talkless> because..?
10:15 < dognip> when i rebooted the pi it said it needed to be an absolute path
10:15 < dognip> and it said it was ignoring it
10:15 < dognip> i had tried ~/download etc
10:15 < dognip> because /home/admin etc didnt work
10:15 < dognip> let me change
10:16 < dognip> do you still think i should delete the externalip portion?
10:16 < Talkless> dognip: don't use ~/, write /home/admin/downlods....
10:17 < Talkless> yes dognip, take a look at my config: https://pastebin.com/C0BEVkFg
10:17 < Talkless> chage "..." lines to what's needed
10:18 < Talkless> dognip: update lnd.service to not use relavie ~/ path, change to /home/admin/downloads/lnd.go/bin/lnd
10:18 < dognip> made this change, going to ln conf now
10:19 < Talkless> and please paste me `sudo ss -ptln | fgrep bitcoin`
10:24 < Talkless> dognip: 
10:24 < dognip> i made changes to config
10:24 < Talkless> dognip: try `systemclt start lnd` maybe it will work now
10:24 < dognip> then i tried to run it manually and its hanging 'waiting for lncli unlock bit
10:25 < Talkless> maybe another lncli is left hanging?
10:25 < dognip> very possible
10:25 < dognip> should i reboot?
10:25 < Talkless> killall lncli
10:25 < dognip> ok     
10:26 < dognip> no processes found
10:26 < Talkless> ugh, i dunno.. reboot.?
10:26 < dognip> want me to systemclt start lnd?
10:26 < Talkless> yeah try that 
10:27 < Talkless> and I still would like to see `sudo ss -ptln | fgrep bitcoin`
10:27 < dognip> admin@raspberrypi:~ $ sudo systemctl start lnd admin@raspberrypi:~ $ systemctl status lnd.service ● lnd.service - LND Lightning Daemon    Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)    Active: active (running) since Thu 2018-08-16 13:27:35 EDT; 6s ago  Main PID: 890 (lnd)    CGroup: /system.slice/lnd.service            └─890 /home/admin/download/lnd.go/bin/lnd --externalip=128.103.244.93 admin
10:28 < dognip> admin@raspberrypi:~ $ sudo ss -ptln | fgrep bitcoin LISTEN     0      100    127.0.0.1:28332                    *:*                   users:(("bitcoind",pid=705,fd=17)) LISTEN     0      128    127.0.0.1:8332                     *:*                   users:(("bitcoind",pid=705,fd=10)) LISTEN     0      128          *:8333                     *:*                   users:(("bitcoind",pid=705,fd=138)) LISTEN     0      100    127.0.0.1:283
10:29 < Talkless> dognip: bitcoind does not listen to 28333
10:30 < Talkless> dognip: bitcoind does not listen to 28333, do you have `zmqpubrawtx=tcp://127.0.0.1:28333` in bitcoin.conf ?
10:31 < dognip> i have that line
10:31 < dognip> i bleieve it is listening
10:31 < Talkless> I see only 28332
10:31 < dognip> https://imgur.com/a/iEArE8d
10:31 < Talkless> oh right your copy paste was not complete, sorry
10:31 < dognip> my bad
10:32 < Talkless> ok now you can follow lnd log with `journalctl -f -u lnd`
10:32 < Talkless> does it seem "alive" ?
10:32 < dognip> yes     
10:32 < dognip> it sure does :)
10:32 < Talkless>  /home/admin/download/lnd.go/bin/lnd getinfo | fgrep version 
10:32 < Talkless> ?     
10:32 < dognip> balance is still wrong but its alive
10:33 < dognip> loadConfig: either bitcoin.active or litecoin.active must be set to 1 (true)
10:33 < dognip> bitcoin.active is definitely set somewhere
10:33 < Talkless> uhm     
10:33 < dognip> dont know why it says that
10:33 < Talkless> ps aux | fgrep lnd
10:33 < Talkless> what is the user of lnd ?
10:33 < Talkless> maybe you have changed it?
10:33 < dognip> bitcoin i think
10:33 < Talkless> ps aux | fgrep lnd
10:34 < dognip>  bitcoin    890 79.2 14.0 1137560 140500 ?      Ssl  13:27   5:07 /home/admin/download/lnd.go/bin/lnd --externalip=128.103.244.93 admin     1022  0.0  0.0   4372   548 pts/0    S+   13:34   0:00 grep -F --color=auto lnd admin@raspberrypi:~ $
10:34 < Talkless> yeah, lnd
10:34 < Talkless> oh bitcoin* I've ment
10:34 < dognip> what is that command doing
10:35 < Talkless> ps aux prints processes with various information, like user, pid , etc
10:35 < Talkless> first column is user
10:35 < Talkless> so I see it's bitcoin
10:35 < dognip> ok     
10:35 < Talkless> fgrep just filters text lines so you see only these lines that contain "lnd"
10:35 < dognip> ahh ok
10:35 < Talkless> and | ("pipe") passes first commands outputs to the seconds
10:35 < Talkless> to the second
10:36 < Talkless> you can execut `ps aux` to see all processses
10:36 < dognip> so we looked at output of getino for version?
10:36 < dognip> getinfo*
10:36 < Talkless> dognip: coul you remove `--externalip` from lnd.service?
10:37 < Talkless> maybe if you pass argument, it does not use lnd.conf ?
10:37 < Talkless> so it says that it does not get "bitcoin.active" set.
10:37 < dognip> ok, but then i specify it somewhere else?
10:37 < Talkless> edit lnd.service, then `systemctl daemon-reload` and then `systemctl restart lnd`
10:37 < Talkless> dognip: in lnd.conf, as my example showed
10:38 < dognip> ok     
10:38 < Talkless> [20:17] <Talkless> yes dognip, take a look at my config: https://pastebin.com/C0BEVkFg
10:40 < dognip> ok ive moved that from lnd.service to lnd.conf
10:41 < dognip> i have to do that daemon restart thing?
10:41 < Talkless> yeas
10:41 < Talkless> systemctl daemon-reload
10:41 < Talkless> systemctl restart lnd
10:41 < Talkless> daemon-reload says to rescan your .service changes
10:42 < dognip> ok both went through
10:43 < dognip> im looking at the journal and lnd.service is failing
10:43 < dognip> failed with reuslt exit-code
10:43 < Talkless> no better info?
10:44 < dognip> Aug 16 13:43:51 raspberrypi systemd[1]: lnd.service: Service hold-off time over, scheduling restart. Aug 16 13:43:51 raspberrypi systemd[1]: Stopped LND Lightning Daemon. Aug 16 13:43:51 raspberrypi systemd[1]: Started LND Lightning Daemon. Aug 16 13:43:51 raspberrypi lnd[1144]: Attempting automatic RPC configuration to bitcoind Aug 16 13:43:51 raspberrypi lnd[1144]: Automatically obtained bitcoind's RPC credentials Aug 16 13:43:51 rasp
10:44 < dognip>  Aug 16 13:43:51 raspberrypi systemd[1]: lnd.service: Main process exited, code=exited, status=1/FAILURE Aug 16 13:43:51 raspberrypi systemd[1]: lnd.service: Unit entered failed state. Aug 16 13:43:51 raspberrypi systemd[1]: lnd.service: Failed with result 'exit-code'.
10:45 < Talkless> dognip: check contenst of .lnd/logs/bitcoin/mainnet/lnd.log maybe the problem is logged there
10:45 < dognip> ok      
10:45 < dognip> just to verify
10:45 < dognip> should this /home/admin/download/lnd.go/bin/lnd getinfo | fgrep version
10:45 < dognip> be done on lncli not lnd?
10:46 < Talkless> sorry, that should be lncli
10:46 < Talkless> my bad
10:46 < Talkless> it should connect to daemon (when it's running) and get it's version
10:46 < Talkless> just for sanyti check
10:46 < Talkless> sanity*
10:46 < Talkless> but I guess it's not running in your case?
10:46 < dognip> lncli getinfo was returning data
10:47 < dognip> maybe i should revert changes?
10:49 < Talkless> dognip: I remember that there was problem for me, that systemctl didn't start lnd
10:49 < Talkless> so I did
10:49 < Talkless> systemctl stop lnd
10:49 < Talkless> systemctl start lnd
10:49 < Talkless> there's also systemctl reset-failed
10:50 < dognip> i reverted changes and daemon-reload and restart lnd
10:51 < dognip> looking at journal it looks good? new channels discovered etc
10:51 < dognip> just the external ip change was reverted
10:52 < Talkless> welp strange
10:52 < Talkless> whatever
10:53 < Talkless> dognip: so there's no longer "loadConfig: either bitcoin.active or litecoin.active must be set to 1 (true)" ?
10:53 < dognip> when i do this: /home/admin/download/lnd.go/bin/lnd getinfo | fgrep version
10:53 < dognip> i get  loadConfig: either bitcoin.active or litecoin.active must be set to 1 (true)
10:54 < dognip> but this
10:54 < dognip> admin@raspberrypi:~ $ /home/admin/download/lnd.go/bin/lncli getinfo | fgrep version     "version": "0.4.2-beta commit=90cdc9da8f60dd94d99d61fd9e86a7ffd39b3b1b" admin@raspberrypi:~ $
10:54 < dognip> looks good
10:54 < Talkless> ooh     
10:54 < Talkless> nono, it should be lncli
10:55 < dognip> ya :)
10:55 < Talkless> ok dognip, so you have latst lnd running
10:55 < dognip> so in about 3 hours you made one mistake
10:55 < Talkless> does it start automatically at boot?
10:55 < dognip> i probably made 100 so we'll call it even
10:55 < Talkless> systemctl status lnd should say "enabled"
10:55 < dognip> systemctl status lnd ● lnd.service - LND Lightning Daemon    Loaded: loaded (/etc/systemd/system/lnd.service; enabled; vendor preset: enabled)    Active: active (running) since Thu 2018-08-16 13:48:38 EDT; 7min ago  Main PID: 1246 (lnd)    CGroup: /system.slice/lnd.service            └─1246 /home/admin/download/lnd.go/bin/lnd --externalip=128.103.244.93
10:56 < Talkless> yeah looks enabled.
10:56 < dognip> i think it would work at boot
10:56 < Talkless> do you unlock wallet every time, or have unencrypted setup?
10:56 < dognip> sadly, my original problem remains!
10:56 < dognip> i unlock it 
10:56 < Talkless> ok, I guess you could try to report bug, because it's the sam issue with latest code.
10:56 < dognip> ok. do you think starting from the seed would recover?
10:57 < Talkless> idduno, I haven't try to recover lnd wallet
10:57 < Talkless> I would disable autopilot and close all channels, maybe then lnd will "refresh" it's wallet balance or whatever...
10:57 < dognip> can you disable autopilot on the fly
10:58 < dognip> or do i change and reboot
10:58 < Talkless> I haven't seen option in "lncli help" to disable on the fly
10:58 < Talkless> I just stop, edit lnd.conf, and start
11:00 < Talkless> OJ I have to go  away for a dinner
11:00 < Talkless> OK*     
11:00 < dognip> thank you so much for the help talkless
11:00 < dognip> ill come on again tomorrow to get your lightning node info
11:00 < dognip> for a payment
11:01 < Talkless> :D     
11:01 < Talkless> I don't need that, but if you'll insist...
11:01 < dognip> I insist!
11:01 < dognip> it was a learning experience
11:02 < dognip> even i was tired of it and i have money invested!
11:24 < dognip> talkless, i have some open channels now
11:24 < dognip> pm me your info
11:35 -!- grafcaps [~haroldbr@104.137.194.255] has joined #lnd     
11:41 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection]     
11:41 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd     
11:50 < Talkless> Any deas on what does "Failing link:" ... "unable to accept new commitment: rejected commitment: commit_height=1, invalid_commit_sig" mean? My new channel is pending force close.. ?
11:53 < Talkless> that happened after "Received re-establishment message from remote side for channel(..."
11:55 < molz> Talkless, not sure i understand the story.. you tried to open a channel to some node and it got force closed instantly?
11:55 < Talkless> Channel was open, and my node decided to forcefully close it
11:56 < Talkless> channel has 36 confirmations, closing transaction has 7 now
11:56 < Talkless> maybe it didn't liked because this was _second_ channel to the same node
11:57 < Talkless> first channel is still allive
11:57 < molz> it's probably a c-lightning node 
11:58 < Talkless> I believe I've opened it agaist speciffically LND node (joltfun). They do have C-Lighnung one, and owner said LND->C_lightning node does experience closed challes time to time.. but this time is LND->LND :/
12:00 < molz> hmm     
12:03 < Talkless> After "Received re-establishment message from remote side for channel(" i see next message:
12:03 < Talkless> HSWC: Sent 48299 satoshis and received 0 satoshis in the last 10 seconds (14.000000 tx/sec
12:03 < Talkless> this 48K is for older channel of the same node!
12:04 < Talkless> maybe it htought that remote node declared that I have paid 48k in that new channel, and guesed that it's cheating?
12:04 < Talkless> First channel has remote balance of 48299, got this " HSWC: Sent 48299 satoshis and received ", and got second, zero-payments-done channel force-closed...
12:17 < molz> you can ignore that message
12:30 < Talkless> " in the last 10 seconds".. it was done yeasterday...
12:30 < Talkless> https://github.com/lightningnetwork/lnd/issues/1737
12:46 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
12:50 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #lnd     
12:54 -!- qubenix [~qubenix@193.148.18.237] has quit [Quit: qubenix]     
13:07 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer]     
13:12 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #lnd     
13:28 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer]     
13:31 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #lnd     
13:36 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Client Quit]     
13:40 -!- tin_ [~tyn@2601:645:4100:87b0:a479:fc52:3607:a8fd] has joined #lnd     
13:49 -!- qubenix [~qubenix@204.152.210.239] has joined #lnd     
14:11 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!]     
14:23 -!- tin_ [~tyn@2601:645:4100:87b0:a479:fc52:3607:a8fd] has quit [Ping timeout: 260 seconds]     
15:48 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 240 seconds]     
16:24 <@roasbeef> dognip: whck your set of pending chacnnels, and also that you're still getting notifications from bitcoind 
17:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd     
17:27 -!- mode/#lnd [-n] by ChanServ     
17:34 < No>  ­ ­ ­ ­ ­  http://magaimg.net/img/wqz.jpg  ­  ­ ­ ­ ­ ­ ­ ­ ­ ­ http://magaimg.net/img/wqz.jpg  ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­
17:35 -!- mode/#lnd [+n] by ChanServ     
17:36 <@roasbeef> fkn spammers 
17:36 <@roasbeef> sorry about that y'all 
18:36 -!- gethh [uid264798@gateway/web/irccloud.com/x-pdqujnzcdtualgfv] has quit [Quit: Connection closed for inactivity]     
18:55 -!- ken2812221 [~ken281222@180.217.169.165] has joined #lnd     
19:13 -!- rls [~rls@69.197.143.181] has quit [Read error: Connection reset by peer]     
19:47 -!- reallll [~belcher@unaffiliated/belcher] has joined #lnd     
19:50 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 255 seconds]     
21:59 -!- force7 [~force@c-71-232-65-53.hsd1.ma.comcast.net] has quit [Remote host closed the connection]     
22:53 -!- gethh [uid264798@gateway/web/irccloud.com/x-oultfutsxusiohol] has joined #lnd     
22:54 -!- drrty [drrty@gateway/vpn/privateinternetaccess/drrty] has quit [Ping timeout: 272 seconds]