The primary UVMS is unable to connect to the database after the secondary UVMS has been updated. No actions are then any longer possible on the secondary UVMS.
1. Primary UVMS can no longer submit queries as the UVMS the logfile is flooded with these messages:
| 2016-07-26 10:55:06 |INFO | main | com.orsyp.central.server.CheckCentralServer | UniverseException: Central IO Connection problem - Access denied:
Invalid password [UJCENT/uvms_server/X]
| 2016-07-26 10:55:12 |ERROR| request-worker-50 | com.orsyp.central.server.AuthentificationStdImpl | Passphrase not authorized for uvms_server, request coming from:uvms_server
2. Unilst node command executed on the primary UVMS returns:
| 2016-07-26 11:07:34 |ERROR| request-worker-50 | com.orsyp.central.server.AuthentificationStdImpl | Passphrase not authorized for uvms_server, request coming from:uvms_server
| 2016-07-26 11:07:34 |ERROR| main | com.orsyp.central.server.CommonCommand | Unable to extract node list
at $Proxy0.getNodesByWildcard(Unknown Source)
Root Cause: Under normal conditions when the primary UVMS is installed or upgraded, it generates a passphrase, injects it into the database. When the secondary UVMS is then installed or upgrade it takes the passphrase from the datbase and adds it to its phrase.key file. So both are able to connect and to work.
This can however go wrong for different reasons. In this particular situation, the secondary UVMS does not take the passphrase from the database, but generates its own and updates the database with it. In this case the primary will no longer be able to connect and work as its passphrase is no longer valid.
The workaround consists then simply in copying the phrase.key file from the secondary UVMS onto the primary UVMS node and in restarting it again.