Masternode not starting

T

toknormal

Guest
Hi

I can't get my masternodes to start for love nor money and I'm searching for tips.

Remote is on Linux hosted server (Vulture), local on OS/X 10.9.5. Updated all to 0.11.1.19

- independent masternode genkeys generated for each node and configured in masternode.conf
- daemons started ok on remote server
- masternode genkeys configured on remote servers and correspond to local masternode.conf respectively
- daemons start up ok and report blockchain downloaded with getinfo ("balance" reports zero, but it always did)
- "masternode start many" reports "masternode started successfully" on local machine

Everything looks fine except when I call "grep HotCold .darkcoin/debug.log" on remote machine, it just drops a line to the next command prompt and doesn't show me anything. Also nodes don't turn up on ninja.

What am I missing ?
 
the standard configuration file name is darkcoin.conf and not masternode.conf.
try the following command on the remote machine: darkcoind masternode list | grep <your ip>
 
SirHikmat said:
the standard configuration file name is darkcoin.conf and not masternode.conf.
try the following command on the remote machine: darkcoind masternode list | grep <your ip>
Click to expand...

Hi - thanks for the reply.

According to the guide: https://darkcointalk.org/threads/masternode-start-many-guide.2990/

...there is both a darkcoin.conf and masternode.conf where the latter lists the multiple masternodes you have.

b.t.w. I tried the grep command you suggested but nothing - just drops to the command prompt on the next line.

EDIT: ninja is now reporting one of the nodes as live, even though the 'grep' command didn't return anything. It still doesn't see the other one.
 
toknormal said:
Hi

I can't get my masternodes to start for love nor money and I'm searching for tips.

Remote is on Linux hosted server (Vulture), local on OS/X 10.9.5. Updated all to 0.11.1.19

- independent masternode genkeys generated for each node and configured in masternode.conf
- daemons started ok on remote server
- masternode genkeys configured on remote servers and correspond to local masternode.conf respectively
- daemons start up ok and report blockchain downloaded with getinfo ("balance" reports zero, but it always did)
- "masternode start many" reports "masternode started successfully" on local machine

Everything looks fine except when I call "grep HotCold .darkcoin/debug.log" on remote machine, it just drops a line to the next command prompt and doesn't show me anything. Also nodes don't turn up on ninja.

What am I missing ?
Click to expand...
try to remove peers.dat on remotes and restart them
 
ok, I've got a bit further but still no cigar.

Turns out you need more than just the masternode address and the masternode genkey in masternode.conf (multiple masternodes setup). You also need to get the transaction ID that sent the 1000 DRK to the cold wallet address and an "index" (which I've no clue what is but just deduced it was zero by inspection from other configurations).

So now my local wallet parses masternode.conf but I have two problems:

[1] - only 1 of the masternodes is visible (the one in darkcoin.conf that's only there to 'keep it happy'). The second node - that isn't listed in masternode.conf but IS listed darkcoin.conf doesn't appear active

[2] - neither of the nodes respond to the grep HotCold .darkcoin/debug.log test (when I execute that on either of the nodes, the cursor just drops to the next line)

It seems to be a problem with "masternode start many". When I executed that locally, the wallet responded "masternode started remotely" (i.e. singular - and sure enough I only appear to have 1 running)

[3] - I only detected it in ninja - and it's yellow, not green which doesn't seem like a "fully active" situation to me

I must still be missing something. b.t.w. I deleted peers,dat on both nodes.
 
ok, CIGAR !

Turns out, if you type "masternode start many", you get a response saying "masternode started remotely" which kind of fools you into thinking you've done something successful.

On the other hand if you type "masternode start-many" (with a dash in between start and many) you get a whole page of fantastic stuff telling you what masternodes it started, what their aliases are and if each one was successfull etc.

Only thing is - that grep thing never works with me. Always use ninja as the definitive test. (Except I'm still yellow, not green - should I interpret that as an "Amber Alert" ? ;) )
 
toknormal said:
Only thing is - that grep thing never works with me. Always use ninja as the definitive test. (Except I'm still yellow, not green - should I interpret that as an "Amber Alert" ? ;) )
Click to expand...

good to hear that it finally works. Can you please share one IP-address that we can test if you are on the masternode list. The "grep"-thing should work, as soon your node is on the list.

What OS are you running on your server?
 
No problem - you can have them both: 108.61.174.198 and 108.61.175.122.

Just one thing - this morning I went to check the block numbers. They were both stuck on 208908. So I restarted with --reindex and then checked back 20 minutes later. Both had caught up with the blockchain but only one of them was tracking - the other got stuck at 218830 when the latest block was up to 218834 or something.

So I restarted the stuck daemon again (with --reindex) and now it seems to be tracking ok.
 
Whenever you're reindexing, you're remembering to remove the peers.dat file as well, right?
 
toknormal said:
No :) I had no idea that you needed to do that.
Click to expand...
Yep, always remove the peers.dat file from the datafolder after you stop the daemon. Then launch the daemon with ./darkcoind --reindex. Reindexes don't take nearly as long with the new checkpoints added.
 
Had the same issue. Check if both the daemon and the cold storage are synced to the latest block (./darkcoind getinfo and get info on the wallet console)

edit: oh already suggested
 
You must log in or register to reply here.
Back
Top