The Data Aggregator in a new Fault Tolerant environment fails to start.
The error from the system only shows it failing with a generic message about it being a Fault Tolerant Data Aggregator.
The Consul Proxy Host is installed on one of the Data Aggregators.
The Consul Proxy Host is installed on one of the Data Aggregators resulting in conflict for the consul agent service both the daproxy and dadaemon need to run.
The Data Aggregator in a Fault Tolerant environment has consul agent and consul-ext processes that allow it to communicate with the Consul Proxy Host.
The Consul Proxy Host has daproxy and consul agent processes that allow it to communicate with the Data Aggregators.
The consul agent processes on each server use the same service files, configuration files, and ports on their respective hosts. When they are trying to both run on the same host, where the Consul Proxy Host and one of the Data Aggregator hosts are the same, these conflicts cause failure of the consul agent service for one or the other to fail.
As a result the system doesn't function as designed and the Data Aggregators never receive the OK to start from the Consul Proxy Host.
All supported Performance Management releases
Install the Consul Proxy Host services on a different host.
After the change to the new host with a new host name and IP, follow the Knowledge Base article How to update Data Aggregator Fault-Tolerant consul proxy services after their hosts IP Address changes.
The steps in that article show what files require change on the Data Aggregators to recognize the new Consul Proxy Host they need to communicate with.