I seem to be having trouble with the new release. I can't get the masternodes to say "masternode started remotely" like they used to before the update.
I've printed the debug log to the console and looked for clues, it says:
CActiveMasternode::ManageStatus() - Checking inbound connection to 'xxx:yyy'
CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
CActiveMasternode::ManageStatus() - Could not find suitable coins!
CActiveMasternode::Dseep() - Error: masternode is not in a running status
CActiveMasternode::ManageStatus() - Error on Ping: masternode is not in a running status
But I've started the nodes, they are synced, and in the masternode list.. But I think they'll all drop out?
You can try this command in the controller wallet console :
addnode vps_ip:port onetry
masternode start-alias mn_name your_password
Ports must be open on the vps, else the masternode will get banned.
Thanks, that said "result: 'successful', I can get to the node/port from the outside (with telnet), but the node still said "not capable masternode: Could not find suitable coins!" - I did do a cleanup transaction to move all the non 500 coin amounts to the reward address, could that have unlinked anything? I'll try a new TX next perhaps.
EDIT: I tried a new TX with same result. Then I rebuilt the crave-2.0.4.1 binary, and all is well again, so something has stopped working with the activation process in the latest release. I'm still using the latest .2 wallet but without reward addresses specified on the controller side, and downgraded to .1 for the nodes.
I'd be happy to help debug it further if I can.
In the meantime I'll downgrade the remaining nodes and should be happily craving away.. Cheers
