The lockbox stable value threshold was not met because the system fingerprint has changed. To reset the system fingerprint, open the lockbox using the passphrase. : File : /opt/voyence/lockbox/xml/csp.clb.
To resolve this situation, execute the following steps on AS:
1. Navigate to $VOYENCE_HOME/bin directory as follows:
cd $VOYENCE_HOME/bin
2. Type the following commands to unlock the lockbox:
source /etc/voyence.conf
./cstdriver -lockbox $VOYENCE_HOME/data/lockb.clb -passphrase <passphrase>
3. Restart vcmaster with following command:
service vcmaster restart
On distributed setup,
- If you choose Standard Security mode during AS installation, copy lockb.ekey from $VOYENCE_HOME/data in the AS to $VOYENCE_HOME/data on the remote server (DS, RA, or Database).
Restart vcmaster on remote servers.
- If you chose Advanced Security mode during AS installation, make sure lockbox on AS has DS, RA details (server name, IP address) added/present.
Steps to follow as below:
a. On the AS, navigate to $VOYENCE_HOME\bin directory.
cd $VOYENCE_HOME/bin
b. Add distributed system hosts to the lockbox using the cstdriver utility if not added already, as follows:
source /etc/voyence.conf
./cstdriver -lockbox $VOYENCE_HOME\data\lockb.clb
-passphrase <passphrase> -addHost <FQDN of Report Advisor server>
./cstdriver -lockbox $VOYENCE_HOME\data\lockb.clb
-passphrase <passphrase> -addHost <IP address of Report Advisor server>
./cstdriver -lockbox $VOYENCE_HOME\data\lockb.clb
-passphrase <passphrase> -addHost <FQDN of Device server>
./cstdriver -lockbox $VOYENCE_HOME\data\lockb.clb
-passphrase <passphrase> -addHost <IP address of Device server>
c. Go to $VOYENCE_HOME\data directory.
d. Copy the lockb.clb file to $VOYENCE_HOME\data on each of the distributed system hosts (DS, RA).
e. Restart vcmaster on each of distributed system hosts.