How To Fix Slave Connection Error – SolusVM – Error Retrieving Information Could not contact
You may get an error in your SolusVM Admin control panel like the one below, even if your slave is online.
Error Retrieving Information... Could not contact xxx.xx.xxx.xx on port 6767 413 - Request Entity Too Large
Assuming your slave dedicated server is online and you can SSH into it then there are a few things you can check to see why your Master cannot connect to your slave.
Slave Connection Error – Have you used all your space?
Use the df -h command inside your slave to check you have not used all of the available space on the / drive. If you have and it shows as 100% usage you will need to delete some files. This will restore access.
Check ID key and add Mater IP in allow.dat
2. Is the ID Key and Password Correct?
You can check the file /usr/local/solusvm/data/solusvm.conf inside your slave and compare it to your node settings in your SolusVM admin panel. Ensure they match. use the command
Is your Master IP listed in /usr/local/solusvm/data/allow.dat if not add the IP of your master to this file and save it.
Firewall Blocking Connections?
Disable the firewall on both your master and slave to see if this resolves your problem and restores connectivity. You need to ensure port 6767 is open on both your master and your slave. You can use an iptables rule to open this port.
Check SELinux Status
Check the status of SELinux and if it is enabled disable it. You can check the status of SELinux by issuing
If SELinux is enabled you can disable it by editing the /etc/sysconfig/selinux file.
Just change the SELinux=enforcing directive to the one below, save and close the file. It’s a good idea to reboot at this stage.
How Was This Article? – SolusVM Slave Connection Error – Error Retrieving Information Could not contact