Seadrive Failed to get sync info from server

Server: seafile-pro-server 6.2.9 on CentOS 7.
Seadrive client: 0.8.6

Yesterday we had a power failure which affected the server.
Seadrive isn’t working as expected anymore after that.

At first i got this error:

[03/29/18 15:16:13] sync-mgr.c(595): Repo ‘Kingsland_Amsterdam_18’ sync state transition from downloading to ‘error’: ‘Error occured in download.’.
[03/29/18 15:16:44] sync-mgr.c(561): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/29/18 15:16:44] [03/29/18 15:16:44] sync-mgr.c(561): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘get sync info’ to ‘downloading’.
http-tx-mgr.c(4834): Download with HTTP sync protocol version 2.
[03/29/18 15:16:44] http-tx-mgr.c(1145): Transfer repo ‘ca5a6553’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[03/29/18 15:16:44] http-tx-mgr.c(1145): Transfer repo ‘ca5a6553’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[03/29/18 15:16:44] http-tx-mgr.c(1145): Transfer repo ‘ca5a6553’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[03/29/18 15:16:44] http-tx-mgr.c(4179): Bad response code for GET http://***:8082/repo/ca5a6553-a700-428b-9d11-6fc0ef3ad2bb/fs-id-list/?server-head=f9bea2fc7baff91e0e76c73818f9e1fc5a42a300&client-head=929d8c4ecb49bea2d5095cb7160df07b1617e647&dir-only=1: 500.
[03/29/18 15:16:44] http-tx-mgr.c(4862): Failed to get fs id list for repo ca5a6553 on server http://
:8082.
[03/29/18 15:16:44] http-tx-mgr.c(1145): Transfer repo ‘ca5a6553’: (‘normal’, ‘fs’) --> (‘error’, ‘finished’)
[03/29/18 15:16:44] sync-mgr.c(595): Repo ‘Kingsland_Amsterdam_18’ sync state transition from downloading to ‘error’: ‘Error occured in download.’.

Then i checked if any libraries are corrupt with ./seaf-fsck.sh.
And indeed, repo ‘Kingsland_Amsterdam_18’ was corrupt. Seahub showed an empty library so I ran ./seaf-fsck.sh – repair [repo-id] and fixed the library. Seahub was now showing files again.
On Seadrive however I now get the following error:

[03/30/18 11:59:10] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 11:59:10] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 11:59:41] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 11:59:41] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 12:00:12] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 12:00:12] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 12:00:44] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 12:00:44] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 12:01:16] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 12:01:16] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 12:01:47] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 12:01:47] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 12:02:18] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 12:02:18] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.

Also there are other computers with seadrive which can only read files, but can’t write them. I’m waiting for their logfiles as we speak.

Is there anyone that can provide me with a solution or a step in the right direction?

I just received a logfile from another seadrive client and it seems to happen only at the repo ‘Kingsland_Amsterdam_18’.
They also get Input/output errors:

[03/30/18 09:45:58] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:45:58] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:46:29] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:46:29] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:54:44] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:54:44] http-tx-mgr.c(654): libcurl failed to GET http://:8082/repo/ca5a6553-a700-428b-9d11-6fc0ef3ad2bb/commit/HEAD: Couldn’t resolve host name.
[03/30/18 09:54:44] http-tx-mgr.c(654): libcurl failed to GET http://
:8000/api2/repos/: Couldn’t resolve host name.
[03/30/18 09:54:44] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:55:15] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:55:15] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:55:46] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:55:46] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:56:17] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:56:17] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:56:48] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:56:48] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:56:59] http-tx-mgr.c(4502): Bad response code for POST http://:8082/repo/ca5a6553-a700-428b-9d11-6fc0ef3ad2bb/pack-fs/: 403.
[03/30/18 09:56:59] file-cache-mgr.c(469): Failed to get file object 3a79bdd22b61c2ad43f95d5e133f29bd4ea80970 of ca5a6553-a700-428b-9d11-6fc0ef3ad2bb/KINAM8 - Buiten - Mainstage V1.pdf from server http://
:8082.
[03/30/18 09:57:05] file-cache-mgr.c(1092): Read cache file C:/Users/guus_/seadrive/data\file-cache\ca5a6553-a700-428b-9d11-6fc0ef3ad2bb\KINAM8 - Buiten - Mainstage V1.pdf timeout.
[03/30/18 09:57:05] dokan-ops.c(1962): Failed to read \Kingsland_Amsterdam_18\KINAM8 - Buiten - Mainstage V1.pdf: Input/output error
[03/30/18 09:57:05] dokan-ops.c(63): ReadFile \Kingsland_Amsterdam_18\KINAM8 - Buiten - Mainstage V1.pdf: IO error
[03/30/18 09:57:10] file-cache-mgr.c(1092): Read cache file C:/Users/guus_/seadrive/data\file-cache\ca5a6553-a700-428b-9d11-6fc0ef3ad2bb\KINAM8 - Buiten - Mainstage V1.pdf timeout.
[03/30/18 09:57:10] dokan-ops.c(1962): Failed to read \Kingsland_Amsterdam_18\KINAM8 - Buiten - Mainstage V1.pdf: Input/output error
[03/30/18 09:57:10] dokan-ops.c(63): ReadFile \Kingsland_Amsterdam_18\KINAM8 - Buiten - Mainstage V1.pdf: IO error
[03/30/18 09:57:11] http-tx-mgr.c(4502): Bad response code for POST http://:8082/repo/ca5a6553-a700-428b-9d11-6fc0ef3ad2bb/pack-fs/: 403.
[03/30/18 09:57:11] file-cache-mgr.c(469): Failed to get file object 2fed5ed2545ffdb9c813f6346c2d413ab9c780b9 of ca5a6553-a700-428b-9d11-6fc0ef3ad2bb/KINAM8 - Buiten - Vipdecks op trap V1.pdf from server http://
:8082.
[03/30/18 09:57:17] file-cache-mgr.c(1092): Read cache file C:/Users/guus_/seadrive/data\file-cache\ca5a6553-a700-428b-9d11-6fc0ef3ad2bb\KINAM8 - Buiten - Vipdecks op trap V1.pdf timeout.
[03/30/18 09:57:17] dokan-ops.c(1962): Failed to read \Kingsland_Amsterdam_18\KINAM8 - Buiten - Vipdecks op trap V1.pdf: Input/output error
[03/30/18 09:57:17] dokan-ops.c(63): ReadFile \Kingsland_Amsterdam_18\KINAM8 - Buiten - Vipdecks op trap V1.pdf: IO error
[03/30/18 09:57:19] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:57:19] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.
[03/30/18 09:57:22] file-cache-mgr.c(1092): Read cache file C:/Users/guus_/seadrive/data\file-cache\ca5a6553-a700-428b-9d11-6fc0ef3ad2bb\KINAM8 - Buiten - Vipdecks op trap V1.pdf timeout.
[03/30/18 09:57:22] dokan-ops.c(1962): Failed to read \Kingsland_Amsterdam_18\KINAM8 - Buiten - Vipdecks op trap V1.pdf: Input/output error
[03/30/18 09:57:22] dokan-ops.c(63): ReadFile \Kingsland_Amsterdam_18\KINAM8 - Buiten - Vipdecks op trap V1.pdf: IO error
[03/30/18 09:57:50] sync-mgr.c(569): Repo ‘Kingsland_Amsterdam_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[03/30/18 09:57:50] sync-mgr.c(603): Repo ‘Kingsland_Amsterdam_18’ sync state transition from get sync info to ‘error’: ‘Failed to get sync info from server.’.

The log of the client says there isn’t the libary anymore. Like you have sawn it on Seahub.

Yes the library was visible all the time in seahub, only after repairing it showed files again. I was also able to download these files, but seadrive (still) shows these errors

In the meantime i received another logfile from my client.
Seems the only problem for them is the I/O Errors.

[04/03/18 10:12:44] sync-mgr.c(569): Repo ‘Rijk_Zwaan_De_Lier’ sync state transition from ‘committing’ to ‘synchronized’.
[04/03/18 10:12:44] sync-mgr.c(569): Repo ‘Lakedance_17_aug’ sync state transition from ‘committing’ to ‘synchronized’.
[04/03/18 10:12:44] sync-mgr.c(569): Repo ‘ASOT_2017’ sync state transition from ‘committing’ to ‘synchronized’.
[04/03/18 10:12:44] sync-mgr.c(569): Repo ‘Tik_Tak_Beach_2018’ sync state transition from ‘get sync info’ to ‘downloading’.
[04/03/18 10:12:44] http-tx-mgr.c(4834): Download with HTTP sync protocol version 2.
[04/03/18 10:12:44] http-tx-mgr.c(1145): Transfer repo ‘c6e5e0ae’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[04/03/18 10:12:44] http-tx-mgr.c(1145): Transfer repo ‘c6e5e0ae’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[04/03/18 10:12:44] http-tx-mgr.c(1145): Transfer repo ‘c6e5e0ae’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[04/03/18 10:12:44] http-tx-mgr.c(1145): Transfer repo ‘c6e5e0ae’: (‘normal’, ‘fs’) --> (‘finished’, ‘finished’)
[04/03/18 10:12:44] sync-mgr.c(569): Repo ‘Tik_Tak_Beach_2018’ sync state transition from ‘downloading’ to ‘load repo’.
[04/03/18 10:12:44] sync-mgr.c(569): Repo ‘Tik_Tak_Beach_2018’ sync state transition from ‘load repo’ to ‘synchronized’.
[04/03/18 10:12:45] sync-mgr.c(569): Repo ‘Paaspop_18’ sync state transition from ‘synchronized’ to ‘get sync info’.
[04/03/18 10:12:45] sync-mgr.c(569): Repo ‘Paaspop_18’ sync state transition from ‘get sync info’ to ‘downloading’.
[04/03/18 10:12:45] http-tx-mgr.c(4834): Download with HTTP sync protocol version 2.
[04/03/18 10:12:45] http-tx-mgr.c(1145): Transfer repo ‘8ddb8df3’: (‘normal’, ‘init’) --> (‘normal’, ‘check’)
[04/03/18 10:12:45] http-tx-mgr.c(1145): Transfer repo ‘8ddb8df3’: (‘normal’, ‘check’) --> (‘normal’, ‘commit’)
[04/03/18 10:12:45] http-tx-mgr.c(1145): Transfer repo ‘8ddb8df3’: (‘normal’, ‘commit’) --> (‘normal’, ‘fs’)
[04/03/18 10:12:45] http-tx-mgr.c(1145): Transfer repo ‘8ddb8df3’: (‘normal’, ‘fs’) --> (‘finished’, ‘finished’)
[04/03/18 10:12:45] sync-mgr.c(569): Repo ‘Paaspop_18’ sync state transition from ‘downloading’ to ‘load repo’.
[04/03/18 10:12:45] sync-mgr.c(569): Repo ‘Paaspop_18’ sync state transition from ‘load repo’ to ‘synchronized’.
[04/03/18 10:13:37] dokan-ops.c(2326): Failed to set file 1fa24203-2bab-43e3-868d-8431b2700c93/Berekeningen hidden in repo tree.
[04/03/18 10:13:37] dokan-ops.c(63): SetFileAttributes \Brug_Amsterdamse_Bos_1\Berekeningen: IO error
[04/03/18 10:13:37] dokan-ops.c(2326): Failed to set file 1fa24203-2bab-43e3-868d-8431b2700c93/Ontwerpen hidden in repo tree.
[04/03/18 10:13:37] dokan-ops.c(63): SetFileAttributes \Brug_Amsterdamse_Bos_1\Ontwerpen: IO error
[04/03/18 10:13:37] dokan-ops.c(2326): Failed to set file 1fa24203-2bab-43e3-868d-8431b2700c93/Oud hidden in repo tree.
[04/03/18 10:13:37] dokan-ops.c(63): SetFileAttributes \Brug_Amsterdamse_Bos_1\Oud: IO error
[04/03/18 10:13:37] dokan-ops.c(2326): Failed to set file 1fa24203-2bab-43e3-868d-8431b2700c93/Tekeningen hidden in repo tree.
[04/03/18 10:13:37] dokan-ops.c(63): SetFileAttributes \Brug_Amsterdamse_Bos_1\Tekeningen: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Berekeningen hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Berekeningen: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Ontwerpen hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Ontwerpen: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Oud hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Oud: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Tekeningen hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Tekeningen: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Tekeningen/LW hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Tekeningen\LW: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Tekeningen/MW hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Tekeningen\MW: IO error
[04/03/18 10:13:38] dokan-ops.c(2326): Failed to set file bc4bf597-8460-4c47-95ff-ba9363837427/Verhuur hidden in repo tree.
[04/03/18 10:13:38] dokan-ops.c(63): SetFileAttributes \Brug_Zwembad_Europacup_2018\Verhuur: IO error

But I got no idea where I should start fixing that…

Allright I seemed to have fixed all issues by going through the following steps:

  • First uninstall seadrive and reinstall it.
  • deleted the user
  • recreated the user
  • Login with new user

this seems to fix some issues with ‘internal server errors’ while logging in, and I no longer encounter any I/O issues.

You don’t have to recreate the user, it should be enough to run ./seaf-fsck.sh --repair and ./seaf-gc.sh and then install seadrive another time.

2 Likes