Enabling debug on AWS proxy
Enterprise Workloads Editions
❌ Business| ✅ Enterprise (Purchase Separately) | ✅ Elite
This topic discusses steps to be performed on the AWS proxy to enable debug. The procedure helps in troubleshooting failures during the DR failover job
Procedure
- Login to AWS proxy with the default user name centos.
- Go to the AWS Console > EC2 Console.
- From the IPV4 Public IP field, copy the proxy server IP.
- From the Key pair name field, see the key pair associated with the proxy server.
- Using an SSH client (for example, Putty), connect to the proxy server. For detailed steps to connect to an EC2 instance, see AWS documentation.
- Specify the hostname or IP.
- Provide the key pair you had associated with the proxy server.
- Login with default username (for centos proxy, use username centos, or for Ubuntu proxy, use username ubuntu) and press enter when prompted for a password.
- Switch to sudo role.
sudo su
- Stop Druva services.
/etc/init.d/Phoenix stop
- Check if the Druva related process is not running.
ps -ef| grep -i phoenix
- To Manually stop the Druva services, run the following command:
Kill -9 <PID>
- Edit the Druva configuration file.
vi /etc/Phoenix/DR/Phoenix.cfg
- Add below parameter ( to avoid the automatic termination of failover instance).
Add DEBUG_TW = True
Note: In case of DR failover job failure, the failover instance is AWS is terminated by default.
- Update the DEBUGLEVEL value from 0 to 9.
- Save the Druva configuration file.
- Start the Druva services.
/etc/init.d/Phoenix start
- Initiate the DR failover again.