- Server: Professional Edition v. 7.1.6
- Client: SeaDrive v. 2.0.13
- Platform: Mostly Windows, but also Mac and Linux
Situation: When a user makes relevant changes to the directory structure of a library, it is hard for the user to understand what it is going on. Said in a different way, the user doesn’t know what the SeaDrive client is doing and how long it will take to complete. It happens that an apparently simple and quick operation like “Always keep on this device” for a small directory is launched, but the “running arrows” icon in the System Tray keep spinning without any output on the “Transfer progress” (either upload/download). During this syncing activity the user is prevented any access to the files.
The seadrive.log has been checked, but it doesn’t give enough information, in particular about what is left to do and the syntax looks hard to understand, even for a Sysadmin.
In some occasions the client looked like stuck and in the log (image attached) the following message repeats:
"The last hydrate worker has not been complted"
(verbatim, the spelling error is in the log)
and the message "
cancel fetch file... " appears one per minute, probably going on for each one of the thousands of files involved in the operation.
Question 1: What is the problem?
Question 2: How can we understand if there is an error or the SeaDrive Client is working smoothly? Do exist other user-friendly ways to check the activities the SeaDrive client is carrying out exist?
Question 3: How can we monitor the activity in progress, also on the cache during creation or update activities?