- Mar 9, 2014
I'm having the same issue for a few hours now. This last time I started my hot wallets while on my first masternode, I thought I'd try dash-cli masternode start on the remote, and it worked, in that it said "masternode started successfully" (usually, all I have to do is dash-cli masternode debug) I did this with both my wallets online after start-many on my local hot wallet.I'm not sure but I think the following command is the one I was looking for:
./dash-cli masternode status | grep -e SERVER_IP -e SERVER_IP -e etc.
Nope, it's not the correct command either. Writing ./dash-cli masternode status in the VPS terminal shows the following:
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, xxxxxx), coinbase )",
"service" : "106.xxx.xxx.xxx:9999",
"status" : 3,
"pubKeyMasternode" : "xxxxxxxxxxxxx",
"notCapableReason" : "Could not find suitable coins!"
Whatever that means, can anyone please explain?
Anyway, doing the same thing with my second MN wallet didn't work. I don't know what's wrong. Local says masternodes started successfully (in the start-many way) but no joy on remote for second wallet.