Thanks kydub, that one did have a broken config but the other non-working masternode was correct.
I've turned off staking using
staking=0
reservebalance=5000
and the masternode now shows
./coinonatxd getstakinginfo
{
"enabled" : false,
"staking" : false,
"errors" : "",
"currentblocksize" : 0,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 292822.64254297,
"search-interval" : 0,
"weight" : 250329408570,
"netstakeweight" : 223617043699649,
"expectedtime" : 0
}
But I'm still seeing repeated
CActiveMasternode::ManageStatus() - Checking inbound connection to 'x.x.x.x:44678'
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 statusconnected to self at x.x.x.x:51448, disconnecting
CDarkSendPool::UpdateState() == 3 | 3
connect() to 80.92.226.17:44678 failed after select(): Network is unreachable
in both nodes so was wondering if there was a problem in the XCXT network.
Thanks
I don't think you need to include reservebalance in the conf. Did you use listaddressgroupings to check the address balances to ensure 5000 xcxt are in the mn address? I received a reward 1 minute ago so I doubt it's the network. Is it possible your wallet is locked? How are you starting your masternode? So it unlocks it should be
masternode start
I did manage to find a
similar issue and solution for dash. Here it is adapted to coinonatxd
Problem:
You have masternode in list but coinonatxd masternode debug gives you Could not find suitable coins!. Few hours later you node drops out of list.
Explanation:
This means that your node was not activated actually. On a successfully activated remote masternode coinonatxd masternode debug should return Masternode successfully started. One reason why your masternode wasn't activated could be that new activation message can't reach your masternode from your local wallet because somewhere on its route there are only v11 masternodes and they just ignore new messages.
Fix:
To fix this you need to connect to your node directly and there are few ways to do this:
Simple one, temporary: open console in local wallet and type
addnode
- this will force your client to open direct connection to your MN.
if #1 didn't work for some reason or you want to force your wallet to connect to your MNs every time you run it use the connect arugment when starting the wallet like so:
./coinonatxd -connect=
or add
connect=
in coinonatx.conf. You can add it multiple times if you have many masternodes. Note: this way your client will connect only to specified IPs.