Help: All Seafile Clients stop syncing; Where to look for the problem?

[Hugo Cello]

Hi All,

I'm new to the list and more or less new to Seafile. I've installed Seafile server on RasPi some time ago and it was running fine so long (Clients on Windows, Android and Linux). During my holidays Seafile clients stopped syncing any longer. I didn't find any error messages so I updated the server from version 2.1.3 to 3.1.3 without issue following the Wiki. But unfortunately the situation does not change.

I can see all my files on seahub, add and delete files there but they got not synced to clients. It's the same the other way round. Newly created files on client are not synced to server. Starting seafile.sh and seahub.sh gives no error message. There are error messages in ccnet.log though, e.g.

--------------------- snip -----------------------------
[08/27/14 19:00:08] ../common/peer.c(956): [Net Error] Peer gerbil@Wombat (cf50730d4d) down
[08/27/14 19:00:08] ../common/processor.c(219): [Proc] Shutdown processor keepalive2-proc(-1001) for bad update: 515 peer down
[08/27/14 19:00:08] ../common/processors/keepalive2-proc.c(476): [Keepalive] Error from peer 515 peer down
[08/28/14 09:37:33] ../common/connect-mgr.c(266): Unknown peer 0d2911500b4a74a242f7bd9f600fe1a7a51e3d47 connecting
[08/28/14 10:09:05] ../common/peer.c(948): libevent got an error! what=33, errno=104 (Connection reset by peer)
[08/28/14 10:09:05] ../common/peer.c(956): [Net Error] Peer vroni@ (0d2911500b) down
[08/28/14 10:09:05] ../common/processor.c(219): [Proc] Shutdown processor keepalive2-proc(-1001) for bad update: 515 peer down
[08/28/14 10:09:05] ../common/processors/keepalive2-proc.c(476): [Keepalive] Error from peer 515 peer down
[08/28/14 11:15:10] ../common/connect-mgr.c(266): Unknown peer 0d2911500b4a74a242f7bd9f600fe1a7a51e3d47 connecting
[08/28/14 12:29:51] ../common/peer.c(948): libevent got an error! what=33, errno=104 (Connection reset by peer)
[08/28/14 12:29:51] ../common/peer.c(956): [Net Error] Peer vroni@ (0d2911500b) down
[08/28/14 12:29:51] ../common/processor.c(219): [Proc] Shutdown processor keepalive2-proc(-1001) for bad update: 515 peer down
[08/28/14 12:29:51] ../common/processors/keepalive2-proc.c(476): [Keepalive] Error from peer 515 peer down
[08/28/14 16:06:36] ../common/session.c(375): Accepted a local client
[08/28/14 16:07:10] ../common/connect-mgr.c(266): Unknown peer cf50730d4ddeb3eacdd01221f08de05980572ffe connecting
[08/28/14 16:07:21] ../common/processor.c(293): [Proc] peer 159af560b6, Shutdown processor service-stub-proc(4278) for bad response: 405 Protocol v
--------------------- snip -----------------------------

but I've got no idea how to proceed (tried google, FAQs and Wiki first for sure).

Any hint is highly appreciated. What could be the next steps?

Thanks for your time
Hugo

[JiaQiang Xu]

This looks like a network problem. Do you have firewall between the client and the server? Ports 12001 and 10001 should be open.

[Hugo Cello]

On Friday, August 29, 2014 3:02:40 PM UTC+2, JiaQiang Xu wrote:

This looks like a network problem. Do you have firewall between the client and the server? Ports 12001 and 10001 should be open.

Thanks for your help, There is no firewall existing in the internal network. Ports 12001 and 10001 are open as TCP ports. It worked for a few month without problem. It seems like a network problem for me as well as syncing starts but up- and download speed stay 0%.

Anyone aothe hint where to look / what to do?
Hugo
 

[Jaime Sotelo]

I know you've already checked that but...

out of RAM?
out of disk or I/O error??

I mean, it sounds like system error due to read/write error or something. Check system logs.

[Hugo Cello]

I solved the problem. I found (by clicking the green connection mark) in the seafile client the message
"transfer protocol outdated. you need to upgrade seafile"
No message about this in the server log files.
I upgraded all clients to version 3.1.5. Now it works again.

Thanks for all your help
Hugo