Reuben's Start Multiple Masternodes from One Wallet Guide (start-many)

keyser said:
This is how my remote dash.conf looks like on two masternodes on the same server:

Masternode 1
---------------------------------------
#----
rpcuser=xxxxx
rpcpassword=xxxxxx
rpcallowip=127.0.0.1
masternodeaddr=my external ip:9999
bind=127.0.0.2
bind=my external ip
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=200
#--------------------
# change ami_public_ip to public ip address which you connected by ssh
externalip=my external ip
#---------------------
#------------
masternode=1
addnode=23.23.186.131
#----------
masternodeprivkey=xxxxxxxxxxxxxxxxxxxxxxxxxx

---------------------------------------------------------------------------------

Masternode 2

#----
rpcuser=xxxxxxxxxxxxxx
rpcpassword=xxxxxxxxxx
rpcallowip=127.0.0.1
rpcport=8003
masternodeaddr=my external ip:9999
bind=127.0.0.4
bind=my external ip
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=200
#--------------------
# change ami_public_ip to public ip address which you connected by ssh
externalip=my external ip
#---------------------
#------------
masternode=1
addnode=23.23.186.131
#----------
masternodeprivkey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Click to expand...


I have 2 mns running on the same server, using 2 separate ips. I used a similar config to yours. When i issue start-many i get the confirmation the both are running, and withing 5 minutes i can also verify that both IPs are up. However while later, one of them goes down for no apparent reason.

Any ideas to help me out with this? Here's my dash.conf on the server:

rpcuser=xxxxx
rpcpassword=xxxxxx
rpcallowip=127.0.0.1
bind=127.0.0.1
bind=external ip1
masternodeaddr=external ip1:9999
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=XXXXXXXXXprivkey1
addnode=23.23.186.131


rpcuser=xxxxx (same user as above mn)
rpcpassword=xxxxxx (same password as above)
rpcallowip=127.0.0.1
bind=127.0.0.2
bind=external ip2
masternodeaddr=external ip2:9999
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
masternodeprivkey=privkey2
addnode=23.23.186.131
 
vitriol said:
I have 2 mns running on the same server, using 2 separate ips. I used a similar config to yours. When i issue start-many i get the confirmation the both are running, and withing 5 minutes i can also verify that both IPs are up. However while later, one of them goes down for no apparent reason.

Any ideas to help me out with this? Here's my dash.conf on the server:
Click to expand...

"bind"= <your_external_ip1> and "bind"= <your_external_ip2>. Remove those bind=127.0.0.x lines.

And, you have to set "rpcport" to 2 different ports because when both dashd try to open a RPC-socket on 127.0.0.1 one will fail.
 
crowning said:
"bind"= <your_external_ip1> and "bind"= <your_external_ip2>. Remove those bind=127.0.0.x lines.

And, you have to set "rpcport" to 2 different ports because when both dashd try to open a RPC-socket on 127.0.0.1 one will fail.
Click to expand...
Ugh, removed the bind=127.0.0.x part, but im not sure where to put the different ports for rpc.
Wild guess is rpcallowip=127.0.0.1:porthere?
Problem is I dont know which port to use
 
vitriol said:
Ugh, removed the bind=127.0.0.x part, but im not sure where to put the different ports for rpc.
Wild guess is rpcallowip=127.0.0.1:porthere?
Problem is I dont know which port to use
Click to expand...
use different for each dash.conf
port=9998
port=9997
etc....

edit: I meant what is in the bottom ;)
 
UdjinM6 said:
actually
rpcport=9998
rpcport=9997
etc
:rolleyes:
Click to expand...
But why does he have to do all this? Can't he just have these lines for all of his MNs in one wallet and it still works on Mainnet: (omit the line numbers)

  1. rpcuser=SomeRandomString
  2. rpcpassword=EvenLongerRandomString
  3. rpcallowip=127.0.0.1
  4. listen=0
  5. server=1
  6. daemon=1
  7. logtimestamps=1
 
Update: I tried setting port to a diff value, then i tried setting rpcport to a different value. Same result, one of the two masternodes goes down after a few minutes. Does anyone know if I can start the daemon to only log errors and not all mn debug messages? At least that way i can find out what s going on
 
moli said:
But why does he have to do all this? Can't he just have these lines for all of his MNs in one wallet and it still works on Mainnet: (omit the line numbers)

  1. rpcuser=SomeRandomString
  2. rpcpassword=EvenLongerRandomString
  3. rpcallowip=127.0.0.1
  4. listen=0
  5. server=1
  6. daemon=1
  7. logtimestamps=1
Click to expand...
vitriol said:
..... Here's my dash.conf on the server:
Click to expand...
:rolleyes:

vitriol said:
Update: I tried setting port to a diff value, then i tried setting rpcport to a different value. Same result, one of the two masternodes goes down after a few minutes. Does anyone know if I can start the daemon to only log errors and not all mn debug messages? At least that way i can find out what s going on
Click to expand...

Send me debug.log files from both datadir-s on your server pls. I'll have a look. [email protected]
 
UdjinM6 said:
:rolleyes:



Send me debug.log files from both datadir-s on your server pls. I'll have a look. [email protected]
Click to expand...
UdjinM6, you the man! Alas, feeling a bit idiotic, now that u mention it, i have to ask...both data dirs?? I have not seen any mention anywhere that there should be TWO data dirs. I only had one, 1 config file with the concatenated content u see above.
Sigh, i wish these things would be more explicit.
I will try and run 2 daemons with 2 configs, see how that works
 
vitriol said:
UdjinM6, you the man! Alas, feeling a bit idiotic, now that u mention it, i have to ask...both data dirs?? I have not seen any mention anywhere that there should be TWO data dirs. I only had one, 1 config file with the concatenated content u see above.
Sigh, i wish these things would be more explicit.
I will try and run 2 daemons with 2 configs, see how that works
Click to expand...
Aha! Yep, that's the problem.
You need 2 datadirs with separate dash.conf in each one and ran daemons like
Code: 
dashd -datadir=/full/path/to/datadir1
dashd -datadir=/full/path/to/datadir2
 
Hi there,

Could someone point me what else can I check - mainly - I'm able to start-many two of my masternodes:

{
"overall" : "Successfully started 2 masternodes, failed to start 0, total 2",
"detail" : {
"status" : {
"alias" : "MN1",
"result" : "successful"
},
"status" : {
"alias" : "MN2",
"result" : "successful"
}
}
}

I can see them on dashninja.pl, but as soon as I turn off my cold wallet the masternodes disappear :-(
dash.conf on remote servers:

rpcuser=A93Aap5Nr80OS543OJQWoJWYcWoMFt2njKbBiUnzA34YEocBfegGrOiHBfpgX8mFSKmOJsej
rpcpassword=KGFU9nQ3GY43hIeKWRmXPexXtlvimaM2CprehLhiRBsSi3JHj5Zot2lHbMZZNJOz3oiltTh0J
#rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1

rpcuser=A93AaC93jncL0iWCPb32maRHdxfZNUyb6Ejl1fPfrY4CA2nf25Z5Q45qfL7nT12lqywujsLLQsB0SEocBf
rpcpassword=KGFU9nQGYhIeKWRmXPexX4el61Ke1lA981Ncrc8RFjxySVwZdvfSXEqebMZZNJOz3oiltTh0J
#rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1

masternode.conf and dash.conf on local (cold wallet):


MN1 IPaddress1:9999 MASTERNODEPRIVKEY TRANSACTIONHASH 0
MN2 IPaddress2:9999 MASTERNODEPRIVKEY TRANSACTIONHASH 1


rpcuser=R12AqewN43DOrewMFN2f4U32fM432fB2Ef32fR2fS2fA2fN2fD43fL4gt65Eh76Tj76Tj76EuR65yS54
rpcpassword=LgfdsO3214NfeGttgE54fsdfsdg5g335Rgg6R45gA45gN5Dg5OgM54gS5gT5Rg5Ig5NgG5gO5Fg5
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
addnode=23.23.186.131

Am I missing something??

Dash version - "version" : 120049,

Best regards
 
dash version @ local ? same or lower?

For local you only need the masternode.conf file and put there this:
alias_of_MN IP:9999 generated_privkey TX_ID INDEX_NR

On remote config - dash.conf put these:
Code: 
rpcuser=
rpcpassword=
rpcallowip=127.0.01
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=100
addnode=23.23.186.131
masternode=1
masternodeprivkey=same_privkey_as_for_local_config

start from local and tell me if it disappears now....
 
Last edited by a moderator:
Thank for a quick reply.
In first post I see - "Please note that when using masternode.conf, dash.conf no longer needs to specify "masternode=1, masternodeprivkey and ip" anymore as this is all integrated into masternode.conf."

Dash version - remote and local = newest 0.12.49
Had to add masternodeprivkey also. Testing :)
 
you do not need to put masternode=1 on local..... your local needs only one line in config ....

in your remote, YES, you need to have the code above....

edit: to clarify the things....

on local you needs only masternode.conf

on remote you needs only dash.conf :)
 
Last edited by a moderator:
I understand now.
Well, at least now I see "EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon." on remote debug.log's :)
Looks good :) Switched off cold wallet and I still see my MN's on dashninja.pl :)
Thanks a lot Spławik :) (dzięki bardzo Kolego :)
 
Hi guys,

I have a problem here.

Local dash.conf = empty

Local masternode.conf entries are correct.

It always says

you must set masternode=1 in the configuration
(code -1)

when starting the nodes from console.

But when I add that to dash.conf it also wants a mnprvkey there..

What am I doing wrong?
 
You must log in or register to reply here.
Back
Top