ops… there is no need to use the sudo command because it will invoke the root/administrator privilege, and we don’t want that, everything should be carried on as a user (tzuser), just type:
@maxtez-raspbaker For some reason I have to use sudo or I’m getting super confused and need to recheck my reality. I’ll give it another shot later tonight and report back. I’m determined to get my RPi3 on the zeronet. Thanks for all your efforts thus far.
ah ah I don’t know if your sudo drama is for real but sounds a bit funny…
yes please don’t give up now, your RPI3 got already on the alphanet and that was THE big step…
I prepared a summary of the steps to get on the zeronet, it is nothing new, just condensed the same existing material in bullet points.
But first a reminder that Tezos and sudo don’t like each other, all commands related to Tezos should be typed 1) as a user (tzuser) without root/administrator privilege 2) from the default location /home/tzuser 3) in the x-windows environment where multiple terminals will/can be opened.
There are essentially 5 steps to get on the zeronet starting from scratch (blank SD card)
- write the image of OS+tezos on the SD card (link to the image file, here: github.com/demodun/tezos-rpi3/wiki page [b-1])
- first time boot: expand the OS to take the full space of the SD card with the command
- use wget to retrieve the zip file tz-zero040318.zip and the file tz-switch040318.sh
(see page [f] with the updates in the wiki site for the links and the exact wget commands)
- change the permission with
chmod 764 tz-switch.shthen type just once
./tz-switch.shto extract the content of the zip file. The command ./tz-switch.sh
will put Tezos for the zeronet in the working location (/home/tzuser/tezos) then it will automatically
extract from the zip file a new “tz-start.sh” file and a new “config.json” file and it will perform
few other operations. Once it is done the command will also delete the zip file (to save space).
- the usual commands that were introduced to run the RPI3 on the alphanet network apply for the zeronet as well:
./tz-init.sh(to be used only the first time to create an identity for the RPI3 on the zeronet),
./tz-start.shto start the node and
./tz-stop.shto stop the node. These script files are all located in /home/tzuser.
Hope it helps…
@wambo any luck getting your RPI3 node up and running?
@maxtez-raspbaker Thanks for putting this together. I haven’t had a chance to revisit this yet but hope to get some time this weekend to take another crack at it. I think you’re probably right though - I was going back and forth off of older and newer sets of instructions.
@maxtez-raspbaker Thank you! Hopefully I can align my multiverses and get my RPi3 on the zeronet tonight!
@maxtez-raspbaker I am still getting confused so I wrote up the below steps to make it simple. I’m still getting “Permission denied” on step 7. Any ideas what I’m doing wrong?
Tezos Zeronet on RPi3
For details: https://github.com/demodun/tezos-RPI3/wiki
Remember: Tezos and sudo don’t like each other, all commands related to Tezos should be typed
- as a user (tzuser) without root/administrator privilege
- from the default location /home/tzuser
- in the x-windows environment where multiple terminals will/can be opened.
There are essentially 8 steps to get your RPi3 on the Tezos zeronet starting from scratch (blank SD card) (16GB minimum size)
Download the Tezos RPi3 image
Using Etcher (https://etcher.io), write the Tezos RPi3 image to your SD card
First time boot:
3. Check to make sure you are in the right folder
type “pwd” (it should return: /home/tzuser)
Expand the Tezos OS to take the full space of the SD card
Use wget to retrieve the zip file tz-zero040318.zip and the file tz-switch040318.sh
wget -NO /home/tzuser/tz-switch.sh https://www.dropbox.com/s/wyb5qihpj5vbpd7/tz-switch040318.sh
Change the permission on the downloaded file to unzip in next step
chmod 764 tz-switch.sh
Type just once to extract the content of the zip file
The command ./tz-switch.sh will put Tezos for the zeronet in the working location (/home/tzuser/tezos) then it will automatically
extract from the zip file a new “tz-start.sh” file and a new “config.json” file and it will perform
few other operations. Once it is done the command will also delete the zip file (to save space)
- The usual commands that were introduced to run the RPI3 on the alphanet network apply for the zeronet as well:
./tz-init.sh (to be used only the first time to create an identity for the RPI3 on the zeronet)
./tz-start.sh to start the node
./tz-stop.sh to stop the node
These script files are all located in /home/tzuser.
thanks for the detail report, now I understand the issue and how to fix it.
I agree that it could have been simpler, the way it started from the alphanet then switching to zeronet keeping both on the RPI3, maybe I should have simply erased the alphanet. Although it seems that soon the zeronet will be promoted to alphanet status. It is getting a bit convoluted but no worries in one way or another I’ll make it working for anyone with RPI3.
Back to your report. It is all perfect up to point 7., the command
chmod 775 tz-start.sh is not necessary. The command itself does not do any harm but somehow in your procedure overshadows the command
chmod 764 tz-switch.sh which is absolutely necessary. You can see that
chmod 764 tz-switch.sh is listed on the first post of this thread but regrettably I forgot to mention about it in my post yesterday (bullet points). I edited the bullet points post to include the correction.
Bottom line, all you need to do is just type:
chmod 764 tz-switch.sh
and this is the day your RPI3 will fly on the zeronet (with the commands you listed in point 8).
@maxtez-raspbaker I remember the other chmod 764 command but wasn’t sure how it fit in. Thanks for the clarification. Hopefully this will make it easier for others to experiment with their RPi3 which is what we all want. I’ll try and write up a similar, simple to follow steps on creating accounts, delegating and baking as well if I get time. Will get my RPi3 working later this evening.
My RPi3 is on the zeronet although not sure if the zeronet is online…
my guess is that you have no connections, right? the reason is that bootstrapping relies on active nodes on the zeronet which are listed in the file config.json. If those nodes are disconnected then…you have no way to get in the network. To fix this you have two options:
option I) edit the file config.json in the folder /home/tzuser/.tezos-node and replace some of the ip addresses you see there. The new ip addresses should be taken from active nodes on the zeronet, you can find them here tzscan.io/network
option II) grab a new config.json that I uploaded today. It should be ok but it is not guarantee
wget -NO /home/tzuser/.tezos-node/config.json https://www.dropbox.com/s/hb08tcutxpe3y49/config041318.json
Once you start seeing the RPI3 connecting with “validator.peer”, I don’t want to spoil your moment but keep an eye in case the node unexpectedly crushes. This is something that came up yesterday (04/13/18), please go to the wiki site (https://github.com/demodun/tezos-rpi3/wiki), in the update page you’ll find a remedy. Nothing new in terms of procedure just upload a new zip file (precompiled tezos) and a new tz-switch.sh file.
It is never ending…and we still have to go through the alphanet (again), betanet and finally mainnet,
but it will be worth it!!
@maxtez-raspbaker Sorry for not getting back sooner. Haven’t had a chance to trouble shoot my RPi3 yet but will soon. I ran across this Asus Tinker board reading through some of my tech feeds and wondered if it may work with your Tezos RPi3 image. Seems a little more powerful than the RPi3 and with 2 GB memory. What do you think?
no problem, there have been some recent changes on the zeronet (see the wiki page), even if you had the node running, a new update is required (new zip file and tz-switch.sh file).
yes I saw the Asus Tinker somewhere, the main plus feature is the 2GB ram memory and perhaps also the 3.0 slot for the SD card. The question is the OS support. At the moment according to the Asus info page there is only one option, that is a Debian-based distribution. The only way to find out whether Tezos can run on it is just try. But I don’t see why it shouldn’t…
Ok, thanks. Will get the new updates for my RPi3 this weekend. Will probably get the ASUS Tinker as well since I can’t help buying cool tech items.
ah ah, I see, let me know if the toy is worth playing with…
First of all this is awesome work and I’ve been following it for a bit now but finally got around to creating my own node. I’m having problems getting it started on the alpha and zero net with your tz-start scripts. I have updated to the latest update for the zero net (041818) and I believe the latest for the alpha (the update you listed on Reddit.) The error is:
xterm: Xt error: Can’t open display :0 :1
And then it just hangs. I’m assuming the command to start the node occurs but the monitoring displays don’t open. I can get it running with the normal run command, but I just wanted to let you know that I keep getting the display error no matter what version I use. I’d be willing to help trouble shoot if you wanted.
Thanks for all the awesome work!
Great! it is always good to hear more people trying Tezos on RPI3.
The display issue has been solved a while ago with a revised script “tz-start.sh” and since then the revised script was always part of the updates.
Maybe your problem may have originated from getting the alpha version from reddit (which file?), in any case,
please refer to the wiki page (github.com/demodun/tezos-rpi3/wiki) for any download.
The alphanet network is down at least until zeronet is promoted to alphanet.
For the time being all you need is 1) the image file (os+tezos) which I think you already have then 2) zip file “tz-zero041818.zip” (which seems you also downloaded) and 3) the file “tz-switch.sh”.
The next step is to change the permission of the file with
chmod 764 tz-switch.sh and run it
./tz-switch.sh This will extract the new pre-compiled tezos for the zeronet, do few more things and once the script is done your node is ready to go on the zeronet. Just type
./tz-start.sh (nothing new here!).
For more info, a good post on this thread ~12 days ago (bullet points list) should cover all your bases, and of course the wiki page.
Let me know how it goes
I updated the tz-start.sh script to what is found here https://github.com/demodun/tezos-RPI3/wiki/[f]-Updates and am still experiencing the same issues. I have been running my pi node on the zero net using just the shell command tezos/tezos-node run to get it going. From looking at the shell script, it simply is supposed to open a new shell running the node with a cpu limit and a bootstrapper for the client (tezos/tezos-client bootstrapped). I have tried everything I can to figure out why it won’t open a new terminal on my display. No matter what xterm command I try to use it simply says: “Can’t open display” and then either “DISPLAY is not set” and when I try to set the DISPLAY (which I’m honestly not even sure what I’m supposed to set it to) it just says it can’t open that display (a lot of help just said host:0.0, but that did not work). What am I missing here?
Also, when it is running, I’d like to make sure it is connected to the network. I checked tzscan.io/network and I couldn’t find my node on the list. Should it be there? Will it not appear there until the boostrapper is also running?
I have so many more questions but I’d like to get this working and play around with this before I keep going full steam ahead. Thanks!
Of course right after I post this, I get it to work. I reset the pi and used the mouse to create a few new windows, and then it recognized my display just fine. Not sure why it was being so fussy the first couple of times. So now I have the node running and the bootstrapper client up as well. If you could still help me confirm it is on the network I would really appreciate. Again, thanks so much for this!
I think you are on the right track, don’t worry about tzscan it may take a while to see your node on the list because the list records only user’s nodes with direct connection to the tzscan node. But if your node is running correctly, you should see on your terminal some scrolling text, something like “date time validator.peer(nn) new head …” or something similar.
you can avoid using the scripts (tz-start.sh, tz-stop.sh) they where created to make things easier (I used them actually!). However keep in mind that the crontab service is set to restart the node every 3 days using those scripts.
I am scratching my head try to understand why your script “tz-start.sh” does not pick the right display. The script was included in the zip file tz-zero041818.zip that you have downloaded. Then when you run the other “script tz-switch.sh” it will extract the content of the zip file including “tz-start.sh”.
Reading your last message again, I realized you mentioned cpulimit. That option was removed in the recent updates like the one you have downloaded, which makes me thinking that somehow the content of the zip file is not extracted properly hence you are still using some old version of “tz-start.sh”. Extracting the content of the zip file is crucial because it also puts in place the pre-compiled tezos for the zeronet network. Now I am wondering if 'tz-start.sh" wasn’t extracted what about the pre-compiled tezos for the zeronet?
Have you changed the permission of “tz-switch.sh” and then run it to extract the content of the zip file, just typing:
./tz-switch.sh ? By doing so you should see the extracted files scrolling on the terminal and the last text is “done!”
You can also check the time stamp on the files in the tezos folder (home/tzuser/tezos) for example with the command
ls -l, the correct time is something like “Apr 18 10:xx”
no worries you’ll get your node running on the zeronet, this is all new for all of us!