Up and Running with a Private Go-Ethereum Network Part 2
In the first post of this series, I talked about getting AWS setup and running your genesis node for a TestNet. Its great to have your own node, but really, you don’t want to have to SSH into the server every time you want to do something. Ideally you would be able to connect your computer to an always live test chain and get to work.
In this short post we’ll talk about how to do that. Since we are running Ubuntu, we need a daemon that will start up the node anytime the server restarts and if the node crashes. I found this article about getting that setup.
If you are caught up with what we did in part 1, then you should just need to follow these instructions:
- SSH into your AWS server
sudo apt-get install supervisorThis installs our supervisor daemon
sudo nano /etc/supervisor/conf.d/geth.confThis creates a daemon config file for geth. We have to
sudoin order to have write access to that file.
- Inside that file enter (assuming you are using the command from part 1):
[program:geth] command=/usr/bin/geth --identity "[SOMETHING]" --rpc --rpcport "8545" --nodiscover --rpccorsdomain "*" --datadir ~/ethchain/datadir/ --port "30301" --networkid [PICK A NUMBER FOR YOUR NETWORK] --verbosity [1-6 number] --rpcapi "db,eth,net,web3" --nat "any" console 2>> ~/ethchain/ethchain.log autostart=true autorestart=true stderr_logfile=/var/log/supervisor/geth.err.log stdout_logfile=/var/log/supervisor/geth.out.log
- Now we need to restart supervisor and get the process started:
sudo supervisorctl reload
To confirm that your node is now running you can
geth attach. I had to use
geth attach http://127.0.0.1:8545 (see this GitHub issue for more information about different
attach commands if this doesn’t work for you).
You should now be in the Geth console. You can now leave your SSH connection to the server and your Geth node should stay running.