Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: bitart on February 16, 2018, 07:32:05 PM


Title: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on February 16, 2018, 07:32:05 PM
Hi experts,
I don't know if this is the right place to ask, but I'd like to start to play with Lightning network, but want to start small.
I've found this https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md (https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md) on github, and I've made my first step, I've ordered the Raspberry Pi 3B.
I've found some threads about Raspberry Pi but it's usually about running some nodes (bitcoin, other alts) on PI but not about LN.
Do you have any experience with the LN node on the PI?
I'm not afraid of linux or anything, just wanted to ask in advance before the PI arrives, what to download, where to search for some info (I can use google, but this is something specific.)
Thanks in advance!

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: nitrousteam on February 16, 2018, 11:13:01 PM
Credit for tutorial goes to Stadicus:

https://medium.com/@stadicus/noobs-guide-to-%EF%B8%8F-lightning%EF%B8%8F-on-a-raspberry-pi-f0ab7525586e

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on February 17, 2018, 08:27:44 AM
Quote from: nitrousteam on February 16, 2018, 11:13:01 PM
Credit for tutorial goes to Stadicus:

https://medium.com/@stadicus/noobs-guide-to-%EF%B8%8F-lightning%EF%B8%8F-on-a-raspberry-pi-f0ab7525586e
Thanks, I haven't found this one yet.
I have read it thru quickly, it uses the eclair version of lightning hub, the one I put it into the OP was referring to lnd which is a different build, according to my understanding, they are totally different.
I'll search for the differences, surely there's somewhere a comparison about the different LN nodes (there's 3 kind of LN nodes as I saw somewhere).

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on February 23, 2018, 09:40:48 PM
Status update:
I've received the Raspberry PI, I've managed to set it up, so it's working, but there's nothing installed yet in connection with bitcoin. I've used this install guide, it was really straightforward and was easy to follow.
https://medium.com/@stadicus/noobs-guide-to-️-lightning️-on-a-raspberry-pi-f0ab7525586e (https://medium.com/@stadicus/noobs-guide-to-️-lightning️-on-a-raspberry-pi-f0ab7525586e)
What I'm reading now is a so called neutrino light client which is not a full node but something like a pruned one without the full blockchain, it connects to other nodes to gather the necessary information about blockchain. If I use this, the 16Gb SD card in the Raspberry PI will be enough to run a bitcoin node with LN hub installed. (I understand that running a full node will be necessary in the future, but now I would like to test only, so it's enough for that purpose.)

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on February 24, 2018, 09:21:15 PM
Next status update:
I've just managed to set up the Raspberry PI 3 with a working minimal OS, but nothing installed which is connected with bitcoin.
Now I've decided to run a neutrino lightweight node to let the lnd connect to it because it doesn't require a full node running locally.
So I was about to install the lnd on the raspberry but failed with the GO language, which is a must to have lnd installed.
I was following this guide:
https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md (https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md)
When I started to intall GO:
Code:
sudo apt-get install golang-1.10-go
I had an error message:
Code:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package golang-1.10-go
E: Couldn't find any package by glob 'golang-1.10-go'
E: Couldn't find any package by regex 'golang-1.10-go'
So I read a bit, and found that for the raspberry linux, we only have go 1.8 available, which is OK for lnd, because 1.8 is the minimal required version of GO.
So I was about to install the 1.8 GO but no success:
Code:
sudo apt-get install golang-1.8-go
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package golang-1.8-go is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'golang-1.8-go' has no installation candidate
So now I'm searching for a workaround to be able to install GO on the raspberry to be able to continue the installation of lnd...


Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bob123 on February 25, 2018, 01:46:35 PM
Quote from: bitart on February 24, 2018, 09:21:15 PM
Code:
sudo apt-get install golang-1.10-go
I had an error message:
Code:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package golang-1.10-go
E: Couldn't find any package by glob 'golang-1.10-go'
E: Couldn't find any package by regex 'golang-1.10-go'
So I read a bit, and found that for the raspberry linux, we only have go 1.8 available, which is OK for lnd, because 1.8 is the minimal required version of GO.
So I was about to install the 1.8 GO but no success:
Code:
sudo apt-get install golang-1.8-go
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package golang-1.8-go is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'golang-1.8-go' has no installation candidate


You might try to add this repository and install 1.8 or 1.9:

Code:
$ sudo add-apt-repository ppa:gophers/archive
$ sudo apt-get update
$ sudo apt-get install golang-1.9-go

If apt-get won't find your desired version you might consider downloading it directly from https://golang.org/dl/ (https://golang.org/dl/)

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on February 25, 2018, 02:22:19 PM
Thanks bob123, the direct download worked at the end:

So I've just managed to install the necessary GO languange on the Raspberry PI, using these guides (had to combine them to get it to work, but at last it works...)
https://tecadmin.net/install-go-on-debian/#
https://stackoverflow.com/questions/48348262/install-go-golang-on-raspbian

To make it easier for you, here are the steps:
1)
Code:
sudo apt-get update
sudo apt-get -y upgrade
2)
Code:
wget https://dl.google.com/go/go1.10.linux-armv6l.tar.gz

make sure you download the arm version for the Raspberry

3)
install an old version of GO

Code:
sudo apt-get install golang

this will install the 1.7 version, which is not good for us yet

4)
Uncompress the previously downloaded 1.10 version into your (pi) home directory

Code:
sudo tar -C /home/pi -xzf go1.10.linux-armv6l.tar.gz

5)
remove the old golang installation

Code:
sudo apt remove golang

remove the other unnecessary stuff after removing the old golang

Code:
sudo apt-get autoremove

6)
edit your .profile
insert these lines to let the system found your go language installation

Code:
export GOROOT=/home/pi/go
export GOPATH=$HOME/projects
export PATH=$GOPATH/bin:$GOROOT/bin:$PATH

7)
log out and log in again
check the version and the environment of your installed GO, should look like this:

Code:
go version
go version go1.10 linux/arm

Code:
go env
GOARCH="arm"
GOBIN=""
GOCACHE="/home/pi/.cache/go-build"
GOEXE=""
GOHOSTARCH="arm"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/pi/projects"
GORACE=""
GOROOT="/home/pi/go"
GOTMPDIR=""
GOTOOLDIR="/home/pi/go/pkg/tool/linux_arm"
GCCGO="gccgo"
GOARM="6"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -marm -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-b                                                                                                 uild470418061=/tmp/go-build -gno-record-gcc-switches"

That's all :)

Now moving towards to lnd installation...

Just another tip:
If you're on a fresh installation of Raspbian, you won't have the 'git' to use the golang's built-in downloader part, to be able to install Glide, which is also necessary.
So to get this command working:

Code:
go get -u github.com/Masterminds/glide

you will need this:

Code:
sudo apt-get install git

After this, you can start downloading Glide with the above mentioned command
When it's done, you'll find Glide in the GOPATH/bin

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on March 04, 2018, 11:03:13 PM
Briefing the last steps I've just managed to take:
using this website:
http://dev.lightning.community/guides/installation/ (http://dev.lightning.community/guides/installation/)
I've managed to install lnd and btcd (roasbeef's edition)
Installing lnd:
Using the few commands on the website, the lnd installation was successfull (be aware that the testing of the installation took ~30 minutes, just take this into consideration if you're in a hurry while installing)
Installing btcd
It was also really simple, using the command on the above mentioned websites.

Next steps:
Starting the installed things, especially figuring out how to create a wallet on the PI, stay tuned :)

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on March 17, 2018, 12:45:18 PM
The Lightning network has moved to beta, so now it's possible to officially do testing on the mainnet. Until now, most of the mainnet testing was done without support from the developers, I hope that from now on the support will help the testers.
In connection with the thread, we need to upgrade the lnd because the changes compared to the previous version are not backward compatible because of the new beta version.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: nicosey on March 17, 2018, 08:46:00 PM
Does it have to be a full node?

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on March 18, 2018, 12:28:39 AM
Quote from: nicosey on March 17, 2018, 08:46:00 PM
Does it have to be a full node?
No, my idea is to have a so called neutrino version of the lnd. This means that it only takes 200-300 MegaBytes, because it's a kind of pruned node, so it doesn't download and keep the whole blockchain on site (and does not use 200-400 GigaBytes like a full node) but it connects to some full nodes on the network.
For testing purposes, it's fine for me, if I'll take it more seriously in the future, I just attach a USB external drive with a 500Gb HDD and it can act as a full node with the full blockchain on the HDD.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on March 18, 2018, 12:17:01 PM
Quote from: bitart on March 18, 2018, 12:28:39 AM
Quote from: nicosey on March 17, 2018, 08:46:00 PM
Does it have to be a full node?
No, my idea is to have a so called neutrino version of the lnd. This means that it only takes 200-300 MegaBytes, because it's a kind of pruned node, so it doesn't download and keep the whole blockchain on site (and does not use 200-400 GigaBytes like a full node) but it connects to some full nodes on the network.
For testing purposes, it's fine for me, if I'll take it more seriously in the future, I just attach a USB external drive with a 500Gb HDD and it can act as a full node with the full blockchain on the HDD.


I'm running lightningd instead of lnd but my configuration is very similar: rasperry pi 3 + external HDD for full blockchain. Everything works fine so far.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: Rath_ on March 18, 2018, 05:46:28 PM
Quote from: delpiero10 on March 18, 2018, 12:17:01 PM
I'm running lightningd instead of lnd but my configuration is very similar: rasperry pi 3 + external HDD for full blockchain. Everything works fine so far.

Could you tell me what is the CPU and RAM usage when everything you need to run a full node is turned on? Can you still use the device for browsing the Internet while everything is running in the background? I was thinking of buying the latest Raspberry Pi 3B+ but I would to know more before doing so. I don't really need a full node since I use a hardware wallet but I would like to support Bitcoin network and try running a Lightning Network node on the mainnet.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on March 18, 2018, 06:15:47 PM
Quote from: BitCryptex on March 18, 2018, 05:46:28 PM
Quote from: delpiero10 on March 18, 2018, 12:17:01 PM
I'm running lightningd instead of lnd but my configuration is very similar: rasperry pi 3 + external HDD for full blockchain. Everything works fine so far.

Could you tell me what is the CPU and RAM usage when everything you need to run a full node is turned on? Can you still use the device for browsing the Internet while everything is running in the background? I was thinking of buying the latest Raspberry Pi 3B+ but I would to know more before doing so. I don't really need a full node since I use a hardware wallet but I would like to support Bitcoin network and try running a Lightning Network node on the mainnet.

https://i.imgur.com/jvJJ4If.png

I'm running my raspberry in CLI mode and using it only as btc/ln node so I didn't try to browse the internet.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on March 30, 2018, 08:31:15 PM
Because of the new beta version of LND, I've deleted the previously installed LND and BTCD from the PI and started from scratch. I would like to start a neutrino version of the LND, so according to my current understanding, BTCD is not necessary at all, but I'm not 100% sure yet. This can change in the future as I move forward with testing this thing.

Hint: if you want to start to risk your coins on the main net, you should modify the config.go file in the src directory:
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
		}
If you comment these lines out (you put // at the beginning of the line) you won't have an error message  (and won't stop you) when you want to start your lnd client in neutrino mode on the mainnet.

After saving the config.go file, I have installed the new LND again (the process is the same as above, it just installs the new version).

Now I'm having issues with starting the LND, if I manage to start it (asking for wallet password), I'll post it here.
Code:
2018-03-30 22:16:18.654 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create wallet, or `lncli unlock` to unlock already created wallet.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on March 31, 2018, 05:01:19 AM
Quote from: bitart on March 30, 2018, 08:31:15 PM
Because of the new beta version of LND, I've deleted the previously installed LND and BTCD from the PI and started from scratch. I would like to start a neutrino version of the LND, so according to my current understanding, BTCD is not necessary at all, but I'm not 100% sure yet. This can change in the future as I move forward with testing this thing.

Hint: if you want to start to risk your coins on the main net, you should modify the config.go file in the src directory:
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
		}
If you comment these lines out (you put // at the beginning of the line) you won't have an error message  (and won't stop you) when you want to start your lnd client in neutrino mode on the mainnet.

After saving the config.go file, I have installed the new LND again (the process is the same as above, it just installs the new version).

Now I'm having issues with starting the LND, if I manage to start it (asking for wallet password), I'll post it here.
Code:
2018-03-30 22:16:18.654 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create wallet, or `lncli unlock` to unlock already created wallet.

did you run lncli create/unlock without errors?

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on March 31, 2018, 08:07:30 AM
Quote from: delpiero10 on March 31, 2018, 05:01:19 AM
Quote from: bitart on March 30, 2018, 08:31:15 PM
...
Now I'm having issues with starting the LND, if I manage to start it (asking for wallet password), I'll post it here.
Code:
2018-03-30 22:16:18.654 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create wallet, or `lncli unlock` to unlock already created wallet.

did you run lncli create/unlock without errors?
No, it gave me some error, but I've managed to skip this with using the --noencryptwallet flag when starting lnd. It opens the wallet and lnd continues to start. (This leaves the wallet.dat unencrypted, but for testing purposes for the first start it's fine for me.)
Now I'm waiting for lnd to find some proper nodes, but it's struggling to find any. Maybe it's because of the beta upgrade, nodes needs to upgrade before they will be able to serve neutrino type nodes, so I'm trying to start it periodically, and also checking github, e.g.:
https://github.com/lightninglabs/lightning-app/issues/26 (https://github.com/lightninglabs/lightning-app/issues/26)

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: GameBitCEO on April 01, 2018, 10:17:33 PM
Really interested in that topic. Thanks for your replies

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on April 11, 2018, 10:11:10 PM
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 (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...


Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on April 12, 2018, 05: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?

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on April 12, 2018, 05:40:57 PM
Quote from: delpiero10 on April 12, 2018, 05: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

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on April 12, 2018, 08: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
		}

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on April 12, 2018, 09:07:19 PM
Quote from: delpiero10 on April 12, 2018, 08: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...

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on May 02, 2018, 08:04:24 PM
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...

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: vlom on May 02, 2018, 08: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...  :P

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?

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on May 02, 2018, 08:39:17 PM
Quote from: vlom on May 02, 2018, 08: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...  :P
Thanks :) Of course, all of them :P

Quote from: vlom on May 02, 2018, 08: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.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on May 11, 2018, 08:49:47 PM
Quote from: vlom on May 02, 2018, 08: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...  :P

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.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on August 02, 2018, 05: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...

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: Rath_ on August 02, 2018, 05:53:42 PM
Quote from: bitart on August 02, 2018, 05: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 (https://github.com/rootzoll/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 (https://bitcointalk.org/index.php?topic=4792622.msg43243696#post_point2).

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on August 03, 2018, 07:45:02 PM
Quote from: BitCryptex on August 02, 2018, 05:53:42 PM
Quote from: bitart on August 02, 2018, 05: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 (https://github.com/rootzoll/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 (https://bitcointalk.org/index.php?topic=4792622.msg43243696#post_point2).
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 :)

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: TheBeardedBaby on October 01, 2018, 11:48:06 AM
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.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: lightningslotmachine on October 01, 2018, 12:03:57 PM
I used this tutorial to setup bitcoin + lightning

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

Very easy to follow.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: TheBeardedBaby on October 01, 2018, 12:33:59 PM
Quote from: lightningslotmachine on October 01, 2018, 12:03:57 PM
I used this tutorial to setup bitcoin + lightning

https://github.com/Stadicus/guides/blob/master/raspibolt/README.md (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.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: lightningslotmachine on October 01, 2018, 02:00:26 PM
Quote from: iasenko on October 01, 2018, 12:33:59 PM
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.

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: delpiero10 on October 01, 2018, 06:29:46 PM
Quote from: iasenko on October 01, 2018, 12:33:59 PM
how are the temperatures btw?

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

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: bitart on October 01, 2018, 10:27:51 PM
Quote from: iasenko on October 01, 2018, 12:33:59 PM
Quote from: lightningslotmachine on October 01, 2018, 12:03:57 PM
I used this tutorial to setup bitcoin + lightning

https://github.com/Stadicus/guides/blob/master/raspibolt/README.md (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 (http://www.banggood.com/Raspberry-Pi-23-Copper-Heat-Sink-Heatsink-With-3M-Special-Thermal-Cooling-Paste-p-1045808.html), 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

Title: Re: Running bitcoin node with LN hub on a Raspberry Pi 3
Post by: TheBeardedBaby on October 02, 2018, 08:07:49 AM
Quote from: bitart on October 01, 2018, 10: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 (http://www.banggood.com/Raspberry-Pi-23-Copper-Heat-Sink-Heatsink-With-3M-Special-Thermal-Cooling-Paste-p-1045808.html?p=OS11181479072201504Z), 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.
https://ae01.alicdn.com/kf/HTB1DxA7Kf9TBuNjy0Fcq6zeiFXa6/Raspberry-Pi-2-5-SATA-HDD-SSD-Storage-Expansion-Board-X820-V3-0-USB-3-0.jpg_640x640.jpg


Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines