Overview
This article explains how to enable debug logging on the Druva inSync client across Windows, macOS, and Linux. Debug logging is typically requested by the Druva Support team to capture verbose diagnostic information when troubleshooting backup or restore issues.
Prerequisites
Before you begin, make sure you have the following:
Druva inSync client installed on your device
Administrator or root-level access to your machine
A backup copy of the inSync.cfg file (see the note below before making any changes)
⚠️ Important: Back up your inSync.cfg file before making any changes. This file contains all client-related configuration settings. A corrupt or incorrectly modified file can cause the inSync client to malfunction.
Procedure
Windows
Step 1: Stop the inSync service and processes
Open the Windows Services panel (services.msc) and stop the Druva Client service.
Open Task Manager, locate all running inSync processes, and end them.
Step 2: Locate the configuration file
Navigate to the appropriate inSync.cfg file based on your client version:
Client version | File path |
inSync 5.5 and below | C:\inSync4\users\<username>\inSync.cfg |
inSync 5.8 and above | C:\ProgramData\Druva\inSync4\users\<username>\inSync.cfg |
Replace <username> with your Windows username.
Step 3: Enable debug logging
Open inSync.cfg in a text editor (for example, Notepad).
Locate the DEBUGLEVEL parameter and set its value to 9:
DEBUGLEVEL=9
3. Save and close the file.
Step 4: Restart the Druva client service
Return to the Services panel and start the Druva Client service again.
macOS
Step 1: Stop the inSync process
Open Terminal.
Run the following command to stop the inSync client:
killall inSync
Step 2: Locate and open the configuration file
In Terminal (or Finder with hidden files visible), navigate to:
/Users/<username>/Library/Application Support/inSync/inSync.cfg
Replace <username> with your macOS username. 2. Open inSync.cfg in a text editor.
Step 3: Enable debug logging
Locate the DEBUGLEVEL parameter and set its value to 9:
DEBUGLEVEL=9
2. Save and close the file.
Step 4: Relaunch the inSync application
Open the Druva inSync application from your Applications folder or menu bar.
Linux
Step 1: Stop the inSync daemon
Open a terminal and run the following command to stop the Druva client daemon:
killall inSync
Step 2: Locate and open the configuration file
Navigate to the following directory and open inSync.cfg:
/home/<username>/.inSync/inSync.cfg
Replace <username> with your Linux username.
Step 3: Enable debug logging
Locate the DEBUGLEVEL parameter and set its value to 9:
DEBUGLEVEL=9
2. Save and close the file.
Step 4: Relaunch the inSync application
Start the Druva inSync application or daemon as you normally would on your Linux distribution.
Troubleshooting
Issue | Possible cause | Resolution |
The Druva Client service does not start after changes | inSync.cfg may have a syntax error or become corrupt | Restore the backup copy of inSync.cfg you made before editing, then repeat the steps carefully |
inSync.cfg file not found at the expected path | You may be using a non-standard installation or a client version that uses a different path | Search for inSync.cfg manually, or contact Druva Support for guidance [NEEDS VERIFICATION] |
killall inSync returns "No matching processes" on macOS or Linux | The inSync client is already stopped | Proceed directly to editing the configuration file |
Debug logs are not being generated after the change | The DEBUGLEVEL value may not have been saved correctly | Re-open inSync.cfg and confirm DEBUGLEVEL=9 is present with no extra spaces or characters |
📝 Note
Ensure you take a backup of the inSync.cfg file before making any changes. This is an important file as it contains all the client related configuration and could cause issues if corrupt.