haiwen / seafile-client

Seafile desktop client.
http://seafile.com
Apache License 2.0
471 stars 279 forks source link

Folders no longer Syncing in Windows Client v4.2.1 #583

Closed tyronx closed 8 years ago

tyronx commented 9 years ago

In the GUI it only displays "Waiting for Sync". I recently upgraded the client, since then it doesn't work no longer. I replaced the remote URL from the logs before pasting here as I prefer not to disclose it publicly.

Here are the logs:

seafile.log [05/19/15 11:40:07] seaf-daemon.c(504): starting seafile client 4.2.1 [05/19/15 11:40:07] seaf-daemon.c(506): seafile source code version 190876f1970ef493081eb38dac8d30f5d3b6fa30 [05/19/15 11:40:07] ../common/mq-mgr.c(60): [mq client] mq cilent is started [05/19/15 11:40:07] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seafile.heartbeat [05/19/15 11:43:15] seaf-daemon.c(504): starting seafile client 4.2.1 [05/19/15 11:43:15] seaf-daemon.c(506): seafile source code version 190876f1970ef493081eb38dac8d30f5d3b6fa30 [05/19/15 11:43:15] ../common/mq-mgr.c(60): [mq client] mq cilent is started [05/19/15 11:43:15] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seafile.heartbeat

applet.log [05/19/15 11:43:13]starting ccnet: ("-c", "C:/Users/tyron/ccnet") [05/19/15 11:43:14]trying to connect to ccnet daemon...

[05/19/15 11:43:14]connected to ccnet daemon

[05/19/15 11:43:15]seafile daemon is now running [05/19/15 11:43:15][Rpc Client] connected to daemon [05/19/15 11:43:15][MessageListener] connected to daemon [05/19/15 11:43:15]Unable to get config (int) value download_limit [05/19/15 11:43:15]Unable to get config (int) value upload_limit [05/19/15 11:43:15][Rpc Client] connected to daemon [05/19/15 11:43:15][Rpc Client] connected to daemon [05/19/15 11:43:15]starting seaf-daemon: ("-c", "C:/Users/tyron/ccnet", "-d", "C:/Users/tyron/Documents/Seafile/Seafile/seafile-data", "-w", "C:/Users/tyron/Documents/Seafile/Seafile") [05/19/15 11:43:16]The latest version is 4.1.4 [05/19/15 11:43:16]request failed for https://[removed url for safety]/api2/server-info/: status code 404

[05/19/15 11:43:16]update server info failed Server Error

ccnet.log [05/19/15 11:42:14] ../common/peer.c(941): libevent got an error! what=33, errno=0 (No error) [05/19/15 11:42:14] ../common/peer.c(943): Local peer down [05/19/15 11:42:14] ../common/peer.c(941): libevent got an error! what=33, errno=0 (No error) [05/19/15 11:42:14] ../common/peer.c(943): Local peer down [05/19/15 11:42:14] ../common/peer.c(941): libevent got an error! what=33, errno=0 (No error) [05/19/15 11:42:14] ../common/peer.c(943): Local peer down [05/19/15 11:43:13] ccnet-daemon.c(193): starting ccnet client 4.2.1 [05/19/15 11:43:13] ccnet-daemon.c(195): ccnet source code version fa0fb00390419d73510b394790aa01d5d1e9819a [05/19/15 11:43:13] ../common/session.c(395): Listen on 127.0.0.1 13419 [05/19/15 11:43:13] ../common/session.c(267): Update pubinfo file [05/19/15 11:43:14] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client [05/19/15 11:43:15] ../common/session.c(375): Accepted a local client

tyronx commented 9 years ago

Ok, apparantely I was not supposed to update to the latest possible version since the server is not updated. 4.1.6 works fine.

An error message "Server out of date" or similar would be very helpful!

ididimarco commented 9 years ago

Same issue here. Btw. how did you downgrade your client? 4.1.6 installer quits with "A more up-to-date version is detected ...". Manual uninstall? I hope the folder structure stays intact..

tyronx commented 9 years ago

Yes, I uninstalled manually and there was a yes/no option to keep the user information or something.

ididimarco commented 9 years ago

Ah, i c, then it should be "safe". Thanx.