Drive Client Issue after moving Directories

Hi there,

We’re using the Dirve Client 0.8.4 application since a couple of month without any problems.
Today an user moves several directories from a shared bibliothek to a private bibliothek.

After that the Drive Client applications shows an internal error.
Upgrade to 0.9.1 does not fix the issue.

The log file displays the following columns:

[04/27/18 09:18:57] sync-mgr.c(570): Repo ‘my_storage’ sync state transition from ‘synchronized’ to ‘uploading’.
[04/27/18 09:18:57] http-tx-mgr.c(3878): Upload with HTTP sync protocol version 1.
[04/27/18 09:18:57] http-tx-mgr.c(1145): Transfer repo ‘6e731f8d’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[04/27/18 09:18:57] http-tx-mgr.c(1145): Transfer repo ‘6e731f8d’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[04/27/18 09:18:58] http-tx-mgr.c(1145): Transfer repo ‘6e731f8d’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[04/27/18 09:18:58] http-tx-mgr.c(1145): Transfer repo ‘6e731f8d’: (‘normal’, ‘fs’) --> (‘normal’, ‘data’)
[04/27/18 09:19:00] http-tx-mgr.c(3393): Bad response code for PUT htttps://xxx.xxx.xx/seafhttp/repo/6e731f8d-a5a0-403a-8206-cc3cab287c44/block/aeb42c027e2ab941988bd27b37ab7922ab61d004: 500.
[04/27/18 09:19:00] http-tx-mgr.c(875): libcurl failed to PUT htttps://xxx.xxx.xx/seafhttp/repo/6e731f8d-a5a0-403a-8206-cc3cab287c44/block/b99982996f8a55ed4b0cb1d25212a171e41e172c: Operation was aborted by an application callback.
[04/27/18 09:19:00] http-tx-mgr.c(875): libcurl failed to PUT htttps://xxx.xxx.xx/seafhttp/repo/6e731f8d-a5a0-403a-8206-cc3cab287c44/block/ba2a0287b06b75202a7d9ffec6e67beb208cb8c8: Operation was aborted by an application callback.
[04/27/18 09:19:00] http-tx-mgr.c(3393): Bad response code for PUT htttps://xxx.xxx.xx/seafhttp/repo/6e731f8d-a5a0-403a-8206-cc3cab287c44/block/e7b36a3477a120753e2ce92b0d4e42c59c2ebf6b: 500.
[04/27/18 09:19:00] http-tx-mgr.c(1145): Transfer repo ‘6e731f8d’: (‘normal’, ‘data’) --> (‘error’, ‘finished’)
[04/27/18 09:19:00] sync-mgr.c(604): Repo ‘my_storage’ sync state transition from uploading to ‘error’: ‘Error occured in upload.’.

Any ideas ?

Kai

I suggest the following steps:

  1. Copy files to local disk that have not been uploaded to the server
  2. Logout current account, during the logout, choose cleaning local data, then login again.
1 Like