We have 3-4 Windows 10 clients running SeaDrive 2.0.8 and two libraries of 2 TB in total. Sync on demand is crucial to us since we work with a lot of documents that contain many links. Unfortunately we suffer from lots of conflict files for no apparent reason. We can for sure say that only a single person worked on the files in question. The log entries for the conflicts are very thin
Generating conflict file path/to/dir/containing/conflict/file/example (SFConflict email@example.com 2020-12-17-13-11-22).indd in repo 123456-f34a-4327-99a7-5ebdfac3398b.
However, we find many more errors in the logs that are kind of worrying:
[12/17/20 15:58:36] Seadrive daemon process crashed with code -1073740940 [12/17/20 15:58:37] failed to write to named pipe: The pipe is being closed. [12/17/20 15:58:37] failed to send rpc call: No error [12/17/20 15:58:37] failed to get upload progress: Transport Error [12/17/20 15:58:37] failed to write to named pipe: The pipe is being closed.
And so forth…