Hello IOTA Forum

I made a script to automate the installation of a full node

https://forum.helloiota.com/Topic4185.aspx

By dodolord - 10 Dec 2017

Link to the script: https://github.com/nazarimilad/iota-node

I think I will just copy and paste the description in the README to explain what this script does exactly:

There are a lot of tutorials like this one or this one. The problem with this tutorials is that they take quite some time and they aren't easy to follow for people who are new to a Linux environement.

The purpose of this script is to automate the installation of an IOTA full node. It compiles the IRI, it generates an ini configuration file, it sets up a daemon, it can be used to add new neighbor nodes, etc.

I hope it will be helpful to people trying to set up a full node.
By johnprime - 10 Dec 2017

Looks clean. Nice work. 
By dodolord - 10 Dec 2017

johnprime - 10 Dec 2017
Looks clean. Nice work. 

Thanks!
By kakata - 10 Dec 2017

Excellent!! Great job!
By dodolord - 10 Dec 2017

kakata - 10 Dec 2017
Excellent!! Great job!

Thank you :
By Winston - 10 Dec 2017

@dodolord Great work, and thanks for posting this here. Your thread has been pinned to the top of this forum.
By therium - 10 Dec 2017

Why does the IRI jar file have to be compiled? Shouldn't it just run? I'm having problems getting my full node to run on my Win 8 machine.
By dodolord - 10 Dec 2017

therium - 10 Dec 2017
Why does the IRI jar file have to be compiled? Shouldn't it just run? I'm having problems getting my full node to run on my Win 8 machine.

It has two advantages in my opinion.

First of all, you can see in the script from where the source code for the IRI is downloaded and compiled, which is the official repository of the IRI default implementation.
This way you can always easily check if you can trust the generated IRI jar file. If I included a jar file myself or let the script download it from somewhere, you won't be 100 %  sure if you can trust it.

And secondly because compiling it from the source repository always means that you have the latest version of the IRI jar.
By dodolord - 10 Dec 2017

Winston - 10 Dec 2017
@dodolord Great work, and thanks for posting this here. Your thread has been pinned to the top of this forum.

It's an honour!
By dodolord - 11 Dec 2017

UPDATE: now my IOTA installation script integrates IOTA-PM! So now, when your run the script to install a node, you will also have an option to include IOTA-PM within the installation (see screenshot in the README). You won't have to install and configure IOTA-PM yourself.
By dezoid - 15 Dec 2017

Hi,

i get an Error by installing IOTA-P:

Would you like to install IOTA-PM? This is a program for monitoring and managing IOTA peers connected with your node.
[y/n]: y

./iota-node.sh: line 75: npm: command not found
By dodolord - 15 Dec 2017

dezoid - 15 Dec 2017
Hi,

i get an Error by installing IOTA-P:

Would you like to install IOTA-PM? This is a program for monitoring and managing IOTA peers connected with your node.
[y/n]: y

./iota-node.sh: line 75: npm: command not found

It means it doesn't recognize npm. You have to install it first with the command
sudo apt install npm
By Mango - 29 Dec 2017

HI first off great script dodolord,
Made life very easy.

Can I suggest the following
1. Add to your pre-reqs the following items: curl, npm, dig,

2. can you detail BY EXAMPLE how to add a neighbour. Lets say, i have a neighbour with the following details:

tcp://a.b.c.d:12345
udp://6.7.8.9:09876

you mention that to add a neighbor use the following command: sudo iota-node --add-neighbor addressofYourNeighbour

Can you advise the command we need to issue at the terminal of VPS please ?
Sorry, we are brand new to Linux, and doing our best to learn this.
Regards,
Mango Guy
By dodolord - 29 Dec 2017

Mango - 29 Dec 2017
HI first off great script dodolord,
Made life very easy.

Can I suggest the following
1. Add to your pre-reqs the following items: curl, npm, dig,

2. can you detail BY EXAMPLE how to add a neighbour. Lets say, i have a neighbour with the following details:

tcp://a.b.c.d:12345
udp://6.7.8.9:09876

you mention that to add a neighbor use the following command: sudo iota-node --add-neighbor addressofYourNeighbour

Can you advise the command we need to issue at the terminal of VPS please ?
Sorry, we are brand new to Linux, and doing our best to learn this.
Regards,
Mango Guy

Hi Mango,

Thanks for the feedback. I will add dig, curl and npm in the README.

And for the example, you have type the following command:
sudo iota-node --add-neighbor tcp://a.b.c.d:12345

or if you want to add the other neighbor:
sudo iota-node --add-neighbor udp://6.7.8.9:9876


I hope I could help you! Smile
By Mango - 29 Dec 2017

dodolord - 29 Dec 2017
Mango - 29 Dec 2017
HI first off great script dodolord,
Made life very easy.

Can I suggest the following
1. Add to your pre-reqs the following items: curl, npm, dig,

2. can you detail BY EXAMPLE how to add a neighbour. Lets say, i have a neighbour with the following details:

tcp://a.b.c.d:12345
udp://6.7.8.9:09876

you mention that to add a neighbor use the following command: sudo iota-node --add-neighbor addressofYourNeighbour

Can you advise the command we need to issue at the terminal of VPS please ?
Sorry, we are brand new to Linux, and doing our best to learn this.
Regards,
Mango Guy

Hi Mango,

Thanks for the feedback. I will add dig, curl and npm in the README.

And for the example, you have type the following command:
sudo iota-node --add-neighbor tcp://a.b.c.d:12345

or if you want to add the other neighbor:
sudo iota-node --add-neighbor udp://6.7.8.9:9876


I hope I could help you! Smile

Perfect. Thanks.

Do you by any chance have available slot to add me as neighbor.
I installed everything as you mentioned, but i dont have active neighbors.
Plus
By Mango - 29 Dec 2017

Also, after installing.

>>After restarting your terminal, you can run iota-node from everywhere: sudo iota-node <option>
<<
I believe we need to start the software, by issuing sudo iota-node -x   [ is tis correct]

however, things are not great for me. i issued this command at terminal [ sudo iota-node -s]
the entire ting has exited. something like.

Loaded: loaded (/etc/systemd/system/iota-node.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Friday.....
Process: 3542 Execstart =usr/bin/java -jar /root/.iota-node/iri.jar -c /root/.iota-node/iri.ini (code=exited, status=255)
Main PID: 3542 (code=exited, status=255)

......
any idea what this means ???
Did i screw something up while following your instructions...or do you think i need to wipe everything [uninstall] and start from beginning....

Regards,
By dodolord - 30 Dec 2017

Mango - 29 Dec 2017
dodolord - 29 Dec 2017
Mango - 29 Dec 2017
HI first off great script dodolord,
Made life very easy.

Can I suggest the following
1. Add to your pre-reqs the following items: curl, npm, dig,

2. can you detail BY EXAMPLE how to add a neighbour. Lets say, i have a neighbour with the following details:

tcp://a.b.c.d:12345
udp://6.7.8.9:09876

you mention that to add a neighbor use the following command: sudo iota-node --add-neighbor addressofYourNeighbour

Can you advise the command we need to issue at the terminal of VPS please ?
Sorry, we are brand new to Linux, and doing our best to learn this.
Regards,
Mango Guy

Hi Mango,

Thanks for the feedback. I will add dig, curl and npm in the README.

And for the example, you have type the following command:
sudo iota-node --add-neighbor tcp://a.b.c.d:12345

or if you want to add the other neighbor:
sudo iota-node --add-neighbor udp://6.7.8.9:9876


I hope I could help you! Smile

Perfect. Thanks.

Do you by any chance have available slot to add me as neighbor.
I installed everything as you mentioned, but i dont have active neighbors.
Plus

Unfortunately I can't add more neighbors since my server is at it's limits. But you can always find neighbors on this forum, on https://www.reddit.com/r/nodesharing/ and on slack (on the nodesharing channel).
By dodolord - 30 Dec 2017

Mango - 29 Dec 2017
Also, after installing.

>>After restarting your terminal, you can run iota-node from everywhere: sudo iota-node <option>
<<
I believe we need to start the software, by issuing sudo iota-node -x   [ is tis correct]

however, things are not great for me. i issued this command at terminal [ sudo iota-node -s]
the entire ting has exited. something like.

Loaded: loaded (/etc/systemd/system/iota-node.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Friday.....
Process: 3542 Execstart =usr/bin/java -jar /root/.iota-node/iri.jar -c /root/.iota-node/iri.ini (code=exited, status=255)
Main PID: 3542 (code=exited, status=255)

......
any idea what this means ???
Did i screw something up while following your instructions...or do you think i need to wipe everything [uninstall] and start from beginning....

Regards,

This is because the iota-node service (daemon) will only start AFTER adding a neighbor. Since you didn't first add a neighbor, the service was not active and this caused this failure.
Check the power part of the screenshot in the README: "... Add a neighbor to start a node ..."

If the node is not started, you can't use it. I hope It was helpful Smile
By EtUnity - 31 Dec 2017

Great work! Any chance you can add Nelson to the Script?
By EtUnity - 31 Dec 2017

EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?


I tried to run the command after runiing the scripts and got the below error. Did I do something wrong?  Thanks
~$ sudo iota-node -i
sudo: iota-node: command not found

By dodolord - 1 Jan 2018

EtUnity - 31 Dec 2017
EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?


I tried to run the command after runiing the scripts and got the below error. Did I do something wrong?  Thanks
~$ sudo iota-node -i
sudo: iota-node: command not found


After installing iota-node, you have to restart your terminal.
By EtUnity - 1 Jan 2018

dodolord - 1 Jan 2018
EtUnity - 31 Dec 2017
EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?


I tried to run the command after runiing the scripts and got the below error. Did I do something wrong?  Thanks
~$ sudo iota-node -i
sudo: iota-node: command not found


After installing iota-node, you have to restart your terminal.

I did that and still the same error. Do I have to add neighbors for it to work?
Thanks
By dodolord - 1 Jan 2018

EtUnity - 1 Jan 2018
dodolord - 1 Jan 2018
EtUnity - 31 Dec 2017
EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?


I tried to run the command after runiing the scripts and got the below error. Did I do something wrong?  Thanks
~$ sudo iota-node -i
sudo: iota-node: command not found


After installing iota-node, you have to restart your terminal.

I did that and still the same error. Do I have to add neighbors for it to work?
Thanks

Jep, after restarting your terminal, the first thing you have to do is to add one or multiple neighbors. Only then will the service start.
By EtUnity - 1 Jan 2018

dodolord - 1 Jan 2018
EtUnity - 1 Jan 2018
dodolord - 1 Jan 2018
EtUnity - 31 Dec 2017
EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?


I tried to run the command after runiing the scripts and got the below error. Did I do something wrong?  Thanks
~$ sudo iota-node -i
sudo: iota-node: command not found


After installing iota-node, you have to restart your terminal.

I did that and still the same error. Do I have to add neighbors for it to work?
Thanks

Jep, after restarting your terminal, the first thing you have to do is to add one or multiple neighbors. Only then will the service start.

Thanks will do that
By dodolord - 17 Jan 2018

EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?

Sorry for the late reply. I'm busy with my exams. When they are finished, I definitely will add Nelson to the installation.
By dodolord - 1 Feb 2018

EtUnity - 31 Dec 2017
Great work! Any chance you can add Nelson to the Script?

It has been added Wink check my new post
By EtUnity - 1 Feb 2018

Thanks Smile
By cryptohosting - 9 Feb 2018

Hey All

i see to be getting these errors on the Nelson install part - after some research it may be due to the NPM premission issues? i have installed NPM globally and using package manager and still nothing

ss/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
By dodolord - 9 Feb 2018

cryptohosting - 9 Feb 2018
Hey All

i see to be getting these errors on the Nelson install part - after some research it may be due to the NPM premission issues? i have installed NPM globally and using package manager and still nothing

ss/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space

Hmm. Where does this "node-gyp" and "gyp" come from?
By tatubias - 23 Feb 2018

cryptohosting - 9 Feb 2018
Hey All

i see to be getting these errors on the Nelson install part - after some research it may be due to the NPM premission issues? i have installed NPM globally and using package manager and still nothing

ss/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ '9.4.0' ]
gyp verb install input version string "9.4.0"
gyp verb install installing version: 9.4.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version not already installed, continuing with install 9.4.0
gyp verb ensuring nodedir is created /usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0
gyp WARN EACCES user "root" does not have permission to access the dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp/9.4.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/nelson.gui/node_modules/node-sass/.node-gyp"
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space

you can try running 

sudo npm install --unsafe-perm --verbose -g nelson

or

sudo chown -R root:root /usr/lib/node_modules




By maxxist - 30 Apr 2018

dodolord - 10 Dec 2017
Link to the script: https://github.com/nazarimilad/iota-node

I think I will just copy and paste the description in the README to explain what this script does exactly:

There are a lot of tutorials like this one or this one. The problem with this tutorials is that they take quite some time and they aren't easy to follow for people who are new to a Linux environement.

The purpose of this script is to automate the installation of an IOTA full node. It compiles the IRI, it generates an ini configuration file, it sets up a daemon, it can be used to add new neighbor nodes, etc.

I hope it will be helpful to people trying to set up a full node.

nice work. the script and tutorial still work great on ubuntu 18.04.   great place to start for noobs like me.
By s1ckm4n - 13 May 2018

Great, thanks!