This article applies to:
Product edition: Phoenix
Overview
This article describes the procedure to enable and disable debug logging to troubleshoot the DRaaS issues.
Enable and disable debug logging for DRaaS
Enable debug logging
SSH into the AWS proxy.
Run: sudo su -
Stop Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix stopAgent Version 7.x.x:
service Druva-EnterpriseWorkloads stopVerify if any Druva or Phoenix related processes.
Agent Version 6.x.x:
ps -ef| grep -i PhoenixAgent Version 7.x.x:
ps -ef | grep -i EnterpriseWorkloadsIf any process is still found running, kill the process with the following command:
Kill -9 <process id>
Take a backup of the Configuration File
Agent Version 6.x.x:
/etc/Phoenix/DR/Phoenix.cfgAgent Version 7.x.x:
/etc/Druva/EnterpriseWorkloads/Config.yamlOpen the file in VI editor and change the debug value from 0 to 9
Agent Version 6.x.x: change the value from
DEBUGLEVEL = 0 to DEBUGLEVEL = 9Agent Version 7.x.x: change the value from
debug_level: 0 to debug_level: 9Save the changes.
Then Start Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix startAgent Version 7.x.x:
service Druva-EnterpriseWorkloads startInitiate the backup or the restore job.
Disable debug logging
SSH into the AWS proxy.
Run: sudo su -
Stop Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix stopAgent Version 7.x.x:
service Druva-EnterpriseWorkloads stopVerify if any Druva or Phoenix related processes.
Agent Version 6.x.x:
ps -ef| grep -i PhoenixAgent Version 7.x.x:
ps -ef | grep -i EnterpriseWorkloadsIf any process is still found running, kill the process with the following command:
Kill -9 <process id>Take a backup of the Configuration File
Agent Version 6.x.x:
/etc/Phoenix/DR/Phoenix.cfgAgent Version 7.x.x:
/etc/Druva/EnterpriseWorkloads/Config.yamlandOpen the file in VI editor and change the debug value from 9 to 0
Agent Version 6.x.x: change the value from
DEBUGLEVEL = 9 to DEBUGLEVEL = 0Agent Version 7.x.x: change the value from
debug_level: 9 to debug_level: 0Save the changes.
Then again start Agent Client Service.
Agent Version 6.x.x:
/etc/init.d/Phoenix startAgent Version 7.x.x:
service Druva-EnterpriseWorkloads startInitiate the backup or the restore job.
Upload files
After the job finishes or terminates, zip and upload following files to the case:
Zip of /var/log/Phoenix from the AWS proxy.
System logs from the AWS proxy /var/log/messages.
Job logs of the failed or terminated DRaaS job.
Output of VMImportChecker script (optional).
Create a directory in /home using the following command:mkdir /home/DruvaLogs
Copy the log files using the following command:cp -r /var/log/Phoenix /home/DruvaLogs
Change the permission of the copied files using the following command:chmod -R 755 /home/DruvaLogs
Connect to the proxy using the WinSCP tool and copy /home/DruvaLog directory to your local machine.
Copy system logs /var/log/ messages.
Zip all the files and upload them to the required portal.