When you start a remote masternode when the wallet is locked, the masternode doesn't start. However once you started a locked wallet once, it is impossible to start the Masternode even when unlocked.
Steps to reproduce:
- Encrypt QT Wallet
- Set up local and remote Masternode as per setup guide
- Leave QT wallet locked
- Click on Start Many in the QT Wallet
- Receive error message "Cannot allocate VIN"
- Unlock QT Wallet
- Click on Start Many in the QT Wallet
- Still receive error message "cannot allocate VIN"
Step 8 should result in "Masternode started successfully"
Restarting the QT Wallet doesn't help.
Ideally the QT Wallet should check whether the wallet is locked and prompt the user to unlock before starting the MN.
Secondly, why does this scenario occur? Does something get cached somewhere?
When you start a remote masternode when the wallet is locked, the masternode doesn't start. However once you started a locked wallet once, it is impossible to start the Masternode even when unlocked.
Steps to reproduce:
Step 8 should result in "Masternode started successfully"
Restarting the QT Wallet doesn't help.
Ideally the QT Wallet should check whether the wallet is locked and prompt the user to unlock before starting the MN.
Secondly, why does this scenario occur? Does something get cached somewhere?