Published on: November 28, 2012 by George K.
Scenario:
On Managing the Slave node as a part our SolusVM support, it shows the red warning message “Connection Failed. Debug Data : Error :4” and the VPSes on that node was showing red icons saying they are offline when they are actually not. Actually, the SolusVM Slave not connecting to Master.
Solution:
The reason for this is that the ID and the password of the SolusVM slave used are incorrect and You need to match it with the master. The password is encrypted using mcrypt+salt+random key before it hits the database.
On each slave there is a file (/usr/local/solusvm/data/solusvm.conf) there is a string <ID>:<PASSWORD>. Copy that password and goto Nodes –> List Nodes –> and click “Edit Node Password” icon for the slave node in question. Change the password and you should be able to get it right!.
Other things to try out would be to run upcp on slave and master servers. Also you may need to reconfirm you have master’s IP in the file /usr/local/solusvm/data/allow.dat
If you need any further assistance on SolusVM you can contact our VPS node management team with your requirements and they will get back to you in no time. Click here for VPS node management support
Category : Linux, Troubleshooting, VPS
George started his career in web hosting and Linux technical support in the year 2004 and is with SupportSages since 2009. He has keen interest in server optimizations, custom security solutions, hacked server recovery, cyber forensic and high availability fail over system design and implementation. George loves long drives and is passionate about art and literature.
Add new commentSIGN IN