Seafile Client on Ubuntu - Transport Error


#1

Upon starting Seafile after booting my Ubuntu laptop, all libaries show Waiting to Sync with the white cloud and three dots. After attempting force a sync by right clickings and choosing Sync Now, all libaries go orange and I see a dialog that says Transport Error.

Checking the logs I see that “Bad response: 102 processor is dead” has spammed the log (i snipped the hundreds of entries);

Applet.log:

[12/04/2017 06:58:27 PM][Sea RPC] Bad response: 102 processor is dead.
[12/04/2017 06:58:27 PM][Sea RPC] Bad response: 102 processor is dead.
[12/04/2017 06:58:27 PM][Sea RPC] Bad response: 102 processor is dead.
[12/04/2017 06:58:27 PM][Sea RPC] Bad response: 102 processor is dead.
[12/04/2017 06:58:27 PM][Sea RPC] Bad response: 102 processor is dead.
[12/04/2017 06:58:27 PM][Daemon Mgr] stopping ccnet/seafile daemon
[12/04/2017 06:58:30 PM]starting ccnet:  ("-c", "/home/alarioza/.ccnet")
[12/04/2017 06:58:31 PM]trying to connect to ccnet daemon...

[12/04/2017 06:58:31 PM]connected to ccnet daemon

[12/04/2017 06:58:31 PM]starting seaf-daemon:  ("-c", "/home/alarioza/.ccnet", "-d", "/home/alarioza/Seafile/.seafile-data", "-w", "/home/alarioza/Seafile")
[12/04/2017 06:58:32 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:32 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:32 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:33 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:33 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:33 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:34 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:34 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:34 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:35 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:35 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:35 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:36 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:36 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:36 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:37 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:37 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:37 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:38 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:38 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:38 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:39 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:39 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:39 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:40 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:40 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:40 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:41 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:41 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:41 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:42 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:42 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:42 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:43 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:43 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:43 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:44 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:44 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:44 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:45 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:45 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:45 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:46 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:46 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:46 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:47 PM][Rpc Client] connected to daemon
[12/04/2017 06:58:47 PM][RPC] failed to start rpc server: 511 Unknown service.
[12/04/2017 06:58:47 PM]Unable to get config value use_proxy: Transport Error
[12/04/2017 06:58:47 PM]seafile rpc is not ready after 16 retry, abort
[12/04/2017 06:58:55 PM]starting ccnet:  ("-c", "/home/alarioza/.ccnet")
[12/04/2017 06:58:56 PM]trying to connect to ccnet daemon...

I also have a Windows 10 and Android clients connecting to this sever with the same account, but they work perfectly fine. Any ideas?


#2

Version of client? Version of ubuntu? Source of client (deb donwload, ppa, self compiled)? Version of server?


#3

This is because the underlying process seaf-daemon is dead. Just restart the client.


#4

Seafile Client: 6.0.7 (from Ubuntu Software)
Seafile Server: 6.2.2
Ubuntu: 17.10


#5

Restarting the client does not solve the issue.


#6

I’m still having this issue - is there more information I can provide for someone to help me find the solution?


#7

Did you tried to reinstall klient?


#8

I have, but I’m still having the issue. :disappointed:


#9

I have 17.10 a Seafile running great, so you have to look around what can be bad. Look at sys log and try to run client. There should be some error message which cause deamon kill.


#10

Checking my system log I found:

seaf-daemon[10300]: segfault at 0 ip           (null) sp 00007ffe20705cb8 error 14 in seaf-daemon[55eb5cbed000+9c000]

Seems like @daniel.pan was on the right track, but I’m not sure what would cause this?


#11

Yes that’s what we know from start. Daemon is running, i’m trying to get why. This is error which mean, daemon start and drop cause some bad setup.

it’s looks like some TCP/IP problem. Do you have IPv6 active in your system? What you setup in client as URL to Seafile server? IP or domain? if domain can you check over nslookup <seafile_domain> what DNS returning for you?


#12

IPv6 appears to be enabled:

sudo sysctl -a | grep disable_ipv6
net.ipv6.conf.all.disable_ipv6 = 0
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
net.ipv6.conf.default.disable_ipv6 = 0
sysctl: reading key "net.ipv6.conf.enp2s0.stable_secret"
net.ipv6.conf.enp2s0.disable_ipv6 = 0
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
net.ipv6.conf.lo.disable_ipv6 = 0
sysctl: reading key "net.ipv6.conf.wlp3s0.stable_secret"
net.ipv6.conf.wlp3s0.disable_ipv6 = 0

The URL I am using is a domain name. Below is what nslookup returns (with the domain name and IP removed):

nslookup the.domain.name
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	the.domain.name
Address: 1.2.3.4


#13

I just uninstalled seafile and installed the version via the ppa instead of the one in the Ubuntu Software Store but it was having the same issues. However, I was notified about a system system update shortly after which just finished and after rebooting, Seafile is now correctly syncing the libraries.

I’m not sure what was wrong, but if you’re still curious I’d be happy to supply any more info trying to figure out what was going on.


#14

May you got bad bad dependecies or their versions :wink: