After changed the DA’s and Daproxy IP Address the cust received the message “WARNING: this is a Fault Tolerant setup and currently other DA has the execution ...aborted”:

[[email protected] apache-karaf-2.4.3]# service dadaemon status
Redirecting to /bin/systemctl status dadaemon.service
● dadaemon.service - Data Aggregator
Loaded: loaded (/etc/systemd/system/dadaemon.service; disabled; vendor preset: disabled)
Active: inactive (dead)
[[email protected] apache-karaf-2.4.3]#


[[email protected] scripts]# service dadaemon status
Redirecting to /bin/systemctl status dadaemon.service
● dadaemon.service - Data Aggregator
Loaded: loaded (/etc/systemd/system/dadaemon.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2018-07-30 11:18:44 -03; 54s ago
Process: 3076 ExecStart=/opt/IMDataAggregator/scripts/dadaemon start sysd (code=exited, status=1/FAILURE)

Jul 30 11:18:44 imda01.te.copel.nt dadaemon[3076]: Dload Upload Total Spent Left Speed
Jul 30 11:18:44 imda01.te.copel.nt dadaemon[3076]: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl:...refused
Jul 30 11:18:44 imda01.te.copel.nt dadaemon[3076]: % Total % Received % Xferd Average Speed Time Time Time Current
Jul 30 11:18:44 imda01.te.copel.nt dadaemon[3076]: Dload Upload Total Spent Left Speed
Jul 30 11:18:44 imda01.te.copel.nt dadaemon[3076]: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl:...refused
Jul 30 11:18:44 imda01.te.copel.nt dadaemon[3076]: WARNING: this is a Fault Tolerant setup and currently other DA has the execution ...aborted
Jul 30 11:18:44 imda01.te.copel.nt systemd[1]: dadaemon.service: control process exited, code=exited status=1
Jul 30 11:18:44 imda01.te.copel.nt systemd[1]: Failed to start Data Aggregator.
Jul 30 11:18:44 imda01.te.copel.nt systemd[1]: Unit dadaemon.service entered failed state.
Jul 30 11:18:44 imda01.te.copel.nt systemd[1]: dadaemon.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[[email protected] scripts]#
 

Some files use the IP Address and not the Hostname

PM 3.6 PM Fault Tolerance

If hostname is specified, check /etc/hosts or DNS lookup for the hostname to make sure it's returning correct IP

Check if the Ports 8300, 8301 and 8500 are open, command example from DA Proxy to DA01:
echo -n > /dev/tcp/imda01/8300
echo -n > /dev/tcp/imda01/8301
echo -n > /dev/tcp/imda01/8500

Firewall
service firewalld status
iptables –list

Files and Folders that need to check:
===========================

DA's:
/opt/IMDataAggregator/consul/conf/
/opt/IMDataAggregator/consul-ext/conf/
/etc/DA.cfg
/etc/systemd/system/dadaemon.service
/etc/systemd/system/consul.service
/etc/systemd/system/consul-ext.service

DA proxy:
/opt/CA/daproxy/conf

Note: Several files in these folders has the IP Address or Hostname informed so is better to check one by one

After changed all configuration file is need to stop all services:
============================================

DA’s:
service consul stop
service consul-ext stop
/opt/IMDataAggregator/scripts/dadaemon stop
Only on DA02 /opt/IMDataAggregator/scripts/dadaemon maintenance
systemctl daemon-reload

DA proxy:
service daproxy stop
systemctl daemon-reload

Remove all files from:
================

/opt/IMDataAggregator/consul/data
/opt/IMDataAggregator/consul-ext/data
/opt/CA/daproxy/data

Start all services:
=============

DA’s
service consul start
service consul-ext start

Note: The DA services should to start automatically

DA proxy:
service daproxy start

Commands that can help:
===================

DA proxy:
service daproxy status

DA
service consul status
service consul-ext status
If some files configuration was changed is need to run “systemctl daemon-reload”
ps -elf | grep consul
ps -elf | grep java
/opt/IMDataAggregator/consul/bin/consul members
/opt/IMDataAggregator/consul/bin/consul operator raft list-peers

Web page http://PROXYIP:8500/ui/

See PM Fault Tolerance on site:
https://docops.ca.com/ca-performance-management/3-6/en/administrating/fault-tolerance