Applicable to:
- SolusVM
Symptoms
Master SolusVM fails to connect to the slave node:
SVM_ERROR: Debug Data: 5 could not send the HTTP request: Could not execite the request: couldn't connect to host
Webserver on the slave node is not running:
# service svmstack-nginx status
nginx dead but pid file exists
Cause
Webservice is not running on the slave node and requests cannot be served
Resolution
Note: The article is applicable for the cases with ERROR: 5 code error only. If the code error is different, search for the solution in this hub article
- Connect to the slave node via SSH
- Start
svmstack-nginx
service# service svmstack-nginx restart
# service svmstack-fpm restart - Fix the errors if the service fails to start. If you are not able to fix errors on your own, consider contact SolusVM support.
Comments
0 commentsPlease sign in to leave a comment.