Running bitcoin node with LN hub on a Raspberry Pi 3

TheBeardedBaby

legendary

Activity: 2240

Merit: 3150

₿uy / $ell ..oeleo ;(

Quote from: bitart on October 01, 2018, 05:27:51 PM

Mine is sitting in the cupboard (doors closed) and it's fine there were no problem with overheating or anything similar (I've no HDD attached, I was trying to run a neutrino type hub)
I've bought this copper heat sink, it's for the Pi and it was really easy to stick it onto the chips... it's about 2 EUR, free shipping, so it's not a big deal...
I think you should have some cooling because of the SATA HDD rather than the PI

Yeah, that was my concern too, I'm thinning for something like this for the SATA solution and probably will have it open for a while.

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

Quote from: TheBeardedBaby on October 01, 2018, 07:33:59 AM

Quote from: lightningslotmachine on October 01, 2018, 07:03:57 AM

I used this tutorial to setup bitcoin + lightning

https://github.com/Stadicus/guides/blob/master/raspibolt/README.md

Very easy to follow.

Great, thank you for the info, how are the temperatures btw? Do I need an extra/bigger radiator to cool it, maybe fan too? When everything is done I'll probably will put it in a box and have it on the desk but I want to order everything together, that's why I'm asking if I'll need some more stuff.

Mine is sitting in the cupboard (doors closed) and it's fine there were no problem with overheating or anything similar (I've no HDD attached, I was trying to run a neutrino type hub)
I've bought this copper heat sink, it's for the Pi and it was really easy to stick it onto the chips... it's about 2 EUR, free shipping, so it's not a big deal...
I think you should have some cooling because of the SATA HDD rather than the PI

delpiero10

full member

Activity: 270

Merit: 101

Quote from: TheBeardedBaby on October 01, 2018, 07:33:59 AM

how are the temperatures btw?

CPU temp is around 58°C on my node(btc+ln)

lightningslotmachine

newbie

Activity: 22

Merit: 6

Quote from: TheBeardedBaby on October 01, 2018, 07:33:59 AM

Great, thank you for the info, how are the temperatures btw? Do I need an extra/bigger radiator to cool it, maybe fan too? When everything is done I'll probably will put it in a box and have it on the desk but I want to order everything together, that's why I'm asking if I'll need some more stuff.

You don't need anything more than the stuff listed there. No extra fan or anything like that. Even a Raspberry Pi case is optional. Don't think it will overheat. I've had it running 24/7 for a couple of weeks now. Been working just fine.

TheBeardedBaby

legendary

Activity: 2240

Merit: 3150

₿uy / $ell ..oeleo ;(

Quote from: lightningslotmachine on October 01, 2018, 07:03:57 AM

I used this tutorial to setup bitcoin + lightning

https://github.com/Stadicus/guides/blob/master/raspibolt/README.md

Very easy to follow.

Great, thank you for the info, how are the temperatures btw? Do I need an extra/bigger radiator to cool it, maybe fan too? When everything is done I'll probably will put it in a box and have it on the desk but I want to order everything together, that's why I'm asking if I'll need some more stuff.

lightningslotmachine

newbie

Activity: 22

Merit: 6

I used this tutorial to setup bitcoin + lightning

https://github.com/Stadicus/guides/blob/master/raspibolt/README.md

Very easy to follow.

TheBeardedBaby

legendary

Activity: 2240

Merit: 3150

₿uy / $ell ..oeleo ;(

How is going with your project?
I'm considering order a RB Pi3B+ with a SATA module to hook up one HDD for a full node + LN.
Never played with Raspberry before so it's gonna be a challenge.
How are the temperatures btw. Have to find a good place and build a box with cooling. I really want to start rolling next month.

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

Quote from: Rath_ on August 02, 2018, 12:53:42 PM

Quote from: bitart on August 02, 2018, 12:30:57 PM

Just managed to spend a little time with the Raspberry PI LN hub project again, it's not easy to deal with things like this, if you have no freetime

First thing is to update the lnd itself, there's a new version out there, so I need to update it, preferably via git, hope it will be an easy go... I'll be back...

Did you consider running RaspiBlitz? The whole setup process is fairly easy and it shouldn't take you too much time. Check out the readme file for detailed documentation. It is worth mentioning that this project supports LCD displays so that you can easily view the most important information any time you want.

Take a look at some questions regarding running a Lightning Network node here.

Thanks for the info, I've just checked it. It's nice and user friendly, so I'll give it a try if my project won't succeed...
The only (but very important) difference for me that it uses a full blockchain on an external HDD instead of the "light" version (neutrino node), which don't require a full blockchain available locally (uses a trusted node for the blockchain data), which could be really handy if you already have a full node locally and you want to play only with LN on your Raspberry PI.
So I'll give it a try as soon as I give up this neutrino thing

Rath_

legendary

Activity: 1876

Merit: 3132

Quote from: bitart on August 02, 2018, 12:30:57 PM

Just managed to spend a little time with the Raspberry PI LN hub project again, it's not easy to deal with things like this, if you have no freetime

First thing is to update the lnd itself, there's a new version out there, so I need to update it, preferably via git, hope it will be an easy go... I'll be back...

Did you consider running RaspiBlitz? The whole setup process is fairly easy and it shouldn't take you too much time. Check out the readme file for detailed documentation. It is worth mentioning that this project supports LCD displays so that you can easily view the most important information any time you want.

Take a look at some questions regarding running a Lightning Network node here.

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

Just managed to spend a little time with the Raspberry PI LN hub project again, it's not easy to deal with things like this, if you have no freetime

First thing is to update the lnd itself, there's a new version out there, so I need to update it, preferably via git, hope it will be an easy go... I'll be back...

delpiero10

full member

Activity: 270

Merit: 101

Quote from: vlom on May 02, 2018, 03:11:53 PM

really nice. thank you for sharing all this. as soon as i find the time i will try it too. i have an unused pi waiting to be connected. btw: which post should I merit... Tongue

btw: a first question. i once had a core node running. but the pi was so slow and it wasent able to be up to date with the chain. do you have this problem too?

If you are talking about pi performance(not slow downloading speed) you can run raspberry in cli mode(without GUI). You can find it in raspi-config.

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

Quote from: vlom on May 02, 2018, 03:11:53 PM

really nice. thank you for sharing all this. as soon as i find the time i will try it too. i have an unused pi waiting to be connected. btw: which post should I merit... Tongue

Thanks

Of course, all of them Tongue

Quote from: vlom on May 02, 2018, 03:11:53 PM

btw: a first question. i once had a core node running. but the pi was so slow and it wasent able to be up to date with the chain. do you have this problem too?

So you mean you have started to run a full node on the pi, let it download the whole chain and sync it afterwards? It takes week or so, because of the size of the blockchain and the realatively slow processor of the PI.
Usually the solution is to run first a full node on a windows/linux PC (with a powerful processor) and let it download and sync the blockchain to an external USB connected HDD.
As soon as it has finished the sync (takes days, still) you can detach the HDD and attach it to the PI and voilá, the PI has to do nothing but continue to sync the daily changes which it can handle more easily.
If you have an older PI, with a slower processor, search for the model if it worths the effort to try to build it, because of the minimal speed requirements.

vlom

legendary

Activity: 1498

Merit: 1117

really nice. thank you for sharing all this. as soon as i find the time i will try it too. i have an unused pi waiting to be connected. btw: which post should I merit... Tongue

btw: a first question. i once had a core node running. but the pi was so slow and it wasent able to be up to date with the chain. do you have this problem too?

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

So, I had enough trying to locate a working neutrino compatible node for the LN mainnet (I don't want to run a full node on the raspberry PI, because this is the point of the neutrino node).
So I switched to testnet and voilá...

Code:

lnd –bitcoin.active –bitcoin.testnet –debuglevel=debug –bitcoin.node=neutrino --noencryptwallet --neutrino.connect=faucet.lightning.community

It's running (OK, still "Catching up block hashes"), but at least there's no problem with finding proper nodes to connect to.
So I'll start now with testnet and later on with the mainnet...

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

Quote from: delpiero10 on April 12, 2018, 03:11:02 PM

one more question... did you modify the config.go file again after git reset? You have mentioned that this change is needed to run a neutrino version:

Code:

if cfg.Bitcoin.Node == "neutrino" && cfg.Bitcoin.MainNet {
str := "%s: neutrino isn't yet supported for " +
"bitcoin's mainnet"
err := fmt.Errorf(str, funcName)
return nil, err
}

Thanks for pointing me to the right direction, I haven't modified the file, and as I've checked the log I've posted in the last post, I've realized that I've forgot to run the

Code:

make && make install

after the successfull git pull to install the new version after downloading it.
I've quickly run the install, and now the version of the lnd is really 0.4.1, but the problem remains the same.
I'm looking into the DNS things maybe I can find something with google...

delpiero10

full member

Activity: 270

Merit: 101

one more question... did you modify the config.go file again after git reset? You have mentioned that this change is needed to run a neutrino version:

Code:

if cfg.Bitcoin.Node == "neutrino" && cfg.Bitcoin.MainNet {
str := "%s: neutrino isn't yet supported for " +
"bitcoin's mainnet"
err := fmt.Errorf(str, funcName)
return nil, err
}

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

Quote from: delpiero10 on April 12, 2018, 12:23:06 PM

Quote

My problem is that my lnd neutrino node can't find any node to connect to, so I'm still struggling with it, but somehow sometime I'll get it working...

Can you upload log file? Is there any error?

There's no particular error, it just doesn't find a node to connect to.

I have several things that seem suspicious in the log, first one is a DNS problem (or something in connection with DNS (what can be the :53: after the router's IP address...)

Code:

2018-04-11 23:59:53.598 [INF] CMGR: DNS discovery failed on seed x49.dnsseed.bluematt.me: lookup x49.dnsseed.bluematt.me on 192.168.1.254:53: no such host
2018-04-11 23:59:54.097 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.sipa.be: lookup x49.seed.bitcoin.sipa.be on 192.168.1.254:53: no such host
2018-04-11 23:59:55.864 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.jonasschnelli.ch: lookup x49.seed.bitcoin.jonasschnelli.ch on 192.168.1.254:53: server misbehaving

I've searched the sourced for this :53: but found nothing, so it's interesting, what's that...

The log:

Code:

lnd –bitcoin.active –bitcoin.mainnet –debuglevel=debug –bitcoin.node=neutrino --noencryptwallet
2018-04-11 23:59:52.308 [INF] LTND: Version 0.4.0-beta commit=
2018-04-11 23:59:52.308 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2018-04-11 23:59:52.309 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0
2018-04-11 23:59:52.716 [INF] LTND: Primary chain is set to: bitcoin
2018-04-11 23:59:52.717 [INF] BTCN: Loaded 0 addresses from file '/home/pi/.lnd/data/chain/bitcoin/mainnet/peers.json'
2018-04-11 23:59:53.181 [INF] CMGR: 38 addresses found from DNS seed dnsseed.bitcoin.dashjr.org
2018-04-11 23:59:53.257 [INF] CMGR: 40 addresses found from DNS seed seed.bitnodes.io
2018-04-11 23:59:53.532 [INF] CMGR: 25 addresses found from DNS seed x49.seed.bitcoinstats.com
2018-04-11 23:59:53.598 [INF] CMGR: DNS discovery failed on seed x49.dnsseed.bluematt.me: lookup x49.dnsseed.bluematt.me on 192.168.1.254:53: no such host
2018-04-11 23:59:54.097 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.sipa.be: lookup x49.seed.bitcoin.sipa.be on 192.168.1.254:53: no such host
2018-04-11 23:59:55.864 [INF] CMGR: DNS discovery failed on seed x49.seed.bitcoin.jonasschnelli.ch: lookup x49.seed.bitcoin.jonasschnelli.ch on 192.168.1.254:53: server misbehaving
2018-04-11 23:59:58.231 [INF] BTCN: Disconnecting peer 51.15.139.246:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.232 [INF] BTCN: Lost peer 51.15.139.246:8333 (outbound)
2018-04-11 23:59:58.416 [INF] BTCN: Disconnecting peer 96.43.135.210:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.416 [INF] BTCN: Lost peer 96.43.135.210:8333 (outbound)
2018-04-11 23:59:58.513 [INF] BTCN: Disconnecting peer 89.163.146.185:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.514 [INF] BTCN: Lost peer 89.163.146.185:8333 (outbound)
2018-04-11 23:59:58.526 [INF] BTCN: Disconnecting peer 96.43.135.210:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.526 [INF] BTCN: Lost peer 96.43.135.210:8333 (outbound)
2018-04-11 23:59:58.625 [INF] BTCN: Disconnecting peer 49.64.216.82:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.625 [INF] BTCN: Lost peer 49.64.216.82:8333 (outbound)
2018-04-11 23:59:58.677 [INF] BTCN: Disconnecting peer 79.160.18.218:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.677 [INF] BTCN: Lost peer 79.160.18.218:8333 (outbound)
2018-04-11 23:59:58.759 [INF] BTCN: Disconnecting peer 185.101.93.105:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.759 [INF] BTCN: Lost peer 185.101.93.105:8333 (outbound)
2018-04-11 23:59:58.809 [INF] BTCN: Disconnecting peer [2002:43db:9616::43db:9616]:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.809 [INF] BTCN: Lost peer [2002:43db:9616::43db:9616]:8333 (outbound)
2018-04-11 23:59:58.860 [INF] BTCN: Disconnecting peer 176.9.42.4:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.860 [INF] BTCN: Lost peer 176.9.42.4:8333 (outbound)
2018-04-11 23:59:58.911 [INF] BTCN: Disconnecting peer [2a02:e00:fff0:1b9::a]:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:58.931 [INF] BTCN: Lost peer [2a02:e00:fff0:1b9::a]:8333 (outbound)
2018-04-11 23:59:58.931 [INF] LNWL: Opened wallet
2018-04-11 23:59:59.370 [INF] BTCN: Disconnecting peer 5.135.215.19:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:59.371 [INF] BTCN: Lost peer 5.135.215.19:8333 (outbound)
2018-04-11 23:59:59.576 [INF] BTCN: Disconnecting peer 39.72.4.56:8333 (outbound), cannot serve compact filters
2018-04-11 23:59:59.576 [INF] BTCN: Lost peer 39.72.4.56:8333 (outbound)
2018-04-12 00:00:00.038 [INF] BTCN: Disconnecting peer 103.82.56.24:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.039 [INF] BTCN: Lost peer 103.82.56.24:8333 (outbound)
2018-04-12 00:00:00.172 [INF] BTCN: Disconnecting peer 173.249.39.131:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.173 [INF] BTCN: Lost peer 173.249.39.131:8333 (outbound)
2018-04-12 00:00:00.254 [INF] BTCN: Disconnecting peer 43.229.76.49:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.255 [INF] BTCN: Lost peer 43.229.76.49:8333 (outbound)
2018-04-12 00:00:00.295 [INF] BTCN: Disconnecting peer 94.110.16.97:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.295 [INF] BTCN: Lost peer 94.110.16.97:8333 (outbound)
2018-04-12 00:00:00.375 [INF] BTCN: Disconnecting peer 78.227.49.100:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.376 [INF] BTCN: Lost peer 78.227.49.100:8333 (outbound)
2018-04-12 00:00:00.461 [INF] BTCN: Disconnecting peer 5.9.2.145:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.462 [INF] BTCN: Lost peer 5.9.2.145:8333 (outbound)
2018-04-12 00:00:00.732 [INF] BTCN: Disconnecting peer 27.217.15.63:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.732 [INF] BTCN: Lost peer 27.217.15.63:8333 (outbound)
2018-04-12 00:00:00.829 [INF] BTCN: Disconnecting peer 72.177.89.166:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:00.829 [INF] BTCN: Lost peer 72.177.89.166:8333 (outbound)
2018-04-12 00:00:01.281 [INF] BTCN: Disconnecting peer 103.45.236.44:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.282 [INF] BTCN: Lost peer 103.45.236.44:8333 (outbound)
2018-04-12 00:00:01.382 [INF] BTCN: Disconnecting peer 103.45.236.44:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.383 [INF] BTCN: Lost peer 103.45.236.44:8333 (outbound)
2018-04-12 00:00:01.497 [INF] BTCN: Disconnecting peer 88.202.180.233:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.497 [INF] BTCN: Lost peer 88.202.180.233:8333 (outbound)
2018-04-12 00:00:01.504 [INF] BTCN: Disconnecting peer 193.110.113.28:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.504 [INF] BTCN: Lost peer 193.110.113.28:8333 (outbound)
2018-04-12 00:00:01.725 [INF] BTCN: Disconnecting peer 95.163.71.126:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.725 [INF] BTCN: Lost peer 95.163.71.126:8333 (outbound)
2018-04-12 00:00:01.775 [INF] BTCN: Disconnecting peer 49.64.216.200:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.776 [INF] BTCN: Lost peer 49.64.216.200:8333 (outbound)
2018-04-12 00:00:01.792 [INF] BTCN: Disconnecting peer 35.184.79.142:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.793 [INF] BTCN: Lost peer 35.184.79.142:8333 (outbound)
2018-04-12 00:00:01.987 [INF] BTCN: Disconnecting peer 141.226.254.221:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:01.987 [INF] BTCN: Lost peer 141.226.254.221:8333 (outbound)
2018-04-12 00:00:02.094 [INF] BTCN: Disconnecting peer 54.37.84.178:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.094 [INF] BTCN: Lost peer 54.37.84.178:8333 (outbound)
2018-04-12 00:00:02.233 [INF] BTCN: Disconnecting peer 58.208.120.20:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.233 [INF] BTCN: Lost peer 58.208.120.20:8333 (outbound)
2018-04-12 00:00:02.234 [INF] BTCN: Disconnecting peer [2a02:27a8:0:1:acdc:77:0:9b]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.235 [INF] BTCN: Lost peer [2a02:27a8:0:1:acdc:77:0:9b]:8333 (outbound)
2018-04-12 00:00:02.330 [INF] BTCN: Disconnecting peer 46.4.65.10:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.330 [INF] BTCN: Lost peer 46.4.65.10:8333 (outbound)
2018-04-12 00:00:02.428 [INF] BTCN: Disconnecting peer [2403:9800:c048:a10:960c:6dff:fe80:61b]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.429 [INF] BTCN: Lost peer [2403:9800:c048:a10:960c:6dff:fe80:61b]:8333 (outbound)
2018-04-12 00:00:02.447 [INF] BTCN: Disconnecting peer [2001:638:a000:4140::ffff:191]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.447 [INF] BTCN: Lost peer [2001:638:a000:4140::ffff:191]:8333 (outbound)
2018-04-12 00:00:02.637 [INF] BTCN: Disconnecting peer [2604:67c0:2001::2]:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.637 [INF] BTCN: Lost peer [2604:67c0:2001::2]:8333 (outbound)
2018-04-12 00:00:02.729 [INF] BTCN: Disconnecting peer 98.7.64.249:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.729 [INF] BTCN: Lost peer 98.7.64.249:8333 (outbound)
2018-04-12 00:00:02.826 [INF] BTCN: Disconnecting peer 31.3.135.183:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:02.826 [INF] BTCN: Lost peer 31.3.135.183:8333 (outbound)
2018-04-12 00:00:03.310 [INF] BTCN: Disconnecting peer 114.219.7.100:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:03.311 [INF] BTCN: Lost peer 114.219.7.100:8333 (outbound)
2018-04-12 00:00:03.713 [INF] BTCN: Disconnecting peer 180.106.133.61:8333 (outbound), cannot serve compact filters
2018-04-12 00:00:03.713 [INF] BTCN: Lost peer 180.106.133.61:8333 (outbound)
2018-04-12 00:00:05.098 [INF] LNWL: The wallet has been unlocked without a time limit
2018-04-12 00:00:05.098 [INF] LTND: LightningWallet opened
2018-04-12 00:00:05.108 [INF] LNWL: Catching up block hashes to height 382320, this will take a while...
2018-04-12 00:00:05.124 [INF] LNWL: Done catching up block hashes
2018-04-12 00:00:05.127 [INF] HSWC: Restoring in-memory circuit state from disk
2018-04-12 00:00:05.127 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
2018-04-12 00:00:05.136 [INF] LNWL: Started rescan from block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f (height 0) for 0 addresses
2018-04-12 00:00:05.137 [INF] LNWL: Catching up block hashes to height 0, this might take a while
2018-04-12 00:00:05.155 [INF] LNWL: Done catching up block hashes
2018-04-12 00:00:05.155 [INF] LNWL: Finished rescan for 0 addresses (synced to block 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, height 0)
2018-04-12 00:00:05.159 [INF] RPCS: RPC server listening on 127.0.0.1:10009
2018-04-12 00:00:05.160 [INF] LTND: Waiting for chain backend to finish sync, start_height=0
2018-04-12 00:00:05.160 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080
2018-04-12 00:02:12.423 [INF] BTCN: Disconnecting peer 94.199.178.17:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.423 [INF] BTCN: Lost peer 94.199.178.17:8333 (outbound)
2018-04-12 00:02:12.479 [INF] BTCN: Disconnecting peer 82.136.99.98:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.480 [INF] BTCN: Lost peer 82.136.99.98:8333 (outbound)
2018-04-12 00:02:12.594 [INF] BTCN: Disconnecting peer 91.211.191.15:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.595 [INF] BTCN: Lost peer 91.211.191.15:8333 (outbound)
2018-04-12 00:02:12.995 [INF] BTCN: Disconnecting peer [2002:674a:7892::674a:7892]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:12.996 [INF] BTCN: Lost peer [2002:674a:7892::674a:7892]:8333 (outbound)
2018-04-12 00:02:17.629 [INF] BTCN: Disconnecting peer 212.51.14.72:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.630 [INF] BTCN: Lost peer 212.51.14.72:8333 (outbound)
2018-04-12 00:02:17.694 [INF] BTCN: Disconnecting peer 185.181.176.246:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.695 [INF] BTCN: Lost peer 185.181.176.246:8333 (outbound)
2018-04-12 00:02:17.879 [INF] BTCN: Disconnecting peer 208.93.231.240:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.879 [INF] BTCN: Lost peer 208.93.231.240:8333 (outbound)
2018-04-12 00:02:17.967 [INF] BTCN: Disconnecting peer 78.46.221.56:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:17.968 [INF] BTCN: Lost peer 78.46.221.56:8333 (outbound)
2018-04-12 00:02:18.208 [INF] BTCN: Disconnecting peer 58.56.252.254:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.209 [INF] BTCN: Lost peer 58.56.252.254:8333 (outbound)
2018-04-12 00:02:18.393 [INF] BTCN: Disconnecting peer 46.188.55.31:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.393 [INF] BTCN: Lost peer 46.188.55.31:8333 (outbound)
2018-04-12 00:02:18.554 [INF] BTCN: Disconnecting peer [2001:41f0:0:4:62:6974:636f:696e]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.555 [INF] BTCN: Lost peer [2001:41f0:0:4:62:6974:636f:696e]:8333 (outbound)
2018-04-12 00:02:18.996 [INF] BTCN: Disconnecting peer [2002:45ac:57a7::45ac:57a7]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:18.996 [INF] BTCN: Lost peer [2002:45ac:57a7::45ac:57a7]:8333 (outbound)
2018-04-12 00:02:19.023 [INF] BTCN: Disconnecting peer 101.180.234.134:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.023 [INF] BTCN: Lost peer 101.180.234.134:8333 (outbound)
2018-04-12 00:02:19.111 [INF] BTCN: Disconnecting peer 94.242.232.92:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.111 [INF] BTCN: Lost peer 94.242.232.92:8333 (outbound)
2018-04-12 00:02:19.592 [INF] BTCN: Disconnecting peer 180.107.22.33:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.593 [INF] BTCN: Lost peer 180.107.22.33:8333 (outbound)
2018-04-12 00:02:19.735 [INF] BTCN: Disconnecting peer 217.73.91.118:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:19.735 [INF] BTCN: Lost peer 217.73.91.118:8333 (outbound)
2018-04-12 00:02:20.088 [INF] BTCN: Disconnecting peer 32.209.17.99:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:20.089 [INF] BTCN: Lost peer 32.209.17.99:8333 (outbound)
2018-04-12 00:02:20.220 [INF] BTCN: Disconnecting peer [2a00:1a48:7810:101:be76:4eff:fe08:c774]:8333 (outbound), cannot serve compact filters
2018-04-12 00:02:20.220 [INF] BTCN: Lost peer [2a00:1a48:7810:101:be76:4eff:fe08:c774]:8333 (outbound)
^C

delpiero10

full member

Activity: 270

Merit: 101

Quote

My problem is that my lnd neutrino node can't find any node to connect to, so I'm still struggling with it, but somehow sometime I'll get it working...

Can you upload log file? Is there any error?

bitart

hero member

Activity: 1442

Merit: 629

Vires in Numeris

So, lnd has been updated again, it's 0.4.1 now, so I thought why not to update on the PI too...
I'm writing this post because the update was not as easy as 1-2-3 (OK, maybe just for me, but anyway)
So I've logged in to the PI, and changed the working directory to the lnd source:

Code:

cd $GOPATH/src/github.com/lightningnetwork/lnd

After, I've started the update with a git pull command, but got this error message:

Code:

pi@Lightning1:~/projects/src/github.com/lightningnetwork/lnd $ git pull remote: Counting objects: 4, done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0
Unpacking objects: 100% (4/4), done.
From https://github.com/lightningnetwork/lnd
12cb35a6..bc029b9c master -> origin/master
Updating a0fe4fb7..bc029b9c
error: Your local changes to the following files would be overwritten by merge:
Gopkg.lock
config.go
Please commit your changes or stash them before you merge.
Aborting

So something has been changed locally, but I don't need those changes (I guess), so I was about to discard those changes and let the pull sync my local copy of the lnd code, but I had no clue what to do (this is my first time I've used git, so pardon me)
After heavy googling, I've found the solution here: https://techsparx.com/software-development/git/reset-local-changes.html
So I have used this:

Code:

git reset --hard

After, the

Code:

git pull

was OK, it run without any error.

My problem is that my lnd neutrino node can't find any node to connect to, so I'm still struggling with it, but somehow sometime I'll get it working...

GameBitCEO

newbie

Activity: 19

Merit: 0

Really interested in that topic. Thanks for your replies

Topic: Running bitcoin node with LN hub on a Raspberry Pi 3 (Read 835 times)