Troubleshooting inSyncSyncer.log file bloating issue
This article applies to:
- OS: Windows
- Product edition: inSync Client 5.9.5 r54843
The total amount of free space in C drive may start dropping.
There are two symptoms due to which the inSyncSyncer.log file may bloat.
- There is a zip file present in C:\inSync4\Users or C:\ProgramData\Druva\inSync4\Users
- The client was downgraded, due to any reason, without removing inSync preferences (user related inSync settings).
Whenever the user device starts, Druva inSync services are loaded automatically. With this process, inSync also performs an API call which checks for the presence of local configuration.
With v5.9.5 r54843, a race condition is observed between API calls when checking the local configuration. Due to this race condition, inSync gets an exception and this exception is logged under inSyncSyncer.log.
Since the frequency for this exception is too high, the inSyncSyncer file starts to bloat. You can see the following entry under inSyncSyncer.log file:
NameError: global name 'inSyncConfig' is not defined
Upgrade to the latest version of inSync Client. Get the latest client from the download link.
Note: The above issue is only seen on Windows only. The inSync Client on Mac and Linux are not affected by this issue.