User will sometimes run a faulty script installation with something like the following:
curl: (7) Failed connect to 127.0.0.1:9443; Connection refused Activating DB Replication…
curl: (7) Failed connect to 188.8.131.52:9443; Connection refused Installation and Configuration of High Availability Add-On for Orchestrator is finished.
These are steps to remove the install files, temporarily disable the firewall, enable the port and try the install script again.
Cleaning Up Failed Redis Installs.
If the initial Redis install fails, even after fixing the issue that caused the failure, the Redis install may fail. We use some scripts created by Redis for the install. These scripts do not perform cleanup after a failed installation. As such, when re-running the installation script, the Redis installer will think it is performing an upgrade or it will face other issues.
- To remov e all redis packages run the following: sudo yum remove redis*
- You can verify that all redis packages are removed by running the command: sudo rpm -qa | grep -i redis3.Once all Redis packages are removed, try rerunning the install scripts
During a Redis install, certain HTTP calls are made to the Redis instances thatare being installed. If the servers firewall settings are not configured correctly, these HTTP will fail. This can be fixed by doing the following:
- As a short-term fix, disable the firewall.
- To disable the firewall run the following command: sudo service firewall stop
- For a long term solution, work with your system admins to get the correct ports opened in the firewall. The list of ports needed by redis can be found here - open a port you can use the following command: firewall-cmd --permanent --add-port=<port/protocol>
- You can also enable pinging:a.firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -p icmp -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT