Skip to main content


 

 

How can we help you?

 

Druva Documentation

How to enable or disable debug logging for Phoenix File Server Agent

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

This article applies to:

  • Product edition: Phoenix
  • OS: Windows and Linux

Overview

This article describes the procedure to enable and disable debug logging for Hybrid Workloads Agent Client service. Ensure that there are no backup or restore jobs scheduled to run for the File server while enabling or disabling debug logging for the agent. Phoenix requires you to cancel all jobs that are currently running for the File server, before performing the following tasks.

Enable and disable debug logging for a Phoenix File Server Agent

Enable debug logging on Windows server

  1. Open Services console and stop Hybrid workloads Agent client service.
  2. Open Task Manager and kill all Druva or Phoenix related processes.
  3. Take a backup of the Phoenix.cfg file located at C:\ProgramData\Phoenix\FS.
  4. Open the Phoenix.cfg file in Notepad.
  5. Look for the DEBUGLEVEL flag and change the value from DEBUGLEVEL = 0 to DEBUGLEVEL = 9. 
  6. Save the changes.
  7. Start Hybrid workloads Agent client service and initiate the backup or the restore job.

Disable debug logging on Windows server

  1. Open Services console and stop Hybrid workloads Agent client service.
  2. Open Task Manager and kill all Druva or Phoenix related processes.
  3. Take a backup of the Phoenix.cfg file located at C:\ProgramData\Phoenix\FS.
  4. Open the Phoenix.cfg file in Notepad.
  5. Look for the DEBUGLEVEL flag and change the value from DEBUGLEVEL = 9 to DEBUGLEVEL = 0. 
  6. Save the changes.
  7. Start Hybrid workloads Agent client service and initiate the backup or the restore job.

Enable debug logging on Linux server

  1. Open the terminal with administrator rights and stop the Phoenix Agent service using the following command:
    /etc/init.d/Phoenix stop
  2. Verify if any Phoenix processes are still running. If any process is still found running, kill the process with the following command:
    ps -ef| grep -i Phoenix
    Kill -9 <process id>
  3. Browse to /etc/Phoenix/FS/Phoenix.cfg and take backup of the Phoenix.cfg file.
  4. Open the Phoenix.cfg file in the VI editor and change the value of DEBUGLEVEL = 0 to DEBUGLEVEL = 9.
  5. Save-Quit the changes.
  6. Start Phoenix Agent Client Service and initiate the backup or the restore job.
    /etc/init.d/Phoenix start

Disable debug logging on Linux server

  1. Open the terminal with the administrator rights and stop the Phoenix Agent service using the following command:
    /etc/init.d/Phoenix stop
  2. Verify if any Phoenix processes are still running. If any process is still found running, kill the process with the following command:
    ps -ef| grep -i Phoenix
    Kill -9 <process id>
  3. Browse to /etc/Phoenix/FS/Phoenix.cfg and take the backup of the Phoenix.cfg file.
  4. Open the Phoenix.cfg file in the VI editor and change the value of DEBUGLEVEL = 9 back to DEBUGLEVEL = 0.
  5. Save-Quit the changes.
  6. Start Phoenix Agent Client Service and initiate the backup or the restore job.
    /etc/init.d/Phoenix start

Collect the Logs from Linux server

After job completes or terminates then collect the below logs and zip in one folder

  1. Logs from server location:

    1. /var/log/Phoenix

    2. /var/log/messages

  2. Failed or Terminated Job Logs from Phoenix Management Console.

Collect the Logs from Windows server

After job completes or terminates then collect the below logs and zip in one folder

  1. Logs from server location:

    1. C:\ProgramData\Phoenix

    2. Windows Application and System event logs in the .evt or .evtx format.

  2. Failed or Terminated Job Logs from Phoenix Management Console.

Upload the Logs

  • If the zip/log file is below 4.5 MB then you can directly send us by attaching it to the email or uploading via support portal on the case.

  • Else, Go to https://upload.druva.com/

    • Enter the case number in the Ticket Number field.

    • Click Choose File and add the compressed files to upload.

    • Click Upload. 

    • Notify the support engineer about the logs uploaded through Portal by responding to the ongoing support ticket.

See also: How to collect the detailed job logs - Druva Documentation