Skip to main content


 

 

How can we help you?

 

 
Druva Documentation

How to enable CDEBUG for inSync client?

Heads up!

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

Overview

The Druva Support team might request you to enable CDEBUG logging to capture stack trace information. A CDEBUG stack trace is a report of the active stack frames at a certain point in time during the execution of a program.

Based on the OS, perform the following steps to enable CDEBUG logging.

Windows

  1. Check if the backup is already running for the affected user, then continue with step 2, else initiate the backup for one of the client machine facing issue.
  2. Create CDEBUG folder on the C: drive.
  3. Check the root of C: drive to ensure that stack dumps are getting created. The file nomenclature will be "<PID>stack.txt".
  4. Delete the CDEBUG folder after 3 minutes of creating the CDEBUG folder.
  5. Open CMD and run the following command to get the process ids of all inSync processes:
    tasklist | find "inSync" > tasklist.txt
  6. Collect the tasklist.txt and all the <PID>stack.txt files and share them with Druva Support.
  7. Once the CDEBUG folder is created, the additional debug log files will get created in the following folder on the user's device -

    C:\ProgramData\Druva\inSync4\Users\<username>\logs

    And not in the C:\CDEBUG folder.

    The CDEBUG folder is to enable debug logs so that additional logs can get created.

Linux

  1. Create the CDEBUG directory using the following command
    mkdir /tmp/CDEBUG
  2. Modify the permission of the CDEBUG directory as follows
    chmod 775 /tmp/CDEBUG
  3. Check the /tmp directory to ensure that stack dumps are getting created. The file nomenclature will be "<PID>stack.txt".
  4.  Delete the CDEBUG folder after 3 minutes of creating the CDEBUG folder.
  5. Check the process id's for all the inSync processes by using the following command 
    ps aux | grep inSync | grep -v "grep" > ps.log
  6. Restart the services.
  7. Collect the tasklist.txt, ps.log & all the <PID>stack.txt files and share with Druva Support.
  8. Once the CDEBUG folder is created, the additional debug log files will get created in the following folder on the user's device -

    /home/<username>/.inSync/logs

MAC

  1. Create a new folder named CDEBUG on the root of the following directory /Users/<username>/Library/Application Support/inSync
  2. Check the root of inSync folder to ensure that stack dumps are getting created. The file nomenclature will be "<PID>stack.txt".
  3. Delete the CDEBUG folder after 3 minutes of creating the CDEBUG folder.
  4. Collect all the <PID>stack.txt files and share with Druva Support.
  5. Once the CDEBUG folder is created, the additional debug log files will get created in the following folder on the user's device -

    /Users/<username>/Library/Application Support/inSync/logs

Note: Ensure you delete the CBEDUG folder after collecting the generated stack files.