How to set up ec2 t1.micro Ubuntu for Masternode part 3/3

chaeplin

chaeplin

Well-known member
* Use this guide only for EC2 instance with Security-Group
* Using this guide on non-EC2 instances is very dangerous ( Especially iptables )

* This guide is valid for RC3(local/remote setup)
* local is home linux cold wallet holding 1K DRK
* remote is server with empty wallet

I. Part 1/3 EC2 Setup
https://darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-1-3.240/

II. Part 2/3 AMI Setup
https://darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-2-3.241/
https://darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-2-3-2.1754/

III. Part 3/3 Masternode update
https://darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-3-3.262/


[Update dakcoind]

1. login ec2, check pwd and cd .darkcoin/
ubuntu@ec2:~$ pwd
/home/ubuntu
ubuntu@ec2:~$ cd ~/.darkcoin/
ubuntu@ec2:~/.darkcoin$ ls
blocks chainstate darkcoin.conf darkcoind darkcoind.pid database db.log debug.log peers.dat wallet.dat
ubuntu@ec2:~/.darkcoin$ ls -la /usr/bin/darkcoind
lrwxrwxrwx 1 root root 32 Apr 10 20:13 /usr/bin/darkcoind -> /home/ubuntu/.darkcoin/darkcoind
Click to expand...
Code: 
pwd
cd ~/.darkcoin/
pwd
ls -la
ls -la /usr/bin/darkcoind

2. download darkcoind
Visit https://www.darkcoin.io/getstarted.html
Download latest vesrion of Masternode(Currentely RC version)
Or visit https://github.com/darkcoinproject/darkcoin-binaries/tree/master/rc

cd ~/.darkcoin
wget https://github.com/darkcoinproject/darkcoin-binaries/raw/master/rc/darkcoin-0.10.11.6-linux.tar.gz
tar xfvz darkcoin-0.10.11.6-linux.tar.gz
cp darkcoin-0.10.11.6-linux/bin/64/darkcoind darkcoind.1
Click to expand...

Code: 
cd ~/.darkcoin
wget https://github.com/darkcoinproject/darkcoin-binaries/raw/master/rc/darkcoin-0.10.11.6-linux.tar.gz
tar xfvz darkcoin-0.10.11.6-linux.tar.gz
cp darkcoin-0.10.11.6-linux/bin/64/darkcoind darkcoind.1


3. check downloaded file and test it's ok
ubuntu@ec2:~/.darkcoin$ ls -la darkcoind.1
ubuntu@ec2:~/.darkcoin$ chmod 755 darkcoind.1
ubuntu@ec2:~/.darkcoin$ ./darkcoind.1 --help
DarkCoin version v0.10.3.4-18-g0f787e5-beta
Click to expand...
Code: 
ls -la  darkcoind.1
chmod 755 darkcoind.1
./darkcoind.1 --help


4. stop darkcoind
ubuntu@ec2:~/.darkcoin$ darkcoind stop
DarkCoin server stopping
Click to expand...

Code: 
darkcoind stop

5. replace
ubuntu@ec2:~/.darkcoin$ mv darkcoind darkcoind.old
ubuntu@ec2:~/.darkcoin$ mv darkcoind.1 darkcoind
Click to expand...
Code: 
mv darkcoind darkcoind.old
mv darkcoind.1 darkcoind

6. start darkcoind
ubuntu@ec2:~/.darkcoin$ darkcoind
ubuntu@ec2:~/.darkcoin$ DarkCoin server starting
Click to expand...
Code: 
darkcoind

7. check running
ubuntu@ec2:~/.darkcoin$ tail -f debug.log
Click to expand...
Code: 
darkcoind getbalance
darkcoind getinfo
tail -f debug.log
 
Last edited by a moderator:
Thanks for putting this together! Your instructions were spot on. I'm struggling with sending the 1k DRK to the new wallet (says it is too much to send at once), but everything else is working flawlessly.
 
zuperdoge said:
Thanks for putting this together! Your instructions were spot on. I'm struggling with sending the 1k DRK to the new wallet (says it is too much to send at once), but everything else is working flawlessly.
Click to expand...
This is a really late reply, but in case someone else has this problem, it's probably only because you forgot to uncheck the darksend checkmark on the right side of the wallet. At this time, we can only send amounts under 10 coins :)
 
I cant start my masternode at all.

Code: 
$ ./darkcoind masternode start "$x"
error: {"code":-1,"message":"masternode list|count|current> passphrase\n"}

This always throws an error. Using latest code from github.
($x holds my password).
 
You probably found out already, but there was an error and misunderstanding. The open source code just allows for payments to MasterNodes, and nothing more, no DarkSend functionality is included :)
 
I'm done! Chaeplin, thanks for putting this together and for being supportive all the time. No way I could have done this on my own.

Although I believe everything is working fine now (the masternode count page has one in my location/isp that wasn't there before), is there a way to check the IP addresses of working masternodes to be sure that mine is there? EDIT: I just figured this out:

Code: 
darkcoind masternode list

It returns a list of all working masternodes with IP address... and my baby is there!! :):):)
 
Last edited by a moderator:
Hi
I'm in the process of setting up an EC-2 masternode. Great tutorial by the way. So far I've got the instance up and running and can log into it from my OS/X command line in terminal. I'm giong to read over the security docs later.

Just one thing - I already set up an instance a couple of days ago, but when I logged into my EC2 account today it was gone. Is there some level of 'activation' below which instances are wiped after a certain amount of time or something ?

Thanks for any tips.
 
Do not, I repeat, DO NOT use Mac OS terminal... I got crap loads of errors that didnt make sense, commands not flying etc, installed vm unbuntu and it went through like a dream. Somehting to do with unicode I think
About EC2, they are listed by region, maybe you're in the wrong region?
EDIT: just had a thought... maybe there is a "putty" for OSx?
 
Last edited by a moderator:
yidakee said:
Do not, I repeat, DO NOT use Mac OS terminal... I got crap loads of errors that didnt make sense, commands not flying etc, installed vm unbuntu and it went through like a dream. Somehting to do with unicode I think
About EC2, they are listed by region, maybe you're in the wrong region?
EDIT: just had a thought... maybe there is a "putty" for OSx?
Click to expand...
Strange, I had no problems at all using the standard terminal in OS X to set up my EC2 instance.
 
A reminder. When finishing, please clean up the terminal history to avoid leaving your password out there:

Code: 
cd ~/
ln -sf /dev/null .bash_history

Then close session, login again and press up arrow to check that there is nothing there. There is another method to avoid your password getting into the console history in the fist place, but I couldn't make it work and this one is easy, so I haven't looked more into it.
 
nice thing about using a remote wallet, is that you don't have to enter your passphrase in the remote wallet. You do it all in the local wallet, and it's easy to keep control of that on your local machine :)
 
TanteStefana said:
nice thing about using a remote wallet, is that you don't have to enter your passphrase in the remote wallet. You do it all in the local wallet, and it's easy to keep control of that on your local machine :)
Click to expand...
I thought about going the remote wallet way, but I saw in a few places doubts about it working or not and I decided against. Eventually I'll do that anyway because it feels much better to have it in cold storage.
 
vertoe said:
I cant start my masternode at all.

Code: 
$ ./darkcoind masternode start "$x"
error: {"code":-1,"message":"masternode list|count|current> passphrase\n"}

This always throws an error. Using latest code from github.
($x holds my password).
Click to expand...
Any replies to this?
 
You must log in or register to reply here.
Back
Top