I was using Debian Jessie and recently upgraded the system to Stretch. I had Seafile client 5.0.1 installed and after the system upgrade the libraries are initially synced (it would begin to download the files) and then immediately unsync a few seconds later. I thought maybe it was a bug with the old Seafile client, so I upgraded to 6.0.0 and I am still having the same problem - I open Seafile and then about 20 seconds later all libraries become unsynced.
1 Like
I just realized something else. After the folders become unsynced, if I try to resync one of them (choosing a different directory) I get the error:
Failed to add download task:
Transport Error
Looking at my log files, this is what I have:
Applet.log
[12/12/2016 02:21:18 PM]starting ccnet: (“-c”, “/home/mike/.ccnet”)
[12/12/2016 02:21:19 PM]trying to connect to ccnet daemon…
[12/12/2016 02:21:19 PM]connected to ccnet daemon
[12/12/2016 02:21:19 PM]starting seaf-daemon: (“-c”, “/home/mike/.ccnet”, “-d”, “/home/mike/Seafile/.seafile-data”, “-w”, “/home/mike/Seafile”)
[12/12/2016 02:21:20 PM][Rpc Client] connected to daemon
[12/12/2016 02:21:20 PM][Rpc Client] connected to daemon
[12/12/2016 02:21:20 PM][MessageListener] connected to daemon
[12/12/2016 02:21:20 PM]Unable to get config value download_limit: Config not exists
[12/12/2016 02:21:20 PM]Unable to get config value upload_limit: Config not exists
[12/12/2016 02:21:20 PM]QString::arg: Argument missing: &Open cloud file browser, Seafile
[12/12/2016 02:21:21 PM][Rpc Client] connected to daemon
[12/12/2016 02:21:22 PM]The latest version is 5.0.1
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 515 peer down.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:52 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:53 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:54 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:55 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:56 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:57 PM][Sea RPC] Bad response: 102 processor is dead.
[12/12/2016 02:21:58 PM][Daemon Mgr] stopping ccnet/seafile daemon
ccnet.log
[12/12/16 14:21:18] ccnet-daemon.c(193): starting ccnet client 6.0.0
[12/12/16 14:21:18] …/common/session.c(132): using config file /home/mike/.ccnet/ccnet.conf
[12/12/16 14:21:18] …/common/session.c(455): socket file exists, delete it anyway
[12/12/16 14:21:18] …/common/session.c(484): Listen on /home/mike/.ccnet/ccnet.sock for local clients
[12/12/16 14:21:18] …/common/session.c(290): Update pubinfo file
[12/12/16 14:21:19] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:19] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:19] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:19] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:20] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:20] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:20] …/common/peer.c(943): Local peer down
[12/12/16 14:21:20] …/common/peer.c(943): Local peer down
[12/12/16 14:21:20] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:20] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:20] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:21] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:21] …/common/session.c(398): Accepted a local client
[12/12/16 14:21:52] …/common/peer.c(943): Local peer down
[12/12/16 14:21:52] …/common/peer.c(943): Local peer down
[12/12/16 14:21:52] …/common/peer.c(943): Local peer down
[12/12/16 14:21:58] …/common/peer.c(941): libevent got an error! what=33, errno=104 (Connection reset by peer)
[12/12/16 14:21:58] …/common/peer.c(943): Local peer down
[12/12/16 14:21:58] …/common/peer.c(943): Local peer down
Seafile.log
[12/12/16 14:21:19] seaf-daemon.c(548): starting seafile client 6.0.0
[12/12/16 14:21:19] …/common/mq-mgr.c(60): [mq client] mq cilent is started
[12/12/16 14:21:19] …/common/mq-mgr.c(106): [mq mgr] publish to heartbeat mq: seafile.heartbeat
[12/12/16 14:21:21] sync-mgr.c(660): Repo ‘reservations’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:21] repo-mgr.c(3592): All events are processed for repo 2afff7e4-11f7-4df9-a4c2-499f49ee06ab.
[12/12/16 14:21:21] sync-mgr.c(660): Repo ‘reservations’ sync state transition from ‘committing’ to ‘initializing’.
[12/12/16 14:21:22] sync-mgr.c(660): Repo ‘Personal documents’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:22] repo-mgr.c(3592): All events are processed for repo 021583b6-0041-43b5-88e1-4e6e85fc0d88.
[12/12/16 14:21:22] sync-mgr.c(660): Repo ‘Personal documents’ sync state transition from ‘committing’ to ‘initializing’.
[12/12/16 14:21:23] sync-mgr.c(660): Repo ‘printme’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:23] repo-mgr.c(3592): All events are processed for repo ffb2f7b9-c2b1-4429-b558-4bbe9317e51e.
[12/12/16 14:21:23] sync-mgr.c(660): Repo ‘printme’ sync state transition from ‘committing’ to ‘initializing’.
[12/12/16 14:21:24] sync-mgr.c(660): Repo ‘www’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:24] repo-mgr.c(3592): All events are processed for repo 2d036bcf-e2cd-488e-9854-24039db10c8c.
[12/12/16 14:21:24] sync-mgr.c(660): Repo ‘www’ sync state transition from ‘committing’ to ‘initializing’.
[12/12/16 14:21:25] sync-mgr.c(660): Repo ‘Adventure Inn documents’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:25] repo-mgr.c(3592): All events are processed for repo 3b0edb8f-20ea-41e5-95f5-63280b80b6da.
[12/12/16 14:21:25] sync-mgr.c(660): Repo ‘Adventure Inn documents’ sync state transition from ‘committing’ to ‘initializing’.
[12/12/16 14:21:26] sync-mgr.c(660): Repo ‘mp3s’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:26] repo-mgr.c(3592): All events are processed for repo 1fb5ef9c-b69b-4e98-a879-0c41433e8b21.
[12/12/16 14:21:26] sync-mgr.c(660): Repo ‘mp3s’ sync state transition from ‘committing’ to ‘initializing’.
[12/12/16 14:21:27] sync-mgr.c(660): Repo ‘Photos’ sync state transition from ‘synchronized’ to ‘committing’.
[12/12/16 14:21:27] repo-mgr.c(3592): All events are processed for repo 72c49351-f1c3-49b3-a16b-5cbebdd268b4.
[12/12/16 14:21:27] sync-mgr.c(660): Repo ‘Photos’ sync state transition from ‘committing’ to ‘initializing’.
The libraries are not unsynced. Seaf-daemon process crashed for some reason. Are you able to produce a coredump?
Sorry for taking so long to answer, but I haven’t been at this computer for a while. I have created a core dump, but it’s 50 MB. I also have no idea how to analyze it.
Deleting the ~/Seafile/.seafile-data hidden directory seems to have done the trick. I’m not sure what caused this. I have a backup of this directory, so if anyone is interested in investigating this further, let me know how to remove sensitive items from it and I’ll send it to you.
1 Like
@Jonathan : I have the same error, same kind of logs, with my new Debian Strectch, unable to use the client (Transport Error).
How can I make a core dump to help solve the problem?
Thanks a lot
The current Seafile client is not compatible with the libssl-1.1 used by Stretch. That’s why the client crashes. We’ll update the code soon to make it compatible with libssl 1.1.
1 Like
OK, thanks for your answer.
Any idea of the delay?
And also, is it posible to build the client in Stretch? I didn’t manage to do it with the instructions in https://manual.seafile.com/build_seafile/linux.html
Thnak you!
Olivier
Is there stil a problem with libssl-1.1 under Debian Stretch? Just dist-upgraded and have the “unsync” problem.
Seems I forgot to update my seafile repo from jessie to stretch. Sorry!