BitShares Forum
Main => General Discussion => Topic started by: maqifrnswa on June 29, 2015, 03:14:02 pm
-
Summary: Raspberry Pi (RPI) and other single-board-computers (SBCs) could be good platforms for distributed, low-power, low-cost witness nodes in BitShares2.0. A convenient way of getting BiShares2.0 on RPIs, especially for those just learning RPI or BitShares, will aid adoption and help the network. This project is looking at ways to simplify access to BitShares2.0 through RPI disk images and repositories.
For CubieBox and archlinux, see https://bitsharestalk.org/index.php/topic,17297.msg220456.html#msg220456
Three ways to get it:
1) Download our Raspbian Jessie minimal server preconfigured for graphene and will update graphene when you run "apt-get update && apt-get upgrade":
https://www.dropbox.com/s/qzeeqnhbngoqo99/20150814_bitshares_raspbian.zip?dl=0
$ md5sum 20150814_bitshares_raspbian.zip
9bad200938d32531f5f0c341e5ea482e 20150814_bitshares_raspbian.zipSee "SD card image based on Raspbian Jessie is available for initial testing" below.
OR
2) Download a Raspbian Jessie distribution (such as http://sirlagz.net/2013/07/19/raspbian-server-edition-2-5/) then follow the instructions for "Rapsbian Jessie PPA" below.
OR
3) Upgrade your Raspbian Wheezy to Jessie and then follow the instructions for "Rapsbian Jessie PPA" below:
a) Download and install Raspbian (https://www.raspberrypi.org/documentation/installation/installing-images/README.md)
b) Make sure you're up to date
apt-get update
apt-get upgradec) Optionally remove packages you don't need to speed up the upgrade (e.g., if you're a server and don't care about -dev packages)
apt-get remove --auto-remove --purge libx11-.* .*-devd) Upgrade to Jessie
sed -i 's/wheezy/jessie/g' /etc/apt/sources.list
find /etc/apt/sources.list.d -type f -exec sed -i -e 's/wheezy/jessie/g' {} \;
apt-get update
apt-get dist-upgrade -o Dpkg::Options::="--force-confold"e) Follow the steps for "Rapsbian Jessie PPA" below
OR
Undocumented, untested 4th way: apt-pin so that you can install packages from Jessie if they are missing from wheezy.
Rapsbian Jessie PPA:
As super user or root, grab the archive key and add the repository
sudo wget -O - http://people.debian.org/~showard/raspbian/bitshares_repo.gpg.key | sudo apt-key add -
sudo sh -c 'echo "deb http://people.debian.org/~showard/raspbian/ jessie main bitshares\ndeb-src http://people.debian.org/~showard/raspbian/ jessie main bitshares" > /etc/apt/sources.list.d/bitshares.list'
Install graphene
apt-get update
apt-get install graphene
4) you now have two new binaries to use, "witness_node" and "cli_wallet"
SD card image based on Raspbian Jessie is available for initial testing.
disk image resize doesn't work, but you still have 500 MB to work with for testing
Please test the image and be a pioneer!
What you need:
- a RPI or RPI2
- an SD card > 2.2 GB
- a connection to the internet for the RPI
- another computer on your network to log in to the RPI, or a monitor and keyboard to log in to the RPI
Step one:
Download the image from the link at the top of the post
Step two:
Follow the instructions on how to install the downloaded image on an SD card. Depending on your OS, you can find instructions here:
https://www.raspberrypi.org/documentation/installation/installing-images/README.md
Step three:
a) ADVANCED: Plug in your RPI to your network and plug in to power. If you know how to do SSH already, and know how to find the RPI's IP address, you can just log in with the user name "pi" and "raspberry" as the password. Go to step four.
b) BEGINNER: Plug in a a keyboard and monitor to the RPI. Plug in your RPI to your network, then plug in to power.
Login with the following information when prompted:
Username: pi
Password: raspberry
then type ifconfig in to the terminal
write down the INET address of eth0, should look like:
inet addr:192.168.1.2 or something like that.
you can type "exit" to return to the log in screen. You don't need the keyboard or mouse any more.
Step four:
Log in to the RPI using another computer on your network:
linux/macosx (use the inet address from above)
ssh pi@192.168.1.2windows (use the inet address from above)
https://www.raspberrypi.org/documentation/remote-access/ssh/windows.md
Step five:
Change your password:
ADVANCED: https://www.raspberrypi.org/documentation/linux/usage/users.md
BEGINNER:
1) type "sudo rasp-config" in to the terminal
2) choose "Change User Password" and follow the prompts
Step six (might not work at the moment, and is optional):
Expand your disk so you can use the whole thing:
1) type "sudo rasp-config" in to the terminal
2) choose "Expand Filesystem" and follow the prompts
step seven:
Check out bitshares.
To make sure you're running the latest graphene:
apt-get update
apt-get upgrade[/quote]
"witness_node" and "cli_wallet" are both in the PATH - so just type those commands and it will work
See https://github.com/cryptonomex/graphene
on how to use them for now
step eight:
update with "apt-get update" then "apt-get upgrade". If I put a new version online, it will pull in the new version without having to get a new image
-
+5% thanks a lot! time to order a pi :)
-
Great project and thanks for the time and effort.
I will seed your torrent 24/7 (http://24s.it)
-
just curious , is it possible to install the current BTS wallet or PLAY wallet to a PI ?
-
bts/0.9.2 git clone will not build without modification as it still has the salsa error
libraries/fc/CMakeFiles/fc.dir/build.make:1871: recipe for target 'libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o' failed
make[2]: *** [libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o] Error 1
CMakeFiles/Makefile2:263: recipe for target 'libraries/fc/CMakeFiles/fc.dir/all' failed
make[1]: *** [libraries/fc/CMakeFiles/fc.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
trying PLAY now
-
bts/0.9.2 git clone will not build without modification as it still has the salsa error
libraries/fc/CMakeFiles/fc.dir/build.make:1871: recipe for target 'libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o' failed
make[2]: *** [libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o] Error 1
CMakeFiles/Makefile2:263: recipe for target 'libraries/fc/CMakeFiles/fc.dir/all' failed
make[1]: *** [libraries/fc/CMakeFiles/fc.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
trying PLAY now
PLAY has the same error
-
bts/0.9.2 git clone will not build without modification as it still has the salsa error
libraries/fc/CMakeFiles/fc.dir/build.make:1871: recipe for target 'libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o' failed
make[2]: *** [libraries/fc/CMakeFiles/fc.dir/vendor/salsa20/salsa20.s.o] Error 1
CMakeFiles/Makefile2:263: recipe for target 'libraries/fc/CMakeFiles/fc.dir/all' failed
make[1]: *** [libraries/fc/CMakeFiles/fc.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
trying PLAY now
PLAY has the same error
Seems solved by commenting all the salsa related lines in libraries/fc/CMakeLists.txt
I also want to mention that I have to use export LC_ALL="en_GB.UTF-8" instead of en_US as I don't have locale en_US preinstalled on my raspbian.
I think you can just comment out:
#SET(SALSA_SRC vendor/salsa20/salsa20.s)and it will work. It's already checking if it is not apple, it should also check if it is not x86 or x86_64
-
Graphene built and running on archlinuxarm cubox
Build comands ;)
#Graphene archlinuxarm cubox
#root
su
pacman -S git base-devel cmake gcc boost make automake doxygen
exit #root terminal
#as user
git clone https://github.com/cryptonomex/graphene.git
cd graphene
git submodule update --init --recursive
make clean
#cmake -DCMAKE_BUILD_TYPE=Debug .
cmake .
make
strip ./programs/witness_node/witness_node
strip ./programs/cli_wallet/cli_wallet
./programs/witness_node/witness_node
#start then stop to edit
#[ctrl+C]
nano witness_node_data_dir/config.ini
'
rpc-endpoint = 127.0.0.1:8090
'
./programs/witness_node/witness_node
#separate terminal window
./programs/cli_wallet/cli_wallet
-
just curious , is it possible to install the current BTS wallet or PLAY wallet to a PI ?
I think they can build, but running may take up too much memory for it to be useful, I think...
RPI1 has 256 or 512 MB of RAM
RPI2 has 1GB of RAM
With some swap, the RPI2 could be viable - I think bitshares/0.9.2 takes 1.25-1.50 GB in "normal" operation, and can take significantly more while scanning for transactions/reindexing
-
just curious , is it possible to install the current BTS wallet or PLAY wallet to a PI ?
I think they can build, but running may take up too much memory for it to be useful, I think...
RPI1 has 256 or 512 MB of RAM
RPI2 has 1GB of RAM
With some swap, the RPI2 could be viable - I think bitshares/0.9.2 takes 1.25-1.50 GB in "normal" operation, and can take significantly more while scanning for transactions/reindexing
current BTS wallet and PLAY built and syncing with my chain server now
-
Newest build:
https://www.dropbox.com/s/2hkmy3quvpmxoep/20150705_bitshares_raspbian.zip?dl=0
$ md5sum 20150705_bitshares_raspbian.zip
6e32f1570c5b3d8055e2ee2216e274b6 20150705_bitshares_raspbian.zip
Fixes a bug in fc so cli_wallet works on ARM processors, updated graphene code base
https://github.com/cryptonomex/graphene/issues/107
-
https://www.kickstarter.com/projects/2073955313/pidrive-low-power-msata-ssd-for-the-raspberry-pi could be a huge boost for the project
-
I have sent this thread to Faddat at the open source hardware project. Their first project looks like it is Klouds.io, but they can get things made for a better deal than most places.
-
I have sent this thread to Faddat at the open source hardware project. Their first project looks like it is Klouds.io, but they can get things made for a better deal than most places.
could elaborate? do they offer ready to use hardware?
-
When I try to extract the IMG file prior to imaging to an SD card, it says its 734 PB?
Anybody know what I'm doing wrong? Thanks!
-
Will there be a version for PI version of windows 10?
-
Still can't extract the .img file to write to SD card because it says its 734 PB.
-
Still can't extract the .img file to write to SD card because it says its 734 PB.
wierd, sorry about that... something up with partitions maybe? What OS are you using (and steps to decompress?)
I have another image to put up soon too, busy at work so I might not get to it for a few days.
As of now I'm not able to do a windows 10 PI image, but if someone is willing to please go ahead. Since the goal is simplicity and security, sticking with a minimal linux server is what i'm most comfortable with.
EDIT: also a big deal: windows 10 costs money, linux is free
-
Still can't extract the .img file to write to SD card because it says its 734 PB.
wierd, sorry about that... something up with partitions maybe? What OS are you using (and steps to decompress?)
I have another image to put up soon too, busy at work so I might not get to it for a few days.
As of now I'm not able to do a windows 10 PI image, but if someone is willing to please go ahead. Since the goal is simplicity and security, sticking with a minimal linux server is what i'm most comfortable with.
Using Zipeg on OSX and it looks like it's extracting to about 5GB. Should be good to go. Thanks again!
-
Up and running on the RPI 2. Now just have to work through the Github instructions. This is my first exposure to Linux.
-
Up and running on the RPI 2. Now just have to work through the Github instructions. This is my first exposure to Linux.
Awesome! Working executables are already in your home directory. If you want to update:
cd bitshares/graphene
git pull
git submodule update --init --recursive
cd build
make witness_node cli_wallet
updated executables will be in /home/pi/bitshares/graphene/build/programs/wallet_node and /home/pi/bitshares/graphene/programs/cli_wallet
Warning, compiling on RPi is VERY slow, that's why I'm putting out disk images and a repository. (also, it requires a newer version of boost, which is also in your home directory - so it gets complicated). You also can wait for packages so that all you would do is "apt-get install graphene" and it will take care of everything automatically.
-
Awesome man thanks!
-
witness node is chugging along...can I do anything with it that is helpful or useful for development?
https://www.dropbox.com/s/l0ktdlwxddfe3tf/2015-07-28%2015.29.46.jpg?dl=0
I'm going to dig into the command line wallet and one of the dummy accounts tonight after work.
-
witness node is chugging along...can I do anything with it that is helpful or useful for development?
If you know about C++ you can write unit-tests and/or documentation and publish a pull request
I'm going to dig into the command line wallet and one of the dummy accounts tonight after work.
If you want to give the webwallet a try you should "install" graphene-ui (different repo)
and of course you can also help out there ...
-
1) Get Raspbian Jessie. (e.g. http://sirlagz.net/2013/07/19/raspbian-server-edition-2-5/ or the version I already shared). Advanced users can apt-pin and make a mixed jessie/wheezy system. I might add more instructions later.
2) As super user or root, grab the archive key and add the repository
wget -O - http://people.debian.org/~showard/raspbian/bitshares_repo.gpg.key | sudo apt-key add -
echo -e "deb http://people.debian.org/~showard/raspbian/ jessie main bitshares\ndeb-src http://people.debian.org/~showard/raspbian/ jessie main bitshares" > /etc/apt/sources.list.d/bitshares/list
3) Install graphene
apt-get update
apt-get install graphene
4) you now have two new binaries to use, "witness_node" and "cli_wallet"
5) You will have updates pushed to you (via apt-get upgrade) periodically without needing to install a new image
EDIT: New image uploaded as well! see first post
-
Could we collaborate and start a mini graphene arm test net in this thread (or a new thread)?
I have been trying to start a test net with lafona using the CLI Wallet Cookbook but I think we are on different chains.
Lets see if these little computers can keep up with MasterCard :P
-
Could we collaborate and start a mini graphene arm test net in this thread (or a new thread)?
I have been trying to start a test net with lafona using the CLI Wallet Cookbook but I think we are on different chains.
Lets see if these little computers can keep up with MasterCard :P
I have the basic witness node running, but I'm at the point where I need to follow the instructions Xeroc posted the other day for a Witness in 2.0 that processes and signs blocks...I don't have the technical understanding at the command line level to do it on my own with confidence. If someone doesn't mind holding my hand a little, I definitely have some time I can contribute to this though, and would definitely like to learn.
-
I have the basic witness node running with the 10 defaunt witnesses.
But when I add another after the 10 min 'next_maintenance_time' and restart - it does not recognise the new witness
GRAPHENE_DEFAULT_MAINTENANCE_INTERVAL in libraries/chain/include/graphene/chain/config.hpp to, say, 10 minutes.
Also --seed-node to connect another computer - it ends up on a different chain
I have been using:
https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook (https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook)
https://bitshares.org/blog/2015/08/04/howto-become-a-witness/#bitshares-20-network-or-graphene-testnet (https://bitshares.org/blog/2015/08/04/howto-become-a-witness/#bitshares-20-network-or-graphene-testnet)
I know a little knowledge can be dangerous but its only a test net so who has the know-how to coordinate this?
-
I have the basic witness node running with the 10 defaunt witnesses.
But when I add another after the 10 min 'next_maintenance_time' and restart - it does not recognise the new witness
you need to
a) add the private key and
b) the witness-id to the configutration
c) upvote your own delegate and
d) wait for the maintenance interval
what's your witness node saying? does it load the key? is the new witness id appearing somewhere?
GRAPHENE_DEFAULT_MAINTENANCE_INTERVAL in libraries/chain/include/graphene/chain/config.hpp to, say, 10 minutes.
Also --seed-node to connect another computer - it ends up on a different chain
I have been using:
https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook (https://github.com/cryptonomex/graphene/wiki/CLI-Wallet-Cookbook)
https://bitshares.org/blog/2015/08/04/howto-become-a-witness/#bitshares-20-network-or-graphene-testnet (https://bitshares.org/blog/2015/08/04/howto-become-a-witness/#bitshares-20-network-or-graphene-testnet)
I know a little knowledge can be dangerous but its only a test net so who has the know-how to coordinate this?
There is no public testnet yet .. I appologize for not stating it properly in the howto ..
for that reason I moved the howto over to the graphene wiki on github!
The howto though is still valid and I expect a public testnet to appear rather soon ...
Familiarize yourself with the progress of becoming a witness node and prepare for the testnet accordingly.
-
what's your witness node saying? does it load the key? is the new witness id appearing somewhere?
witness node loads the key "id": "1.6.10" and its in the get_global_properties but when the time comes to produce a block I get a Segmentation fault (core dumped) and details of my witness are not on the chain on restart.
So its too soon for mere mortals like me.
-
...I get a Segmentation fault (core dumped)...
for those that want debugging symbols,
apt-get install graphene-dbg
-
Package updated, to get it:
apt-get update
apt-get upgradeboth package and repository are gpg signed, apt will automatically check md5 sums and signatures for you
-
package updated
-
http://pan.baidu.com/s/1gdIx8xP
20150814_bitshares_raspbian.zip
-
pi@raspberrypi:~$ witness_node
2903143ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a thread.cpp:95 thread ] name:p2p tid:3051082832
2904252ms th_a application.cpp:127 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a thread.cpp:95 thread ] name:ntp tid:3023819856
2904276ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks.
2904285ms th_a main.cpp:166 main ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
2904317ms ntp ntp.cpp:81 request_now ] sending request to 202.112.29.82:123
2904365ms ntp ntp.cpp:147 read_loop ] received ntp reply from 202.112.29.82:123
2904369ms ntp ntp.cpp:161 read_loop ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp ntp.cpp:181 read_loop ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
3204333ms ntp ntp.cpp:81 request_now ] sending request to 202.118.1.130:123
pi@raspberrypi:~$ witness_node
2903143ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a thread.cpp:95 thread ] name:p2p tid:3051082832
2904252ms th_a application.cpp:127 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a thread.cpp:95 thread ] name:ntp tid:3023819856
2904276ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks.
2904285ms th_a main.cpp:166 main ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
2904317ms ntp ntp.cpp:81 request_now ] sending request to 202.112.29.82:123
2904365ms ntp ntp.cpp:147 read_loop ] received ntp reply from 202.112.29.82:123
2904369ms ntp ntp.cpp:161 read_loop ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp ntp.cpp:181 read_loop ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
3204333ms ntp ntp.cpp:81 request_now ] sending request to 202.118.1.130:123
-
Can I run anything useful on my Raspberry Pi3 now that we've migrated to bitshares 2.0 ?
-
You can run a trading bot there .. and if it also runs the witness node, then you can have it be faster ..
if you open up the witness' p2p port to the internet, it could server as a public API similar to openledger
-
Can I run anything useful on my Raspberry Pi3 now that we've migrated to bitshares 2.0 ?
You could test out my instruction's https://bitsharestalk.org/index.php/topic,21480.msg279541.html#msg279541 ( skip the VirtualBox stuff as it only for Windoze users :P )
You may be effected by this issue https://github.com/cryptonomex/graphene/issues/568 on arm processors.
-
Hey,
I followed this instructions and it worked...
Now, to connect the wallet to my local node, do I just put ws://127.0.0.1:8090 as the api connection? or do I have to do something more?
-
Hey,
I followed this instructions and it worked...
Now, to connect the wallet to my local node, do I just put ws://127.0.0.1:8090 as the api connection? or do I have to do something more?
Yes if you are using 1 computer - start your node with witness_node --rpc-endpoint "127.0.0.1:8090"and connect the api ws://127.0.0.1:8090 in the light client
If you have a node on a Pi and connect the light wallet from another computer witness_node --rpc-endpoint "0.0.0.0:8090" for Pi and connect the api ws://<Pi-ip-address>:8090 in the light client on other computer
-
pi@raspberrypi:~$ witness_node
2903143ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a thread.cpp:95 thread ] name:p2p tid:3051082832
2904252ms th_a application.cpp:127 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a thread.cpp:95 thread ] name:ntp tid:3023819856
2904276ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks.
2904285ms th_a main.cpp:166 main ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
2904317ms ntp ntp.cpp:81 request_now ] sending request to 202.112.29.82:123
2904365ms ntp ntp.cpp:147 read_loop ] received ntp reply from 202.112.29.82:123
2904369ms ntp ntp.cpp:161 read_loop ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp ntp.cpp:181 read_loop ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
3204333ms ntp ntp.cpp:81 request_now ] sending request to 202.118.1.130:123
pi@raspberrypi:~$ witness_node
2903143ms th_a witness.cpp:70 plugin_initialize ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3"]
2903737ms th_a thread.cpp:95 thread ] name:p2p tid:3051082832
2904252ms th_a application.cpp:127 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:59175
2904272ms th_a thread.cpp:95 thread ] name:ntp tid:3023819856
2904276ms th_a witness.cpp:143 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.
2904280ms th_a main.cpp:165 main ] Started witness node on a chain with 0 blocks.
2904285ms th_a main.cpp:166 main ] Chain ID is 3a5fd421c8af8d9d6f0e5b70f00c1756c8b1609083196a0ef82e395c5e8f480e
2904283ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
2904317ms ntp ntp.cpp:81 request_now ] sending request to 202.112.29.82:123
2904365ms ntp ntp.cpp:147 read_loop ] received ntp reply from 202.112.29.82:123
2904369ms ntp ntp.cpp:161 read_loop ] ntp offset: 10573019371415, round_trip_delay 47986
2904373ms ntp ntp.cpp:181 read_loop ] NTP time and local time vary by more than a day! ntp:2015-10-24T08:45:23 local:2015-06-23T23:48:24
3204321ms ntp ntp.cpp:77 request_now ] resolving... ["pool.ntp.org",123]
3204333ms ntp ntp.cpp:81 request_now ] sending request to 202.118.1.130:123
I get this same thing. It just sits there without downloading anything. Does the Pi have enough RAM to run this? My windows machine uses 1GB to run a node.