Applicable to:
- SolusVM
Symptoms
Unable to see information about a node on Dashboard > Nodes > node_name page:
SVM_ERROR: Connection Failed Debug Data: ERROR: 4
Master SolusVM has been migrated recently to the new server and during migration /usr/local/solusvm/data/solusvm.conf
file was not updated on the new server
Cause
The incorrect encryption key is set in SolusVM configuration.
Resolution
Note: The article is applicable for the cases with ERROR: 4 code error only. If the code error is different, search for the solution in this hub article
-
Connect to the master server over SSH.
-
Open the file
/usr/local/solusvm/data/solusvm.conf
with a text editor. Its format is:CONFIG_TEXT: <DATABASENAME>:<USER>:<PASSWORD>:<HOST>:<encryptionkey>
-
Insert encryption eky form the old master node instead of the current key.
Additional Information
See the example in step 3 on Migrating SolusVM Master node to another server
Comments
0 comments
Please sign in to leave a comment.