Replication agent is installed, but the machine doesn't appear in ACP
Challenge
A replication agent is installed, but the machine is not discovered in Acura.
Solution
1) If a new agent is installed on the machine discovered in Acura before, configuration files from the previous installation might still be in use as long as they are not removed during the agent's deletion.
To avoid this, delete the following folders manually.
For Windows Replication Agent:
C:\ProgramData\Hystax
If you can't see this folder, ensure hidden files and folders are displayed.
After that, install the agent.
For Linux Replication Agent:
sudo rm -rf /etc/hystax
After that, install the agent.
2) If this is the first time a replication agent is installed on the machine, and it is not shown in the Acura Control Panel:
- Make sure that the Security group that the Acura instance belongs to allows all traffic for port TCP/443.
- It is also recommended that traffic be allowed for udp/12201, as the logging service uses this port to send data.
- The firewall on the source machine must be disabled to ensure there is nothing that blocks outgoing traffic.
3) А machine might not be discovered in ACP for a particular customer if it has already been detected by a Replication Agent and assigned to a machine group of another customer. In this case, it will not be detected by a newly installed Replication Agent. Instead, the machine will remain in the group where it was last detected. In this case, manually move the machine to the desired group. Use the “Move to another Group” option of the “Actions” menu in the Machines tab of the ACP.
4) A machine might not be discovered in ACP due to an outdated SSL certificate in the replication agent's config file which doesn't match the one used by Acura.
In that case, the certificate must be replaced manually.
After that, if you are using an external replication agent, simply download it and reinstall, or follow the instructions for internal replication agents:
- Download a file with the script:
- For Windows Replication Agent: hwragent-update-cert-and-ip.cmd
- For Linux Replication Agent: hlragent-update-cert-and-ip.sh
- Update the certificate in the downloaded file: open the file and replace the existing certificate with a valid one.
- Run the script on the appropriate machine.
- Verify replication: once the machines are detected by Acura, replication will proceed.
Related Articles
How to perform a connectivity check if a machine is shown offline in ACP
Challenge A source machine has a replication agent installed but it is shown in an offline state in ACP, although the machine has been properly discovered before. Solution One of the possible ways to check the connection to Acura is to use the telnet ...How to replace Windows replication agent's config file in case a machine is shown offline in ACP
Challenge A machine is shown offline in ACP, although the source instance is running and has been replicated successfully before. Cause The replication agent's config file might have become corrupted during an unexpected termination of the repman ..."Module build for the currently running kernel was skipped" message in console during Replication agent's installation
Challenge During the installation of a Linux replication agent (hlragent) with DKMS, the following message can be displayed in the console: Module build for the currently running kernel was skipped since the kernel source for this kernel does not ...Machine has "Blocked" state in the control panel
Challenge A machine has "Blocked" status in the Machines Groups section of the ACP. Cause A machine becomes "Blocked", if it's used to start a CloudSite. This is primarily true for VMware target clouds. The "Blocked" state will remain as long as the ...How to check that a low replication speed is caused by the source machine
Challenge The Acura Control Panel shows that one of the machines is being replicated with an undesirably low speed. Cause There are several factors that may interfere with a replication and cause a "bottleneck" issue for its speed. But before ...