• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

TAO'S MASTERNODE SETUP GUIDE FOR DUMMIES (UPDATE GUIDE UPDATED FOR 13.0)

Hi, am wondering if someone would be willing to help me trouble shoot whats wrong with my MN. I usually monitor from DashWhale and I see that the node is down and I have no IP address. So, I logged into my VPS to check and the server is up, no problem's there.

When I run './dash-cli getinfo' or './dash-cli masternode list full | grep YOUR IP' I am getting a message that

error you must set rpcpassword=<password> in the configuration: /root/.dash/dash.conf

But I sudo into that file and still have the same rpcpassword as always...

I am confused of what steps I need to take, other than trying to do a total reinstall.
 
Amazing said:
Hi, am wondering if someone would be willing to help me trouble shoot whats wrong with my MN. I usually monitor from DashWhale and I see that the node is down and I have no IP address. So, I logged into my VPS to check and the server is up, no problem's there.

When I run './dash-cli getinfo' or './dash-cli masternode list full | grep YOUR IP' I am getting a message that

error you must set rpcpassword=<password> in the configuration: /root/.dash/dash.conf

But I sudo into that file and still have the same rpcpassword as always...

I am confused of what steps I need to take, other than trying to do a total reinstall.
Click to expand...
If you were following this guide make sure you logged in as a user you created and not as a root.
 
UdjinM6 said:
If you were following this guide make sure you logged in as a user you created and not as a root.
Click to expand...

I believe the node is restarted now. The problem I have is that when I run the command
Code: 
grep HotCold .dash/debug.log
there is no debug.log file. I've looked for it in all the directories and it doesn't seem to be there. Can anyone understand why it's missing, or how to create it? Because I need to have the MN setup so I can put my local wallet in cold storage and it will still run, as I am frequently traveling.
 
Wow!
This looks like a Really Great, detailed explanation, which would be perfect for the likes of me !
I got a pile of spare pc's hangin' around... ( in various states of dis-repair) I gotta give it a try.

Does all this info translate to 2016 and the DASH name-change?

Gosh! I dunno how much fiat it took to get a 1k bundle of DRK back in 2014, but I'll probably need to sell our 1st borne to come up with the 8k needed 2day !
He's industious, strong, diligent, and would be a great bargain for anyone interested and we would miss him greatly.... :) Just kidding ! this is Not SR and I'm not selling kids !

Congrats to all the early investors who could see DASH, (DRK) was a great opportunity ! Without their investment in the 'New kid on the block', DASH would not be what is has grown to, today !

Best
rc
 
I set up a masternode on VULTR and connected it to my local DASH-QT. But I forgot a maybe important step. Instead of
> masternode genkey
> getaccountaddress 0
I just did
>masternode genkey
Somehow the masternode seems to run. I put the 1000 DASH into the initial default address.
But what will be the consequences?
 
Dworf said:
I set up a masternode on VULTR and connected it to my local DASH-QT. But I forgot a maybe important step. Instead of
> masternode genkey
> getaccountaddress 0
I just did
>masternode genkey
Somehow the masternode seems to run. I put the 1000 DASH into the initial default address.
But what will be the consequences?
Click to expand...
You are good. As long as you used an address which has a 1000DASH deposit, and set up the masternode.conf properly, everything is fine.

Does your node say "ENABLED" when you run

./dash-cli masternode list full | grep YOUR IP

?

If so, you have no worries.
 
TaoOfSatoshi said:
You are good. As long as you used an address which has a 1000DASH deposit, and set up the masternode.conf properly, everything is fine.

Does your node say "ENABLED" when you run

./dash-cli masternode list full | grep YOUR IP

?

If so, you have no worries.
Click to expand...

yes it says ENABLED

Even in DASH-QT the command "masternode list-conf" shows the configuration

If there is no need for "masternode genkey" then why is it in every tutorial?
And to which address will the payout go?
 
here is some information from my DASH-QT debug panel:

> masternode status
{
"vin" : "CTxIn(COutPoint(XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, 1), scriptSig=)",
"service" : "xx.xx.xx.xx:9999",
"status" : "Not capable masternode: Wallet is locked."
}​

>masternode list-conf
{
"masternode" : {
"alias" : "MN1",
"address" : "xx.xx.xx.xx:9999",
"privateKey" : "YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY",
"txHash" : "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"outputIndex" : "1",
"status" : "MISSING"
}
}​

what does the MISSING status mean - wrong configuration in core?

after unlocking the wallet:

> masternode status
{
"vin" : "CTxIn(COutPoint(XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, 1), scriptSig=)",
"service" : "xx.xx.xx.xx:9999",
"status" : "Not capable masternode: Wallet is locked."
}​

why does it say "Wallet locked" when the wallet is unlocked
 
Can this Masternode thing be done on a dedicated Linux machine without the VULTR account thingy. ?
I am not sure I understand if it is an absolute necessity or if there are particular reasons for it, can we do it without the VULTR account ? Seems like there is always more money to be paid to others eroding the said gains.
 
Hi guys, would you mind a question about multiple masternode launch?
I have read several times the tutorial here
https://www.dash.org/forum/threads/taos-masternode-setup-guide-for-dummies-updated.2680/
but still can not understand one thing. English is not my native language, so, probably that`s why.

So,I have 4000 dash and I would like to start 4 masternodes on a remote Linux VPS. I have been using a masternode hosting, so I have my local masternode.conf configured, it looks like this

MN1 ip1:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0
MN1 ip2:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0
MN1 ip3:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0
MN1 ip4:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0

this is just an example of course. All private keys, etc. are individual for each masternode.
I am ok with my local settings and i will change IP addresses for a new VPS. But i can not catch, how to set up the remote server.
Do I understand right than I need 4 different IP-addresses, but still will be able to use all of the 4 masternodes within one VPS? If so, I thought first, that i need to change the dash/dash.conf on the remote VPA and add extra sections like

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=2
masternodeprivkey=key2
addnode=ip address 2

this is for the second masternode, etc.

However i found here https://github.com/dashpay/dash/blob/v0.12.1.x/doc/guide-startmany.md this info:

If you are using a masternode.conf file you no longer need the dash.conf file. The exception is if you need custom settings (thanks oblox). In that case you must remove masternode=1 from local dash.conf file. This option should be used only to start local Hot masternode now.

I am lost now, shall i still specify all the info on remote VPS in dash.conf or...? Please advise for a dummy how settings for 4 masternodes shall look like and what file they shall be saved in...
Thank you in advance.

UPD. Just found info in the neighbour thread:
Balych said:
Yes you can, and yes each dashd need own IP.
Use dash.conf option bind=123.123.123.123 to specify address.
Click to expand...

But I still can`t understand how in this case dash.conf shall look like. If i write it so:

server=1
rpcuser=username
rpcpassword=password
masternode=1
bind=ip1
masternode=2
bind=ip2
masternode=3
bind=ip3
masternode=4
bind=ip4

will it be sufficient considering that all other info is specified in masternode.conf?



 
Last edited:
obiwan-kenobi said:
Hi guys, would you mind a question about multiple masternode launch?
I have read several times the tutorial here
https://www.dash.org/forum/threads/taos-masternode-setup-guide-for-dummies-updated.2680/
but still can not understand one thing. English is not my native language, so, probably that`s why.

So,I have 4000 dash and I would like to start 4 masternodes on a remote Linux VPS. I have been using a masternode hosting, so I have my local masternode.conf configured, it looks like this

MN1 ip1:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0
MN1 ip2:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0
MN1 ip3:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0
MN1 ip4:9999 7rxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0

this is just an example of course. All private keys, etc. are individual for each masternode.
I am ok with my local settings and i will change IP addresses for a new VPS. But i can not catch, how to set up the remote server.
Do I understand right than I need 4 different IP-addresses, but still will be able to use all of the 4 masternodes within one VPS? If so, I thought first, that i need to change the dash/dash.conf on the remote VPA and add extra sections like

rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=2
masternodeprivkey=key2
addnode=ip address 2

this is for the second masternode, etc.

However i found here https://github.com/dashpay/dash/blob/v0.12.1.x/doc/guide-startmany.md this info:

If you are using a masternode.conf file you no longer need the dash.conf file. The exception is if you need custom settings (thanks oblox). In that case you must remove masternode=1 from local dash.conf file. This option should be used only to start local Hot masternode now.

I am lost now, shall i still specify all the info on remote VPS in dash.conf or...? Please advise for a dummy how settings for 4 masternodes shall look like and what file they shall be saved in...
Thank you in advance.
Click to expand...
If you have 4 IPs on one server you can do this by having 4 daemons running i.e. you would need 4 data folders (1 for each) and you need to specify this folders when you run daemon via -datadir=/full/path/to/folder1 etc.
As for config, yes, you still need dash.conf in each of these remote folders. Few corrections to the one you posted:
masternode=1 - always "=1", no matter which masternode it is
masternodeaddr=ip2:9999 - should be masternodeaddr, not addnode
 
obiwan-kenobi said:
I would like to start 4 masternodes on a remote Linux VPS.
Click to expand...

This, is where the limit of my knowledge fades rapidly !
My question is with the actual meaning of 'remote'. ...and how that may relate to the DASH network, community, and expansion thereof.

Physical location, in regards to under-served geographical locations of population, is what I am concerned with.

Is the utility of DASH truly served by an increase in the MN count in any specific location, or is it advantageous, in the long run, to expand geographically ?

Best
rc
 
UdjinM6 said:
If you have 4 IPs on one server you can do this by having 4 daemons running i.e. you would need 4 data folders (1 for each) and you need to specify this folders when you run daemon via -datadir=/full/path/to/folder1 etc.
As for config, yes, you still need dash.conf in each of these remote folders. Few corrections to the one you posted:
masternode=1 - always "=1", no matter which masternode it is
masternodeaddr=ip2:9999 - should be masternodeaddr, not addnode
Click to expand...
Thank you for advice. Just sent a small donation. What about requirements to hardware? Willl the configuration of 1 x 2,2 Ghz Xeon processor, 1 Gb memory, 20 Gb HDD, unlimited internet access enough to run 4 daemons?
 
obiwan-kenobi said:
Thank you for advice. Just sent a small donation. ...
Click to expand...
Thanks!

obiwan-kenobi said:
... What about requirements to hardware? Willl the configuration of 1 x 2,2 Ghz Xeon processor, 1 Gb memory, 20 Gb HDD, unlimited internet access enough to run 4 daemons?
Click to expand...

- Data folder is ~2Gb+ and slowly growing so it's 4 x ~2Gb+ = ~8Gb+ for data. Given the fact that OS itself usually take ~10-15Gb+ I would aim at 30Gb for HDD.
- 1Gb of RAM could be enough probably but only if you have swap enabled imo. This however would mean that you would need another few Gb for HDD (and you'll probably get very poor performance in peak times like daemon restart etc). I recommend to count memory consumption as ~500 Mb per instance (i.e. when you run 1 daemon per VPS), not sure how much is needed when they run side by side. I would guess that 4 x 500Mb = 2Gb should be ok and should leave some room for the system itself too.
- CPU should be enough imo. Normally CPU usage for dashd daemon is not that high though you can experience some hiccups during simultaneous daemons (re)start (e.g. on VPS reboot).
 
UdjinM6 said:
Thanks!



- Data folder is ~2Gb+ and slowly growing so it's 4 x ~2Gb+ = ~8Gb+ for data. Given the fact that OS itself usually take ~10-15Gb+ I would aim at 30Gb for HDD.
- 1Gb of RAM could be enough probably but only if you have swap enabled imo. This however would mean that you would need another few Gb for HDD (and you'll probably get very poor performance in peak times like daemon restart etc). I recommend to count memory consumption as ~500 Mb per instance (i.e. when you run 1 daemon per VPS), not sure how much is needed when they run side by side. I would guess that 4 x 500Mb = 2Gb should be ok and should leave some room for the system itself too.
- CPU should be enough imo. Normally CPU usage for dashd daemon is not that high though you can experience some hiccups during simultaneous daemons (re)start (e.g. on VPS reboot).
Click to expand...
Got it, thank you! Hopefully the last question: do they generate a lot of traffic? If a VPS has a bandwith limit, say, 1000 Gb per month, will this be enough?
 
obiwan-kenobi said:
Got it, thank you! Hopefully the last question: do they generate a lot of traffic? If a VPS has a bandwith limit, say, 1000 Gb per month, will this be enough?
Click to expand...
Should be enough for 1 MN for sure but I can't remember how many bandwidth you need exactly. Probably @crowning can share some recent stats?
 
A
UdjinM6 said:
Should be enough for 1 MN for sure but I can't remember how many bandwidth you need exactly. Probably @crowning can share some recent stats?
Click to expand...

Around 600 MB/day (ingoing + outgoing traffic together), but I've limited the Masternodes I host to 32 connections, so without this limit there will be more traffic, about twice as much if I remember correctly.

As for the system load, CPU isn't critical usually (dual core recommended, though), but the RAM usage.
A 4 GB RAM server can hold:
  • 10 Masternodes with an average load of 2
  • 11 with a load of 3
  • 12 with a load of 5
  • 13 with a load of 10
  • 14 with a load of 65

So, from my tests, 12 Masternodes per 4GB works, but the system is already quite unresponsive, and a reboot needs ages to sync them all.
My advice is 10 Masternodes per 4 GB RAM.
 
Last edited:
Hi,
my vultr VPS is making restarts quite often now days.
"Dear Customer,
Regarding the following subscriptions:
768 MB Server - x.x.x.x (mnode) in Amsterdam

Our monitoring system indicated an issue with the hardware node hosting the instances listed in this e-mail. Our engineering team has investigated the issue and initiated a restart of the host node in question.

Please note: This event rebooted the instances listed in this e-mail but there is no impact on your data and configurations."

How i can continue my VPS masternode normally (without counting the days from the beginning?)
i only restart the service ./dashd
but i don't see my node in dashninja anymore!
thanks
edit: i have lost over 2 weeks payments !
i think the best way is to auto start ./dashd after a server restart. Is it possible in ubuntu?
 
Last edited:
crowning said:
A


Around 600 MB/day (ingoing + outgoing traffic together), but I've limited the Masternodes I host to 32 connections, so without this limit there will be more traffic, about twice as much if I remember correctly.

As for the system load, CPU isn't critical usually (dual core recommended, though), but the RAM usage.
A 4 GB RAM server can hold:
  • 10 Masternodes with an average load of 2
  • 11 with a load of 3
  • 12 with a load of 5
  • 13 with a load of 10
  • 14 with a load of 65

So, from my tests, 12 Masternodes per 4GB works, but the system is already quite unresponsive, and a reboot needs ages to sync them all.
My advice is 10 Masternodes per 4 GB RAM.
Click to expand...

does this mean you run many MNs on the same machine with one single IP address?
 
You must log in or register to reply here.
Back
Top