Client stops syncing, needs download library again #730

Closed
jaroslavmencl opened this Issue Jul 14, 2014 · 35 comments

Projects

None yet

5 participants

@jaroslavmencl

Hello,

I'm new here. I set up a small network with a Seafile server (Windows 7) and clients on Windows and Mac OSX. Some of clients stop syncing from time to time. Libraries look like not downloaded. They must be downloaded again (random issue) int existing folder.
Users, who are not so "computer skilled" simply can miss that fact.
I would appreciate any help.

Thank you in advance,
Jaroslav

Logs are here: https://www.sendspace.com/file/i5utj1

Owner
lins05 commented Jul 19, 2014

Are these libraries with problems on network mapping drive?

If so, open the settings dialog (tray icon -> settings), go to "advanced"
tab, and turn on the option "Do not automatically unsync a library".

On Mon, Jul 14, 2014 at 3:33 PM, jaroslavmencl notifications@github.com
wrote:

Hello,

I'm new here. I set up a small network with a Seafile server (Windows 7)
and clients on Windows and Mac OSX. Some of clients stop syncing from time
to time. Libraries look like not downloaded. They must be downloaded again
(random issue) int existing folder.
Users, who are not so "computer skilled" simply can miss that fact.
I would appreciate any help.

Thank you in advance,
Jaroslav

Logs are here: https://www.sendspace.com/file/i5utj1


Reply to this email directly or view it on GitHub
#730.

Hi,

these libraries are not on network drives and the "do not automatically unsync" setting I have checked on all clients.

Thank you,
Jaroslav

Owner

Hi Jaroslav,

I checked the logs. Seems after upgrading client to 3.0.4, all the libraries can be synced normally. Can you provide more information about the issue, for example, a screenshot.

Hi,

the problem persists since the first installation (approx 6 months ago). It was 2.1.5 on clients and server.
I believed upgrade to 3.0.4 (again server and clients, a month ago) would help, but it didn't.
I don't have any screenshot now (since it's weekend), but on client applet some libraries ar ok (green with tick) and some are orange, like the user has never downloaded them. He or she then have to "sync with existing folder" again.

Thank you,
Jaroslav

Owner

Hi,

From the log, I see a lot of errors happened because of no space left on the disk. While I can't find information libraries being unsynced.

We only unsync a library when its local directory can't be detected or the library is deleted in the server side.

Possible solution:

  1. Send me logs on other machine that have this problem.
  2. We will add logs on every place when a library is unsynced to help debug the problem.

Hi,

thank you for your care. Disk space messages are because of some system (recovery etc.) partition, but I will check it again.
We do not use web interface, so we do not delete libraries.
The important fact may be that all the mentioned libraries are group (shared). All are stored in c:\seafile (and similar on Macs).
I attach one actuall screenshot (the "administrativa" library should be synced) and logs from another windows client.
Any other version with deeper debug is apreciated!
seafile_screen

Logs are here: https://www.sendspace.com/file/un4z1e

Thank you,
Jaroslav

Hi again,

the problem continues with very frequent creating conflict copies, but I hope it is only secondary problem caused by the random unsyncing mentioned above.
I'm looking forward to your help, because we are getting desperate now.

Thank you,
Jaroslav

Owner

Hi,

This problem is caused by the some database errors on the server side. We will look into the problem. For now we can add a simple option at the client to not unsync the library to solve the problem quickly. You may have to wait for two days.

Regards,
Daniel Pan

Owner

The database is locked by too much synchronized access. And the server thinks a library is deleted from the database.

Hello Daniel,

for sure I would appreciate any (temporary) solution. If you can prepare client as you have described, please, do it. Thank you for your care.

Best regards,
Jaroslav

Just to clarify: we need OS X and Windows clients.

Thank you,
Jaroslav

Hi Daniel,

is there anything new, please? I'm looking forward to your solution.

Thanks again,
Jaroslav

Owner

We plan to give you a new windows package v3.0.5 today. But we find a bug just now. We have to delay it to next Monday.

Ok, thank you for info. Mac OS client is important as well.
Jaroslav

Owner

The windows version is ready (v3.0.5). You can download it via: https://bitbucket.org/haiwen/seafile/downloads . Please give it a test. We will upload mac version later.

Thank you very much, I will let you know soon.
I suppose you recommend to check the new option (do not unsync when not found on server).
Jaroslav

Hi Daniel,

I'd like to ask you, when do you plan to release 3.0.5 client for Mac. Windows clients now seem to be ok, but I want to see cooperation of whole network together and simultaneously.
Thank you for info,

Jaroslav

Owner

We will work on it next Monday.

Thank you for info. Will be the error fixed i next releases 3.1.x, as well?
Jaroslav

Hi Daniel,

is there any progress, please?

Thank you for a message,
Jaroslav

Owner

You can use the 3.1.5 version. The option is included in this version.

Owner

3.1 client is compatible with 3.0 server.

@shoeper shoeper closed this Feb 9, 2016
protivakid commented Apr 22, 2016 edited

The database is locked by too much synchronized access. And the server thinks a library is deleted from the database.

Is this still an issue @freeplant ?

I have set up Seafile for a friend with 3 computers. One of them will un-sync it'self after a few weeks. I first went in and checked the option under Settings>Advanced "Do not automatically unsync a library". This worked for a couple weeks and then he called me again saying it was not synced. I can see the library on the client application but when I go to info it said that it needed to be downloaded. This time a second computer had also become un-synced with the same message under library info on the client.

I downloaded the library now a third time and this time also enabled the option "Do not un-sync a library when not found on server" along with the first option.

Do you think selecting both of these options on the clients will help fix my issue? I also grabbed all server & client logs. Scanning them without knowing what to look for I did see "request failed for http://XXX.XXX.XXX.XXX:XXXX/api2/unseen_messages/" on the two clients that became un-synced but I did not see this on the client that stayed synced the whole time.

Is there something else I should look for in the logs? When a client unsyncs does it make some sort of note in the logs I can key off of and search for? I didn't see any obvious message around the date/time he said it stopped syncing.

Thanks!

Contributor
shoeper commented Apr 22, 2016

Is this still an issue @freeplant ?

I'm very sure it is not. There would have been many reports otherwise and I've never heard of the problem before (I've read almost everything). On unsync - at least when it was due to missing local disk - there is a message in seafile.log on the client side

Contributor
shoeper commented Apr 22, 2016

Btw. did you repair a library using seaf-fsck?

@shoeper I have not run "seaf-fsck" at all or attempted any other repairs on the library.

Looking at the seafile.log files on all 3 clients I see the following

"[04/01/16 09:21:19] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay"

I see this twice on client #1 that was un-synced twice, once on client #2 that un-synced once, and don't see it on client #3 that has remained working.

Any ideas?

Contributor
shoeper commented Apr 22, 2016

Can you have a look at the server logs for the time of the desynchronization?

Which Seafile version are you using? (client & server)
Which database are you using?

Hello the client versions are 5.0.6. The server version is 5.0.3. I am using seahub and setup my server with this windows guide.

The seafserv.log is oddly empty between Mar 18th & Apr 19th. Perhaps it only populates when the server is rebooted and not for every event? From the other logs I copied any events I saw on the date each client un-synced. On April 1 I see "Failed to find repo 4dd6a1d9." however that doesn't explain the April 14th & 16th un-sync events. I included parts of the logs from the server below as well as each client log where the un-sync happened and the few events that occurred prior.

Server:
seafile.log
[04/01/16 09:17:47] http-server.c(1214): Failed to find repo 4dd6a1d9.
[04/01/16 09:18:11] http-server.c(914): Repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d is missing or corrupted.

ccnet.log
[04/01/16 09:18:54] ../common/session.c(398): Accepted a local client

seahub_django_request.log
2016-04-01 09:02:46,670 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version
2016-04-14 07:15:49,147 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version
2016-04-14 07:34:36,588 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version
2016-04-16 07:13:43,507 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version

Client 1:
seafile.log
[04/01/16 09:21:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/01/16 09:21:17] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/01/16 09:21:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/01/16 09:21:17] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/01/16 09:21:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/01/16 09:21:17] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/01/16 09:21:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/01/16 09:21:19] http-tx-mgr.c(2009): Bad response code for GET http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/repo/4dd6a1d9-0514-46c5-b80e-c37f5bff679d/permission-check/?op=upload&client_id=b3c820e708729cdcc5a3c8a0ac6b1eb7eac4678c&client_name=MarcXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 444.
[04/01/16 09:21:19] http-tx-mgr.c(3175): Upload permission denied for repo 4dd6a1d9 on server http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
[04/01/16 09:21:19] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('error', 'finished')
[04/01/16 09:21:19] sync-mgr.c(726): Repo 'Seafile Share' sync state transition from uploading to 'error': 'No such repo on relay.'.
[04/01/16 09:21:19] sync-mgr.c(1300): repo Seafile Share(4dd6a1d9) not found on server
[04/01/16 09:21:19] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay
[04/04/16 09:09:37] seaf-daemon.c(534): starting seafile client 5.0.6

[04/14/16 15:52:55] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/14/16 15:52:55] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/14/16 15:52:56] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:52:56] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:52:56] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/14/16 15:52:56] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/14/16 15:52:56] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:52:56] http-tx-mgr.c(2009): Bad response code for GET http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/repo/4dd6a1d9-0514-46c5-b80e-c37f5bff679d/permission-check/?op=upload&client_id=b3c820e708729cdcc5a3c8a0ac6b1eb7eac4678c&client_name=MarcXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 444.
[04/14/16 15:52:56] http-tx-mgr.c(3175): Upload permission denied for repo 4dd6a1d9 on server http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
[04/14/16 15:52:56] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('error', 'finished')
[04/14/16 15:52:56] sync-mgr.c(726): Repo 'Seafile Share' sync state transition from uploading to 'error': 'No such repo on relay.'.
[04/14/16 15:52:56] sync-mgr.c(1300): repo Seafile Share(4dd6a1d9) not found on server
[04/14/16 15:52:56] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay
[04/15/16 16:29:22] seaf-daemon.c(534): starting seafile client 5.0.6

Client 2:
seafile.log
[04/16/16 07:31:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/16/16 07:31:17] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/16/16 07:31:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/16/16 07:31:17] repo-mgr.c(1978): Failed to stat Deceased/Discharge papers.AOL0d5f0651-cf21-49ec-b240-134398541a59: No such file or directory.
[04/16/16 07:31:17] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/16/16 07:31:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/16/16 07:31:17] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/16/16 07:31:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/16/16 07:31:19] http-tx-mgr.c(2009): Bad response code for GET http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/repo/4dd6a1d9-0514-46c5-b80e-c37f5bff679d/permission-check/?op=upload&client_id=9d5e62ec1a5652709a78b356db6be745bded8984&client_name=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 444.
[04/16/16 07:31:19] http-tx-mgr.c(3175): Upload permission denied for repo 4dd6a1d9 on server http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
[04/16/16 07:31:19] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('error', 'finished')
[04/16/16 07:31:19] sync-mgr.c(726): Repo 'Seafile Share' sync state transition from uploading to 'error': 'No such repo on relay.'.
[04/16/16 07:31:19] sync-mgr.c(1300): repo Seafile Share(4dd6a1d9) not found on server
[04/16/16 07:31:19] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay
[04/17/16 10:29:36] seaf-daemon.c(534): starting seafile client 5.0.6
Contributor
shoeper commented Apr 22, 2016

So the repo wasn't available on the server for whatever reason. This is very likely a setup or hardware issue then.

This

seahub_django_request.log
2016-04-01 09:02:46,670 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version
2016-04-14 07:15:49,147 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version
2016-04-14 07:34:36,588 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version
2016-04-16 07:13:43,507 [WARNING] django.request:144 get_response Not Found: /seafhttp/protocol-version

that for whatever reason the requests weren't handled correctly.

It seems the repo will eventually show up again for the client. Will checking that second option "Do not un-sync a library when not found on server" keep it so that when it does show up it will remain synced or will the client still un-sync even with that checked?

Setup wise I followed the windows guide. There was not much to do, install a specific python version, run the installer, set the url in the config and boot. The library creation and everything else was done through the seafile UI. Is there anyplace else I could look?

Disk wise I checked this disk with the Western Digital diagnostic tool a couple months back and it passed fine. It's not that old nor has it had much use. It does always sound like this thing is pretty active though. I don't know if that's seafile reading/writing to/from the disk a ton even with no client uploads or Windows Server doing it. Does Seafile require some sort of minimum CPU / RAM to run properly? Hardware isn't that old but not top of the line either. It does meet the requirements for Windows Server 08 R2 which I imagine are higher than that of seafile.

Contributor
shoeper commented Apr 22, 2016 edited

Will checking that second option "Do not un-sync a library when not found on server" keep it so that when it does show up it will remain synced or will the client still un-sync even with that checked?

This won't ever unsync libraries automatically. (so if it is not available for 10 minutes but again afterwards it won't get unsynced.

And yes, Seafile does not have high resource requirements. Are you using SQLite or MySQL? In case you're SQLite setting up MySQL could (possibly) improve things.

Thank you so much @shoeper hoping this fixes my issue then. Perhaps when I am more experienced with seafile I will figure out why the library is unavailable for periods of time in the first place. As-is I have only been playing around with it a couple months. Do the logs show anywhere when a previously unavailable library again becomes available? I take it when it is again available the client will continue to sync like normal?

Contributor
shoeper commented Apr 22, 2016

I take it when it is again available the client will continue to sync like normal?

Yes enabling the option we talked about leads to this behaviour.

Do the logs show anywhere when a previously unavailable library again becomes available?

I don't know. But I don't think so because the availability isn't checked on a timely basis. It is more like: it wasn't available in this moment, write a log message. So thinking on this the other way around there would be a log message for each request stating the library was available ;)

I don't know your setup, but in a nutshell as long as possible I'd recommand everyone to run Seafile on Linux. It is much better tested there and it's the platform always being taken into account first (faster availability of updates, faster availability of fixes in case there are bugs, ...). But switching to MySQL could both improve the performance and possibly also fix this behaviour in your case.

Contributor
shoeper commented Apr 22, 2016

On thing you could check would be whether to or more clients were transfering data at the same time (just take a time one client got unsynced and look at the other logs using the same time .. and past the log messages here, please).

Thanks I will look into this. I could run Linux in a VM but the Windows Server does other things for him such as automating bare metal backups for client computers so at this point I think I am stuck with the windows version. Good to keep in mind though if ever there is the opportunity to swap him over.

I'll have to see if I can dig up and MySQL guides for seafile, again I am pretty new to this whole seafile thing but certainly not development / computer troubleshooting in general.

Here is the logs from all 3 clients during the three un-sync windows.

Un-sync 1

UN-SYNC #1 CLIENT #1 AT [04/01/16 09:21:19] ************************************************************************************************************************
Client 1:
[04/01/16 09:21:01] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/01/16 09:21:02] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/01/16 09:21:02] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/01/16 09:21:07] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/01/16 09:21:07] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/01/16 09:21:07] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/01/16 09:21:07] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/01/16 09:21:07] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/01/16 09:21:11] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/01/16 09:21:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/01/16 09:21:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/01/16 09:21:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/01/16 09:21:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/01/16 09:21:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/01/16 09:21:17] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/01/16 09:21:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/01/16 09:21:17] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/01/16 09:21:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/01/16 09:21:17] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/01/16 09:21:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/01/16 09:21:19] http-tx-mgr.c(2009): Bad response code for GET http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/repo/4dd6a1d9-0514-46c5-b80e-c37f5bff679d/permission-check/?op=upload&client_id=b3c820e708729cdcc5a3c8a0ac6b1eb7eac4678c&client_name=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 444.
[04/01/16 09:21:19] http-tx-mgr.c(3175): Upload permission denied for repo 4dd6a1d9 on server http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
[04/01/16 09:21:19] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('error', 'finished')
[04/01/16 09:21:19] sync-mgr.c(726): Repo 'Seafile Share' sync state transition from uploading to 'error': 'No such repo on relay.'.
[04/01/16 09:21:19] sync-mgr.c(1300): repo Seafile Share(4dd6a1d9) not found on server
[04/01/16 09:21:19] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay

Client 2:
[04/01/16 09:21:19] [04/01/16 09:21:19] http-tx-mgr.c(4015): Download with HTTP sync protocol version 1.
sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'initializing' to 'downloading'.
[04/01/16 09:21:19] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/01/16 09:21:20] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/01/16 09:21:20] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/01/16 09:21:20] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/01/16 09:21:21] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('finished', 'finished')
[04/01/16 09:21:21] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'downloading' to 'synchronized'.
[04/01/16 09:21:23] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/01/16 09:21:23] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/01/16 09:21:23] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'synchronized'.
[04/01/16 09:21:54] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).

Client 3:
[04/01/16 09:21:10] [04/01/16 09:21:10] http-tx-mgr.c(4015): Download with HTTP sync protocol version 1.
sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'initializing' to 'downloading'.
[04/01/16 09:21:10] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/01/16 09:21:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/01/16 09:21:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/01/16 09:21:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/01/16 09:21:14] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('finished', 'finished')
[04/01/16 09:21:14] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'downloading' to 'synchronized'.
[04/01/16 09:21:16] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/01/16 09:21:16] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/01/16 09:21:16] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'synchronized'.
[04/01/16 09:21:47] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).

Un-sync 2

UN-SYNC #2 CLIENT #1 AT [04/14/16 15:52:56] ************************************************************************************************************************
Client 1: 
[04/14/16 15:50:53] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:50:53] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:50:53] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'synchronized'.
[04/14/16 15:51:19] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:51:19] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:51:19] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'synchronized'.
[04/14/16 15:51:51] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:51:51] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:51:52] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/14/16 15:51:52] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/14/16 15:51:52] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:51:52] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/14/16 15:51:52] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/14/16 15:51:52] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/14/16 15:51:52] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/14/16 15:51:53] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/14/16 15:51:53] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/14/16 15:52:04] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:52:04] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:52:04] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/14/16 15:52:04] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/14/16 15:52:05] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/14/16 15:52:47] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:52:47] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:52:48] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/14/16 15:52:48] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/14/16 15:52:48] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:52:48] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/14/16 15:52:48] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/14/16 15:52:49] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/14/16 15:52:55] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/14/16 15:52:55] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/14/16 15:52:55] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/14/16 15:52:55] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/14/16 15:52:56] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:52:56] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:52:56] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/14/16 15:52:56] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/14/16 15:52:56] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:52:56] http-tx-mgr.c(2009): Bad response code for GET http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/repo/4dd6a1d9-0514-46c5-b80e-c37f5bff679d/permission-check/?op=upload&client_id=b3c820e708729cdcc5a3c8a0ac6b1eb7eac4678c&client_name=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 444.
[04/14/16 15:52:56] http-tx-mgr.c(3175): Upload permission denied for repo 4dd6a1d9 on server http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
[04/14/16 15:52:56] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('error', 'finished')
[04/14/16 15:52:56] sync-mgr.c(726): Repo 'Seafile Share' sync state transition from uploading to 'error': 'No such repo on relay.'.
[04/14/16 15:52:56] sync-mgr.c(1300): repo Seafile Share(4dd6a1d9) not found on server
[04/14/16 15:52:56] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay

Client 2: 
[04/14/16 15:52:04] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'initializing' to 'downloading'.
[04/14/16 15:52:04] http-tx-mgr.c(4015): Download with HTTP sync protocol version 1.
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/14/16 15:52:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('finished', 'finished')
[04/14/16 15:52:04] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'downloading' to 'synchronized'.
[04/14/16 15:52:06] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:52:06] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:52:06] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'synchronized'.

Client 3:
[04/14/16 15:52:17] [04/14/16 15:52:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'initializing' to 'downloading'.
http-tx-mgr.c(4015): Download with HTTP sync protocol version 1.
[04/14/16 15:52:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/14/16 15:52:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/14/16 15:52:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/14/16 15:52:18] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/14/16 15:52:18] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('finished', 'finished')
[04/14/16 15:52:18] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'downloading' to 'synchronized'.
[04/14/16 15:52:20] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/14/16 15:52:20] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/14/16 15:52:20] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'synchronized'.

Un-sync 3

UN-SYNC #3 CLIENT #2 AT 04/16/16 07:31:19 ************************************************************************************************************************

Client 1:
WAS POWERED OFF

Client 2:
[04/16/16 07:30:32] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/16/16 07:30:32] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/16/16 07:30:32] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/16/16 07:30:32] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/16/16 07:30:32] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/16/16 07:30:35] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/16/16 07:30:38] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/16/16 07:30:38] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/16/16 07:30:38] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/16/16 07:30:41] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/16/16 07:30:41] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/16/16 07:30:47] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/16/16 07:30:47] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/16/16 07:30:47] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/16/16 07:30:47] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/16/16 07:30:47] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/16/16 07:30:51] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/16/16 07:30:54] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/16/16 07:30:54] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/16/16 07:30:54] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/16/16 07:30:56] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/16/16 07:30:56] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/16/16 07:30:59] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/16/16 07:30:59] repo-mgr.c(1978): Failed to stat Deceased/Discharge papers: No such file or directory.
[04/16/16 07:30:59] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/16/16 07:30:59] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/16/16 07:30:59] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/16/16 07:30:59] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/16/16 07:31:04] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('normal', 'commit')
[04/16/16 07:31:10] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'commit') --> ('normal', 'fs')
[04/16/16 07:31:12] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'fs') --> ('normal', 'data')
[04/16/16 07:31:13] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'data') --> ('normal', 'update-branch')
[04/16/16 07:31:16] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'update-branch') --> ('finished', 'finished')
[04/16/16 07:31:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'uploading' to 'initializing'.
[04/16/16 07:31:17] sync-mgr.c(1477): Removing blocks for repo Seafile Share(4dd6a1d9).
[04/16/16 07:31:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'synchronized' to 'committing'.
[04/16/16 07:31:17] repo-mgr.c(1978): Failed to stat Deceased/Discharge papers.AOL0d5f0651-cf21-49ec-b240-134398541a59: No such file or directory.
[04/16/16 07:31:17] repo-mgr.c(3248): All events are processed for repo 4dd6a1d9-0514-46c5-b80e-c37f5bff679d.
[04/16/16 07:31:17] sync-mgr.c(658): Repo 'Seafile Share' sync state transition from 'committing' to 'uploading'.
[04/16/16 07:31:17] http-tx-mgr.c(3157): Upload with HTTP sync protocol version 1.
[04/16/16 07:31:17] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'init') --> ('normal', 'check')
[04/16/16 07:31:19] http-tx-mgr.c(2009): Bad response code for GET http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/repo/4dd6a1d9-0514-46c5-b80e-c37f5bff679d/permission-check/?op=upload&client_id=9d5e62ec1a5652709a78b356db6be745bded8984&client_name=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: 444.
[04/16/16 07:31:19] http-tx-mgr.c(3175): Upload permission denied for repo 4dd6a1d9 on server http://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
[04/16/16 07:31:19] http-tx-mgr.c(1009): Transfer repo '4dd6a1d9': ('normal', 'check') --> ('error', 'finished')
[04/16/16 07:31:19] sync-mgr.c(726): Repo 'Seafile Share' sync state transition from uploading to 'error': 'No such repo on relay.'.
[04/16/16 07:31:19] sync-mgr.c(1300): repo Seafile Share(4dd6a1d9) not found on server
[04/16/16 07:31:19] sync-mgr.c(1304): remove repo Seafile Share(4dd6a1d9) since it's deleted on relay

Client 3:
WAS ALREADY UN-SYNCED FROM 4/14/16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment