--- Day changed Sun Feb 03 2019 01:02 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:16 -!- yoctopede [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 01:16 -!- zshlyk [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 256 seconds] 01:41 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 01:52 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd 02:02 -!- kexkey_ [~kexkey@172.98.82.16] has quit [Read error: Connection reset by peer] 02:17 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Quit: Leaving] 03:09 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 246 seconds] 04:00 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Read error: Connection reset by peer] 04:01 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 04:53 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 04:55 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lnd 05:00 -!- chunkypuffs [~chunkypuf@znc.gamecu.be] has quit [Remote host closed the connection] 05:01 -!- chunkypuffs [~chunkypuf@znc.gamecu.be] has joined #lnd 06:20 -!- jchia_ [~jchia@58.32.32.5] has joined #lnd 06:27 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 06:29 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 06:29 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds] 06:31 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 06:49 -!- jpe [~jp@fnord.cryptophone.de] has joined #lnd 06:54 -!- jpe [~jp@fnord.cryptophone.de] has quit [Ping timeout: 240 seconds] 07:50 < e4xit> What do each of the lnd subsystems stand for when setting debug levels?: [ATPL BRAR BTCN CHDB CMGR CNCT CRTR DISC FNDG HSWC LNWL LTND NTFN PEER RPCS SPHX SRVR SWPR UTXN] 08:15 -!- Marshallazora [~Marshalla@136.0.2.194] has joined #lnd 08:15 -!- Marshallazora [~Marshalla@136.0.2.194] has left #lnd [] 08:55 -!- jpe [~jp@92.116.83.251] has joined #lnd 08:56 < e4xit> There is a small typo in the lnd.conf sample, L117: https://github.com/lightningnetwork/lnd/blob/b341dea3733cb721d6aecefa54123b5b1ac7b126/sample-lnd.conf#L117 it should read "Use lnd --debuglevel=show" where is currently says ..."Use btcd --debuglevel=show", I doubt that qualifies for a PR on it's own though... 09:02 < Veggen> nothing is too small for a PR. 09:03 < Veggen> if you haven't created one before, it'd be a good exercise :) 09:05 -!- so [~so@unaffiliated/so] has quit [Ping timeout: 246 seconds] 09:10 -!- so [~so@unaffiliated/so] has joined #lnd 09:17 < molz> we do run btcd, not sure if it's a typo 09:21 < molz> this is what it shows if you run that command: 09:21 < molz> >btcd --debuglevel=show 09:21 < molz> Supported subsystems [ADXR AMGR BCDB BTCD CHAN CMGR DISC INDX MINR PEER RPCS SCRP SRVR SYNC TXMP] 09:22 < molz> and here's for lnd: 09:22 < molz> >lnd --debuglevel=show 09:22 < molz> Supported subsystems [ATPL BRAR BTCN CHDB CMGR CNCT CRTR DISC FNDG HSWC LNWL LTND NTFN PEER RPCS SPHX SRVR SWPR UTXN] 09:23 < molz> and here's for ltcd: 09:23 < molz> >ltcd --debuglevel=show 09:23 < molz> Supported subsystems [ADXR AMGR BCDB BMGR CHAN CMGR DISC INDX LTCD MINR PEER RPCS SCRP SRVR TXMP] 09:23 < molz> create your own go project and find out more :P 10:18 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #lnd 10:46 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 11:16 -!- kolpi [8fb0f2b2@gateway/web/freenode/ip.143.176.242.178] has joined #lnd 11:16 -!- kolpi [8fb0f2b2@gateway/web/freenode/ip.143.176.242.178] has quit [Client Quit] 11:16 -!- kolpi [8fb0f2b2@gateway/web/freenode/ip.143.176.242.178] has joined #lnd 11:44 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 11:54 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 11:57 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 12:02 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 240 seconds] 12:08 -!- deusexbeer [~deusexbee@093-092-176-118-dynamic-pool-adsl.wbt.ru] has joined #lnd 12:22 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 12:28 -!- deusexbeer [~deusexbee@093-092-176-118-dynamic-pool-adsl.wbt.ru] has quit [Remote host closed the connection] 12:28 -!- deusexbeer [~deusexbee@093-092-176-118-dynamic-pool-adsl.wbt.ru] has joined #lnd 12:43 -!- manantial [~tecnecio@unaffiliated/manantial] has quit [Remote host closed the connection] 13:22 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #lnd 13:54 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 14:29 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 14:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection] 14:47 -!- QuanticPotato [bed2387d@gateway/web/freenode/ip.190.210.56.125] has joined #lnd 14:51 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 14:53 < QuanticPotato> Hi! Yesterday I talked here about a posible bug on lnd's sync. I was asked to try to reproduce it. I deleted my .nd folder and restarted the sync and... the error apeared again. The exact warning message is "Unable to synchronize wallet to chain: did not find a suitable birthday block with a timestamp greater than 2019-01-30 15:15:05 -0300 -03". Using litecoin mainnet, synched to the blockchain. Restarging lnd fixes the problem. 14:53 < QuanticPotato> Restarting lnd* 14:54 < lndbot> If you have a consistent repro, maybe you can post the exact steps to repro in a github issue 14:55 < QuanticPotato> "consistent" is only 2 times so far, but sure, I'll open an issue. 14:58 < QuanticPotato> I'd like to look at the code behind this to try to find the bug. Any pointers? I tried grepping the error, but had no luck. 14:58 < lndbot> Might be in btcwallet in btcsuite 15:00 < QuanticPotato> I'll start there then. Thanks! 15:08 < kolpi> If a router does not support UPnP then should the parameter nat=true be removed to set to 'false'? 15:16 -!- bilthon [bee97252@gateway/web/freenode/ip.190.233.114.82] has joined #lnd 15:16 < bilthon> hello 15:37 < ysangkok> kolpi: if your router doesn't support UPnP, it will just ignore the messages emitted by nat=true. you may as well set it to false if it doesn't help 15:43 < bilthon> I'm trying to run lnd with bitcoind, I am going to compile bitcoind first, so do I have to enable wallet? or can I disable it (on bitcoind) with the --disable-wallet flag 15:43 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 246 seconds] 15:44 < lndbot> You don’t need the bitcoind wallet 15:58 < bilthon> good, thanks! 16:10 < molz> guys, please test v0.5.2-beta-rc6: https://github.com/lightningnetwork/lnd/releases prefer you test this on testnet 16:56 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 272 seconds] 17:11 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 17:12 -!- rh0nj [~rh0nj@88.99.167.175] has joined #lnd 17:17 -!- kolpi [8fb0f2b2@gateway/web/freenode/ip.143.176.242.178] has quit [Ping timeout: 256 seconds] 17:18 -!- yoink [~yoink@unaffiliated/yoink] has joined #lnd 18:08 -!- jpe_ [~jp@92.116.89.17] has joined #lnd 18:11 -!- jpe [~jp@92.116.83.251] has quit [Ping timeout: 240 seconds] 20:10 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 21:00 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 21:22 -!- bilthon [bee97252@gateway/web/freenode/ip.190.233.114.82] has quit [Quit: Page closed] 21:28 -!- aerth [~aerth@gateway/tor-sasl/aerth] has quit [Ping timeout: 256 seconds] 21:31 -!- aerth [~aerth@gateway/tor-sasl/aerth] has joined #lnd 21:38 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 21:38 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 22:15 < raucao> question: should it be possible to switch from btcd to bitcoind by only changing the config? 22:16 < raucao> lnd seems to be unable to sync for me after doing that. zmq enabled and all 22:16 < raucao> says "Waiting for chain backend to finish sync, start_height=561458", but bitcoind is fully synced itself 22:18 < raucao> a few minutes later, this happens: "2019-02-04 06:17:07.146 [ERR] LNWL: Failed to process consensus server notification (name: `blockconnected`, detail: `failed to store sync information 0000000000000000002c3e1d299212fd070a2f3d4d4e18d1b5dbbbaf1a7e1f31: failed to fetch block hash for height 561458: block not found`) 22:18 < raucao> " 22:18 < raucao> if i restart it, the same errors just happen for the next block if there's a new one 22:18 < raucao> any pointers much appreciated. thx 22:29 < Veggen> you might be too impatient? 22:29 < Veggen> https://github.com/lightningnetwork/lnd/issues/2560 22:35 < buZz> raucao: disk full? :P 22:36 < raucao> Veggen: that was it 22:36 < raucao> thx 22:37 <@roasbeef> raucao: it's a rougue log message really at times, while yu'roe syncing and the main chain is ahead 22:37 < raucao> as there's zero output about what's happening and only the error, that's painting the wrong picture 22:38 < raucao> i'll be more patient next time :) 22:40 < Veggen> roasbeef: might consider adding a bit output, say every 10k blocks, in info level? People are getting confused there. 23:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 23:15 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 23:36 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd