SeaDrive 2.0.2 is ready!

Win 10, 1709 (as corporate PC we are stalled on this version for a while)

I tested quite a few times and it works on my computer. Can you check seadrive.log for error messages?

Did some further testing: 2.0.2. works fine on my private PC (Win 10, 1909) - so access to library (on an Ubuntu Server) works fine. Deinstalled 2.0.2 on my non-working PC (Win 10,1709) and installed again 2.0.1. Seadrive works without issue :-). Whatever was changed in .2 might not work with older Win10?

The Windows Cloud API, a MS technology that SeaDrive 2.0 uses, was introduced in Windows 1709. As a consequence, SeaDrive 2.0 will produce errors in Windows 1703 and earlier.

So should be okay as I’m running 1709. But looks like something introduced with 2.0.2. is more advanced and needs an even newer Win10. But that’s ok. I can leave with 2.0.1 until same day our Win10 will be updated to something newer.

@Jonathan
I changed the language a few times. This is the result.

Language: German

Language: switched to English

Language: switched to Chinese

Language: switched to French

Language: switched to German

The seadrive.log does not contain any errors. There are the normal “Repo ‘abc’ sync state transition from x to y” messages. When I start the client, this is the log output:

[05/29/20 12:11:23] [05/29/20 12:11:23] recevied a pipe cmd, type 1 for syncroot C:\Users\TD\seadrive_root\5f369c26
send an unwatch command, syncroot C:\Users\TD\seadrive_root\5f369c26
[05/29/20 12:11:25] Starting SeaDrive client 2.0.2
[05/29/20 12:11:25] rpc server started.
[05/29/20 12:11:25] Done: add_all_to_iocp
[05/29/20 12:11:27] start to serve on pipe client
[05/29/20 12:11:28] start to serve on pipe client
[05/29/20 12:11:28] switching account to https://cloud.datamate.org td@datamate.org.
[05/29/20 12:11:29] start to serve on pipe client
[05/29/20 12:11:29] switching account to https://cloud.datamate.org td@datamate.org.
[05/29/20 12:11:46] [05/29/20 12:11:46] recevied a pipe cmd, type 0 for syncroot C:\Users\TD\seadrive_root\5f369c26
send a watch command, syncroot C:\Users\TD\seadrive_root\5f369c26
[05/29/20 12:11:46] [wt mon] add watch for syncroot C:\Users\TD\seadrive_root\5f369c26
[05/29/20 12:11:46] All repo fs trees are loaded.

This is the seafile-gui.log:

[05/29/20 12:06:04] loaded 1 accounts
[05/29/20 12:06:04] starting applet rpc service
[05/29/20 12:06:04] applet rpc service started
[05/29/20 12:06:05] seadrive gui started
[05/29/20 12:06:05] Using cache directory: C:/Users/TD/seadrive_root
[05/29/20 12:06:05] starting seadrive daemon: seadrive.exe “-d” “C:/Users/TD/seadrive/data” “-l” “C:/Users/TD/seadrive/logs/seadrive.log” “-L” “de_de” “C:\Users\TD\seadrive_root”
[05/29/20 12:06:08] Unable to get config value download_limit: Config not exists
[05/29/20 12:06:08] Unable to get config value upload_limit: Config not exists
[05/29/20 12:06:09] Switched to account https://cloud.datamate.org TD@datamate.org c239c18
[05/29/20 12:06:09] Switched to account https://cloud.datamate.org TD@datamate.org c239c18
[05/29/20 12:07:35] Unable to get config value download_limit: Config not exists
[05/29/20 12:07:35] Unable to get config value upload_limit: Config not exists
[05/29/20 12:09:30] Unable to get config value download_limit: Config not exists
[05/29/20 12:09:30] Unable to get config value upload_limit: Config not exists
[05/29/20 12:09:36] Unmounting before exit
[05/29/20 12:09:36] app event loop exited with 0

[05/29/20 12:09:36] [Daemon Mgr] stopping seadrive daemon
[05/29/20 12:09:36] Seadrive daemon process exited normally with code 0
[05/29/20 12:09:38] loaded 1 accounts
[05/29/20 12:09:38] starting applet rpc service
[05/29/20 12:09:38] applet rpc service started
[05/29/20 12:09:38] seadrive gui started
[05/29/20 12:09:38] Using cache directory: C:/Users/TD/seadrive_root
[05/29/20 12:09:38] starting seadrive daemon: seadrive.exe “-d” “C:/Users/TD/seadrive/data” “-l” “C:/Users/TD/seadrive/logs/seadrive.log” “C:\Users\TD\seadrive_root”
[05/29/20 12:09:41] Unable to get config value download_limit: Config not exists
[05/29/20 12:09:41] Unable to get config value upload_limit: Config not exists
[05/29/20 12:09:42] Switched to account https://cloud.datamate.org TD@datamate.org c239c18
[05/29/20 12:09:42] Switched to account https://cloud.datamate.org TD@datamate.org c239c18
[05/29/20 12:11:13] Unable to get config value download_limit: Config not exists
[05/29/20 12:11:13] Unable to get config value upload_limit: Config not exists
[05/29/20 12:11:23] Unmounting before exit
[05/29/20 12:11:23] app event loop exited with 0

[05/29/20 12:11:23] [Daemon Mgr] stopping seadrive daemon
[05/29/20 12:11:24] Seadrive daemon process exited normally with code 0
[05/29/20 12:11:25] loaded 1 accounts
[05/29/20 12:11:25] starting applet rpc service
[05/29/20 12:11:25] applet rpc service started
[05/29/20 12:11:25] seadrive gui started
[05/29/20 12:11:25] Using cache directory: C:/Users/TD/seadrive_root
[05/29/20 12:11:25] starting seadrive daemon: seadrive.exe “-d” “C:/Users/TD/seadrive/data” “-l” “C:/Users/TD/seadrive/logs/seadrive.log” “-L” “zh_cn” “C:\Users\TD\seadrive_root”
[05/29/20 12:11:28] Unable to get config value download_limit: Config not exists
[05/29/20 12:11:28] Unable to get config value upload_limit: Config not exists
[05/29/20 12:11:29] Switched to account https://cloud.datamate.org rdb@datamate.org c239c18
[05/29/20 12:11:29] Switched to account https://cloud.datamate.org rdb@datamate.org c239c18
[05/29/20 12:12:29] Unable to get config value download_limit: Config not exists
[05/29/20 12:12:29] Unable to get config value upload_limit: Config not exists
[05/29/20 12:12:41] Unmounting before exit
[05/29/20 12:12:41] app event loop exited with 0

The last block is repeated two more times with a different language set in the start command.

Two observations:
a.) In the second block, the start command is executed without “-L” parameter.
b.) All blocks contain an “unmounting before exit” message. I thought there was no more unmounting?

We’ll test on 1709.

We’ll take note of that.

[05/29/20 16:13:29] Failed to connect to named pipe: 
[05/29/20 16:13:29] Exiting with error: internal error: failed to connect to seadrive daemon
[05/29/20 16:13:29] Seadrive daemon process crashed with code -1073741819 
[05/29/20 16:13:34] Trying to restart seadrive daemon

I have the same problem on a 1809.

Unable to start Seadrive 2.0.2.

same error message.
By cons if I reinstall a clean version 1809 of Windows Seadrive 2.0.2 works perfectly.

It seems a very sly bug


Seadrive 2.0.1 seems to work with it in any state of Microsoft Windows;)

Hi, minor issue, there is no way to mark sync errors as read in the “File sync errors” dialogue box. It would be nice, otherwise, the drive icon in the taskbar is always showing an error making me think there is a new sync issue.

Also, the time in the dialogue box always shows as “Just now”. Even if it happened long ago.

I can confirm that there are apps where I cannot see or access Seafile but I can see and access other cloud providers like OneDrive or Dropbox.

1 Like

It seems the seadrive daemon crashed. Do you have any log messages in seadrive.log? Any dump file in logs/dump?

When was support multiple accounts added?

There are different Seafile accounts behind either node.

Only the current chosen account is active. The other ones are not synced when you switch to the current account. In previous version the account will be unregistered from explorer, but that would cause unexpected file removal. CFAPI is not designed to be unregistered frequently. So in 2.0.2 the previous account will be left there. They will only be unregister when you logout and clear cache, or delete the account.

I’m running seafile client and seadrive (2.0.2) on the same computer - seafile to sync key libraries in frequent use, and seadrive to allow access to infrequent\archival libraries\files if needed.

I am finding that seadrive creates a lot of SFConflict files. Typically if I edit a file in a seafile client sync’ed directory, after seafile syncs the file to the server, seadrive will create a SFConflict file in its copy of the library (even though (a) the seadrive copy of the file hasn’t been touched, and (b) the seadrive had not even synced the contents of the file - it previously had just the stub).

Matthew

@mdovey Can you share your seadrive.log?

Hi @mdovey

Thank you for the log. Have you ever logout/delete an account? Or have you ever delete a file in the virtual drive location when SeaDrive is not running?

After the issues with 2.0.1 deleting files. I uninstalled that version of seadrive and deleted its directories (after the uninstallation).

However, I’ve not logged out\deleted an account or deleted a file in the location whilst SeaDrive isn’t running (or for that matter whilst it is), since I installed 2.0.2.

Matthew

Hi,
I just uninstalled the seadrive version 2.0.2 but I still have the shortcut on my windows explorer. Is there a way to remove it?
Thanks

clic droit et supprime le dossier…