Quote from: Grandpa Jones on March 20, 2016, 04:28:23 PM

Quote from: jakiman on March 20, 2016, 01:09:31 PM

Quote from: Grandpa Jones on March 20, 2016, 07:18:37 AM

I get a similar problem with 1.0.2.0 but not 1.0.1.0

When enabling from the controller with start-alias, everything looks fine, with a "result":"successful".

Checking the debug.log of the masternode I can see the correct "Got NEW Masternode entry -" line (identified by txid). Then with masternode list, I can see the correct line "ENABLED" (identified by txid).

But when I do masternode status, I get:

{
   "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
   "service" : "[::]:0",
   "status" : "Not capable masternode: Hot node, waiting for remote activation."
}

I think there is a problem with the new release.

I'm getting the exact same issue for last 3 MN that I created. (both 1.0.1.0 & 1.0.2.0)
I've never had this issue with other MN but only with the 3 MN I've set up today...

Edit: Got 1 of 3 using 1.0.2.0 to start locally. No idea why it worked now after failing last 10 goes. Now 2 to go!
Edit2: Now got all 3 started with 1.0.2.0. All I did was follow the guide by BitcoinFX to upgrade. Then started via "start-alias" from controller wallet.

What do you mean by "start locally"?

I have tried many many many times and it can never start with 1.0.2.0 but starts with no issue for 1.0.1.0, using the same protocol to sync a chain and bring up the node.

Are you trying to run 3 nodes locally? Do they all have public facing IP addresses that are distinct?