Applicable to:
- SolusVM
Problem Description
There is a row of the connection issues to slave servers from SolusVM Master server that has a similar symptom, but different causes and resolution steps. During attempt to view the status of the slave node in SolusVM web interface Dashboard > Nodes > node_name , it reports that connection failed with the following generic error:
SVM_ERROR: Master SolusVM fails to connect to the slave node: Connection Failed
In most cases it follows cURL code error, like the one below. Cause and resolution varies based on this error.
SVM_ERROR: Master SolusVM fails to connect to the slave node: Connection Failed Debug Data: ERROR: 4
Note: Cause and resolution varies based on this error and can be completely different.
Resolving Known Errors
| cURL error code | Cause | Resolution article |
| ERROR: 3 | Access control file /usr/local/solusvm/data/allow.dat on the slave node has incorrect IP address of SolusVM Master |
Connection to the slave nodes fails after migration of Master SolusVM node to the new server: Debug Data: ERROR:3 |
| ERROR: 4 | Not supported old PHP handler on the slave server. The issue can occur after upgrade to the latest SolusVM releases |
Master SolusVM fails to connect to the slave node: Connection Failed Debug Data: ERROR:4
|
| ERROR: 4 | ID/KEY mismatch between SolusVM database and in /usr/local/solusvm/data/solusvm.conf file on the slave server |
Cannot connect to slave node: Connection Failed Debug Data: ERROR:4 |
| ERROR: 4 | SolusVM Master has been migrated to the new server recently, however encryption key is not updated | Unable to see information about a node after Master node migration: Debug Data: ERROR: 4 |
| Debug Data: 5 | Web server on the slave server is not running and requests cannot be served | Master SolusVM fails to connect to the slave node: Debug Data: 5 could not send the HTTP request |
| Debug Data: 5 could not send the HTTP request: Could not execute the request: connect() timed out! | Network or firewall issue between master and slave servers | Unable to connect to the node: Connection Failed Debug Data: 5 could not send the HTTP request: Could not execute the request: connect() timed out! |
| Debug Data without specific cURL error | PHP binary /usr/local/svmstack/php/bin/php on the slave node is corrupted | Slave node is not responsible: Connection Failed: Debug Data |
| Debug Data without specific cURL error | Vital PHP functions were disabled at php.ini
|
No information regarding the node: connection failed: debug data |
Comments
0 comments
Please sign in to leave a comment.