Windows client fails to sync

[crc...@gmail.com]

My wife's laptop can not sync to our Seafile server. Her other PC at work can sync without problem.  In my case, my 2 PCs can sync without any problem either. So, it is only her laptop that is having an issue... ;-(

The client was 1.8.something and I upgraded it to 2.0.5 but the problem still remains the same. Here is the output from seafile.log

[10/29/13 22:09:09] seaf-daemon.c(467): starting seafile client 2.0.5

[10/29/13 22:09:09] seaf-daemon.c(469): seafile source code version 4a0d0c8a4654b19a0be4b791d0297f2091828154

[10/29/13 22:09:09] ../common/mq-mgr.c(60): [mq client] mq cilent is started

[10/29/13 22:09:09] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seafile.heartbeat

[10/29/13 22:09:09] ../common/gc-core.c(313): No blocks. Skip GC.

[10/29/13 22:09:11] sync-mgr.c(425): Repo 'McGill' sync state transition from 'synchronized' to 'committing'.

[10/29/13 22:09:11] bad signature

[10/29/13 22:09:11] index file corrupt

[10/29/13 22:09:11] Failed to load index.

[10/29/13 22:09:11] sync-mgr.c(930): [Sync mgr] Failed to commit to repo McGill(61f12fb7).

[10/29/13 22:09:11] sync-mgr.c(496): Repo 'McGill' sync state transition from committing to 'error': 'Failed to index files.'.

[10/29/13 22:09:42] sync-mgr.c(425): Repo 'McGill' sync state transition from 'initializing' to 'downloading'.

[10/29/13 22:09:42] transfer-mgr.c(502): Transfer repo '61f12fb7': ('normal', 'init') --> ('normal', 'check')

[10/29/13 22:09:42] processors/check-tx-v3-proc.c(260): protocol version is 3.

[10/29/13 22:09:43] transfer-mgr.c(502): Transfer repo '61f12fb7': ('normal', 'check') --> ('normal', 'commit')

[10/29/13 22:09:44] transfer-mgr.c(502): Transfer repo '61f12fb7': ('normal', 'commit') --> ('normal', 'fs')

[10/29/13 22:09:46] bad signature

[10/29/13 22:09:46] index file corrupt

[10/29/13 22:09:46] Failed to load index.

[10/29/13 22:09:46] transfer-mgr.c(401): [tr-mgr] Failed to get new blocks for merge.

With 1.8.x the error messages were exactly the same

I checked the permissions on Seafile/seafile-data/index folder and it should be ok (never easy on windows to check things.....)

where should I look?

[Lingtao Pan]

Can you delete seafile-data and run Seafile again on this machine?

[JiaQiang Xu]

You just need to unsync the problematic library and sync it with the local folder again. This is an ultimate solution to many syncing problems;)

2013/10/30 <crc...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "seafile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to seafile+u...@googlegroups.com.
To post to this group, send email to sea...@googlegroups.com.
Visit this group at http://groups.google.com/group/seafile.
For more options, visit https://groups.google.com/groups/opt_out.

[crc...@gmail.com]

It worked. Thanks

Suggestion

1 - have an explicit status when there is a failure.

2 - have a button that can do unsync and sync without having to reconfigure the path, etc. Not that it is complex to do but if this is the ultimate solution.....