Quote from: MIP on June 02, 2019, 06:54:34 PM

Quote from: bible_pay on June 02, 2019, 02:56:58 PM

If you are lower could you please try resyncing?

I tried resyncing and both controller wallet and MNs are ok now (block 123126, hash 7355d3ef0e69ddbae973912643185bcfe5fbbeef8d30f6726eec8047a89a4e5d)

So everything looks great, but when I finally activate the MNs, it says "success" in the controller wallet, and PRE_ENABLED, but in the MN VPS I see

Code:

$ biblepay-cli mnsync status
{
"AssetID": 999,
"AssetName": "MASTERNODE_SYNC_FINISHED",
"AssetStartTime": 1559500589,
"Attempt": 0,
"IsBlockchainSynced": true,
"IsMasternodeListSynced": true,
"IsWinnersListSynced": true,
"IsSynced": true,
"IsFailed": false

$ biblepay-cli masternode status
{
"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
"service": "209.250.243.91:40000",
"status": "Not capable masternode: Masternode not in masternode list"
}
}

Is this expected and maybe I have to wait some time? (in previous classic it showed "active" right after activation from controller wallet)
Also, I checked collateral tx amount and also if it is old enough.

I think waiting does work in this case, but another way around to be sure is on the Sanc itself, stop it, delete the mnc*.* and gov*.* files and mnp*.* files (just the caches) and restart, and as soon as mnsync status passes 3, I believe your node will be more up to date (with the Sanc list).

EDIT: I don't see you in my Sanc list; try ensuring your controller does not have any banned peers first, then re-start the Sanc (with the Start button from the controller), its possible it needs a new re-broadcast done. It takes up to an hour sometimes to see it change, so this is probably normal.