This article applies to:
OS: Windows and Linux
Product version: inSync Server running onWindows and Linux.
Overview
While troubleshooting a scenario with inSync Client, the Druva support team might request to enable debug logging to capture verbose information. Adebug logcan record database operations, system processes, and errors that occur when executing a backup/restore.Based on the OS, the following are the steps to enable debug logging.
Windows
Perform the following steps to enable debug logging on Windows OS.
Stop the inSync services on the inSync server.
inSync 5.8 and above
Druva inSync Master Config Server
Druva inSync Master Control Panel
Druva inSync Master Sync Server
Edit the inSync Server configuration file "inSyncServer.cfg" located under
C
:\Programdata\Druva\inSyncCloud\inSyncServer4
π Note
β For inSync server 5.3.x and below the β inSyncServer.cfgβ is located under C:\inSyncServer4\
directory.
Modify the value for the following entry:DEBUGLEVEL = 9
Save the configuration file.
Start the Druva inSync server services.
π Note
βChange the DEBUGLEVEL to 0 again after collecting the debug logs for analysis.
Linux
Perform the following steps to enable debug logging on Linux OS.
π Note
β To perform the following steps log in as a root or type sudo before each of the following command and provide the root password when prompted.
Stop the inSync services on the inSync server using the following command.
β
βinSync 5.8 and later versions
β/etc/init.d/inSyncMasterAll stop
Query if the inSync server processes are still running using below command.
βps -aux | grep -i insync
Once the inSync process is stopped,edit the inSync Server configuration file "inSyncServer.cfg" located under
/etc/inSyncServer for
inSync 5.3.1 and older versions. And/etc/inSyncCloud/
inSyncServer for inSync 5.4 and above versions.Modify the value for the following entry:DEBUGLEVEL = 9
Save the configuration file.
Start the Druva inSync server services using the following command.
βinSync 5.8 and later versions
β/etc/init.d/inSyncMasterAll start
π Note
βChange the DEBUGLEVEL to 0 again after collecting the debug logs for analysis.