Seafile client does not start under linux anymore (elementary os = ubuntu 16.04 derivate)


#1

Until today I had a working seafile client installed on my linux computer running elementary OS, a Linux flavour derived from ubuntu 16.04 lts.
I regularly update the system with apt-get update dist-upgrade but I do not restart always the system after that. Today I had some problems with an hp printerdriver, installed them new (which included some python files as well and restarted my linux. After restart I got the problem that seafile client does not start and after a (long) while I get a error message that the intitalisation failed. I uninstalled the files I installed for my printer but this did not help. So I think has something to do with an earlier update.

In the seafile.log I found this (which seems to me it works just fine until this afternoon):

[12/17/18 16:25:51] seaf-daemon.c(491): starting seafile client 6.2.4
[12/17/18 16:25:51] seafile-session.c(382): client id = 4a0c22b8e890a6c535b1b527bc7348dcc4609ee7, client_name = olafs notebook
[12/17/18 16:25:53] seaf-daemon.c(518): rpc server started.
[12/17/18 16:26:38] sync-mgr.c(1309): File syncing protocol version on server https://myshare.uos.de is 2. Client file syncing protocol version is 2. Use version 2.
[12/17/18 16:26:38] sync-mgr.c(545): Repo ‘castlegarden’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:39] repo-mgr.c(3793): All events are processed for repo 2abe53f7-eff6-455c-a466-37debbc1f983.
[12/17/18 16:26:39] sync-mgr.c(545): Repo ‘castlegarden’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:39] sync-mgr.c(545): Repo ‘HSR special issue’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:40] repo-mgr.c(3793): All events are processed for repo d7df788f-e733-402e-bbed-ffbc8761b6ca.
[12/17/18 16:26:40] sync-mgr.c(545): Repo ‘HSR special issue’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:40] sync-mgr.c(545): Repo ‘Austausch’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:41] repo-mgr.c(3793): All events are processed for repo 6687dc13-b964-466a-9af7-98758442dafa.
[12/17/18 16:26:41] sync-mgr.c(545): Repo ‘Austausch’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:41] sync-mgr.c(545): Repo ‘UOS’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:43] repo-mgr.c(3793): All events are processed for repo 2c4c705c-6ce9-49cb-abf2-318fa75891ea.
[12/17/18 16:26:43] sync-mgr.c(545): Repo ‘UOS’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:43] sync-mgr.c(545): Repo ‘PotM’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:47] repo-mgr.c(3793): All events are processed for repo 698bb8f4-7dc9-43f9-9aad-986f29214387.
[12/17/18 16:26:47] sync-mgr.c(545): Repo ‘PotM’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:47] sync-mgr.c(545): Repo ‘Peripherie’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:50] repo-mgr.c(3793): All events are processed for repo 5a62b38f-4262-4d96-bbae-97e07cdbc1a1.
[12/17/18 16:26:50] sync-mgr.c(545): Repo ‘Peripherie’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:50] sync-mgr.c(545): Repo ‘Resettlement Literatur’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:51] repo-mgr.c(3793): All events are processed for repo 5e67a117-5f42-485a-a26c-7879d4c822e1.
[12/17/18 16:26:51] sync-mgr.c(545): Repo ‘Resettlement Literatur’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:51] sync-mgr.c(545): Repo ‘cg-database’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:26:52] repo-mgr.c(3793): All events are processed for repo f8194fcc-162a-43eb-a378-bf1d90b69f6e.
[12/17/18 16:26:52] sync-mgr.c(545): Repo ‘cg-database’ sync state transition from ‘committing’ to ‘initializing’.
[12/17/18 16:26:52] sync-mgr.c(545): Repo ‘Transnationale Erinnerung an Zwangsarbeit’ sync state transition from ‘synchronized’ to ‘committing’.
[12/17/18 16:27:02] repo-mgr.c(3793): All events are processed for repo 5e25b086-23cd-4eb6-ad0e-e156281c2fc3.
[12/17/18 16:27:02] sync-mgr.c(545): Repo ‘Transnationale Erinnerung an Zwangsarbeit’ sync state transition from ‘committing’ to ‘initializing’.

In the applet.log file I found this. It starts with:

[02.12.2018 19:27:03]QObject::connect: No such slot AccountManager::reloginAccount(const Account &)
[02.12.2018 19:27:03]starting ccnet: ("-c", “/home/pinky/.ccnet”)
[02.12.2018 19:27:04]trying to connect to ccnet daemon…

[02.12.2018 19:27:04]connected to ccnet daemon

[02.12.2018 19:27:04]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[02.12.2018 19:27:05][Rpc Client] connected to daemon
[02.12.2018 23:33:23][Rpc Client] connected to daemon
[02.12.2018 23:33:23][MessageListener] connected to daemon
[02.12.2018 23:33:23]Starting the network status detector
[02.12.2018 23:33:23][AutoUpdateManager] cancel all download tasks
[02.12.2018 23:33:23][AutoUpdateManager] clean file caches db
[02.12.2018 23:33:23][AutoUpdateManager] clean file caches
[02.12.2018 23:33:23][Rpc Client] connected to daemon
[03.12.2018 00:48:45]“Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im Pfad /”
[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45][network detector] got a network failure
[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45][api] network error for https://myshare.uos.de/api2/ping/: Fehler bei Netzwerkverbindung.

[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45][api] network error for https://myshare.uni-osnabrueck.de/api2/ping/: Fehler bei Netzwerkverbindung.

[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45][api] network error for https://myshare.uos.de/api2/account/info/: Fehler bei Netzwerkverbindung.

[03.12.2018 00:48:45]QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
[03.12.2018 00:48:45][network detector] resetting the qt network access manager
[03.12.2018 00:48:45][network detector] got a network failure
[03.12.2018 00:48:45][api] network error for https://myshare.uos.de/api2/ping/: Der Zugriff auf das Netzwerk ist nicht gestattet.

[03.12.2018 00:48:45][api] network error for https://myshare.uni-osnabrueck.de/api2/ping/: Der Zugriff auf das Netzwerk ist nicht gestattet.

[03.12.2018 00:48:45][network detector] resetting the qt network access manager
[03.12.2018 00:48:45][network detector] got a network failure
[03.12.2018 00:48:45][api] network error for https://myshare.uos.de/api2/ping/: Der Zugriff auf das Netzwerk ist nicht gestattet.

[03.12.2018 00:48:45][api] network error for https://myshare.uni-osnabrueck.de/api2/ping/: Der Zugriff auf das Netzwerk ist nicht gestattet.

… than there are a lot of repeated error messages and it ends with …

[16.12.2018 21:34:00][network detector] resetting the qt network access manager
[16.12.2018 21:34:00][network detector] got a network failure
[16.12.2018 21:34:00][api] network error for https://myshare.uos.de/api2/ping/: Der Zugriff auf das Netzwerk ist nicht gestattet.

[16.12.2018 21:34:00][network detector] resetting the qt network access manager
[17.12.2018 10:51:32]“Keine derartige Schnittstelle »org.freedesktop.DBus.Properties« des Objekts im Pfad /”
[17.12.2018 14:35:06]id file not found, creating it
[17.12.2018 14:35:06]use existing ccnet id 4a0c22b8e890a6c535b1b527bc7348dcc4609ee7
[17.12.2018 14:35:07]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 14:37:56]seafile rpc is not ready after 16 retry, abort
[17.12.2018 14:37:59]Fehler beim Initialisieren des Seafile-Clients
[17.12.2018 14:37:59][Daemon Mgr] stopping seafile daemon
[17.12.2018 14:37:59]Seafile daemon process exited normally with code 9
[17.12.2018 15:13:54]read id from id file
[17.12.2018 15:13:54]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 15:16:43]seafile rpc is not ready after 16 retry, abort
[17.12.2018 15:16:47]Fehler beim Initialisieren des Seafile-Clients
[17.12.2018 15:16:47][Daemon Mgr] stopping seafile daemon
[17.12.2018 15:16:47]Seafile daemon process exited normally with code 9
[17.12.2018 15:29:49]read id from id file
[17.12.2018 15:29:49]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 15:32:56]read id from id file
[17.12.2018 15:32:57]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 15:35:46]seafile rpc is not ready after 16 retry, abort
[17.12.2018 15:35:52]Fehler beim Initialisieren des Seafile-Clients
[17.12.2018 15:35:52][Daemon Mgr] stopping seafile daemon
[17.12.2018 15:35:52]Seafile daemon process exited normally with code 9
[17.12.2018 15:50:36]read id from id file
[17.12.2018 15:50:36]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 15:52:49]read id from id file
[17.12.2018 15:52:50]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 15:55:39]seafile rpc is not ready after 16 retry, abort
[17.12.2018 15:55:44]Fehler beim Initialisieren des Seafile-Clients
[17.12.2018 15:55:44][Daemon Mgr] stopping seafile daemon
[17.12.2018 15:55:44]Seafile daemon process exited normally with code 9
[17.12.2018 15:56:16]read id from id file
[17.12.2018 15:56:16]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 15:59:05]seafile rpc is not ready after 16 retry, abort
[17.12.2018 15:59:09]Fehler beim Initialisieren des Seafile-Clients
[17.12.2018 15:59:09][Daemon Mgr] stopping seafile daemon
[17.12.2018 15:59:09]Seafile daemon process exited normally with code 9
[17.12.2018 16:04:53]read id from id file
[17.12.2018 16:04:53]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 16:25:50]read id from id file
[17.12.2018 16:25:51]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)
[17.12.2018 16:28:40]seafile rpc is not ready after 16 retry, abort
[17.12.2018 16:28:43]Fehler beim Initialisieren des Seafile-Clients
[17.12.2018 16:28:43][Daemon Mgr] stopping seafile daemon
[17.12.2018 16:28:43]Seafile daemon process exited normally with code 9
[17.12.2018 22:28:27]read id from id file
[17.12.2018 22:28:28]starting seaf-daemon: ("-c", “/home/pinky/.ccnet”, “-d”, “/media/pinky/DATA/Dokumente/Seafile/Seafile/.seafile-data”, “-w”, “/media/pinky/DATA/Dokumente/Seafile/Seafile”)

The ccnet.log file ends with this:

[12/16/18 01:05:44] ccnet-daemon.c(193): starting ccnet client 6.0.4
[12/16/18 01:05:44] …/common/session.c(132): using config file /home/pinky/.ccnet/ccnet.conf
[12/16/18 01:05:44] …/common/session.c(455): socket file exists, delete it anyway
[12/16/18 01:05:44] …/common/session.c(484): Listen on /home/pinky/.ccnet/ccnet.sock for local clients
[12/16/18 01:05:44] …/common/session.c(290): Update pubinfo file
[12/16/18 01:05:44] …/common/session.c(398): Accepted a local client
[12/16/18 01:05:45] …/common/session.c(398): Accepted a local client
[12/16/18 01:05:45] …/common/session.c(398): Accepted a local client
[12/16/18 01:05:45] …/common/session.c(398): Accepted a local client
[12/16/18 01:05:45] …/common/session.c(398): Accepted a local client
[12/16/18 01:05:45] …/common/session.c(398): Accepted a local client
[12/16/18 01:06:25] …/common/peer.c(943): Local peer down
[12/16/18 01:06:25] …/common/peer.c(943): Local peer down
[12/16/18 01:06:25] …/common/session.c(398): Accepted a local client
[12/16/18 01:06:25] …/common/session.c(398): Accepted a local client
[12/16/18 01:06:25] …/common/session.c(398): Accepted a local client
[12/16/18 01:06:26] …/common/session.c(398): Accepted a local client
[12/16/18 01:06:26] …/common/session.c(398): Accepted a local client

I do not have control over the seafile pro server (it is run by my university) but I do have access via web-browser and it still syncs with my Mac-computer.

I would be happy if I would not need to unistall and reinstall the whole seafile client with loosing all my configuration.

Any suggestions how to proceed?


#2

Hello,

I still have the sync problem and still need help to sync again. Meanwhile I tried to uninstall seafile with apt-get purge seafile-cli seafile-gui and reinstall it from the ppa. But nothing changed (curiously purge seems not to delete the config files since I still have the log files from 2017 and the seafile.ini pointing to the old seafile-data directory)

I played a little bit with the sef-cli commands. Seafile can list the remote directories. But not list the local directories. with the stauts command I get this error:

seaf-cli status
Traceback (most recent call last):
File “/usr/bin/seaf-cli”, line 866, in
main()
File “/usr/bin/seaf-cli”, line 862, in main
args.func(args)
File “/usr/bin/seaf-cli”, line 660, in seaf_status
tasks = seafile_rpc.get_clone_tasks()
File “/usr/lib/python2.7/dist-packages/pysearpc/client.py”, line 110, in newfunc
ret_str = self.call_remote_func_sync(fcall_str)
File “/usr/lib/python2.7/dist-packages/pysearpc/named_pipe.py”, line 82, in call_remote_func_sync
self.transport.connect()
File “/usr/lib/python2.7/dist-packages/pysearpc/named_pipe.py”, line 44, in connect
self.pipe_fd.connect(self.socket_path)
File “/usr/lib/python2.7/socket.py”, line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

Maybe this can help to detect the problem? The server is run by my university otherwise I would just switch to owncloud/nectcloud but I have to stick to seafile and realy need to get the sync running.

Desperatly
Olaf


#3

Hi

I also tried to intialize seafile with a brand new instance following instructions on the manual page with the -c and -d option. But still get the error no 111:

pinky@notebook:~/.ccnet$ seaf-cli start -c /media/pinky/DATA/Dokumente/uos-cloud/config-dir
New device id created
Starting seafile daemon …
Started: seafile daemon …
pinky@notebook:~/.ccnet$ seaf-cli status
Traceback (most recent call last):
File “/usr/bin/seaf-cli”, line 866, in
main()
File “/usr/bin/seaf-cli”, line 862, in main
args.func(args)
File “/usr/bin/seaf-cli”, line 660, in seaf_status
tasks = seafile_rpc.get_clone_tasks()
File “/usr/lib/python2.7/dist-packages/pysearpc/client.py”, line 110, in newfunc
ret_str = self.call_remote_func_sync(fcall_str)
File “/usr/lib/python2.7/dist-packages/pysearpc/named_pipe.py”, line 82, in call_remote_func_sync
self.transport.connect()
File “/usr/lib/python2.7/dist-packages/pysearpc/named_pipe.py”, line 44, in connect
self.pipe_fd.connect(self.socket_path)
File “/usr/lib/python2.7/socket.py”, line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

Note:
Internet connection is fine and the owncloud client on my system syncs well with two different servers.

Any suggestion welcome!!!


#4

Seems your university is wiser than you :wink:

Do you have a firewall or just iptables?


#5

As far as I know I have no special firewall installed. Up until december the seafile client did run well and I shure did not install any firewall then but regularly update the system.


#6

Could you please post the output of sudo netstat -tulpen ?


#7
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      123        21121       1658/mysqld     
tcp        0      0 127.0.0.1:38412         0.0.0.0:*               LISTEN      1000       29362       3198/jetbrains-tool
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      0          20943       1326/dnsmasq    
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          20736       906/cupsd       
tcp6       0      0 :::80                   :::*                    LISTEN      0          20405       1617/apache2    
tcp6       0      0 ::1:631                 :::*                    LISTEN      0          20735       906/cupsd       
udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          19090       908/cups-browsed
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           110        17609       882/avahi-daemon: r
udp        0      0 0.0.0.0:34524           0.0.0.0:*                           110        17611       882/avahi-daemon: r
udp        0      0 0.0.0.0:56511           0.0.0.0:*                           65534      20031       1326/dnsmasq    
udp        0      0 127.0.1.1:53            0.0.0.0:*                           0          20942       1326/dnsmasq    
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          21761       1315/dhclient   
udp6       0      0 :::5353                 :::*                                110        17610       882/avahi-daemon: r
udp6       0      0 :::59902                :::*                                110        17612       882/avahi-daemon: r

#8

Try it when seafile starts


#9
I hope I did this well by stop seafile, start seafile and than do the client start  

  pinky@notebook:~/.ccnet$ seaf-cli stop
    pinky@notebook:~/.ccnet$ seaf-cli start
    Starting seafile daemon ...
    Started: seafile daemon ...
    pinky@notebook:~/.ccnet$ sudo netstat -tulpen 
    Aktive Internetverbindungen (Nur Server)
        Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
        tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      123        21121       1658/mysqld     
        tcp        0      0 127.0.0.1:38412         0.0.0.0:*               LISTEN      1000       29362       3198/jetbrains-tool
        tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      0          20943       1326/dnsmasq    
        tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          20736       906/cupsd       
        tcp6       0      0 :::80                   :::*                    LISTEN      0          20405       1617/apache2    
        tcp6       0      0 ::1:631                 :::*                    LISTEN      0          20735       906/cupsd       
        udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          19090       908/cups-browsed
        udp        0      0 0.0.0.0:5353            0.0.0.0:*                           110        17609       882/avahi-daemon: r
        udp        0      0 0.0.0.0:34524           0.0.0.0:*                           110        17611       882/avahi-daemon: r
        udp        0      0 0.0.0.0:56511           0.0.0.0:*                           65534      20031       1326/dnsmasq    
        udp        0      0 127.0.1.1:53            0.0.0.0:*                           0          20942       1326/dnsmasq    
        udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          21761       1315/dhclient   
        udp6       0      0 :::5353                 :::*                                110        17610       882/avahi-daemon: r
        udp6       0      0 :::59902                :::*                                110        17612       882/avahi-daemon: r

#10

Do you not use the GUI?


#11

I did use the GUI but the GUI does not start at all (see my very first post from december). So I tried to get closer to the problem by using the commandline.


#12

I just tried start the GUI client. I took a while until the final error message from the client. Meanwhile I did the sudo command but output seems the same:

Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      123        21121       1658/mysqld     
tcp        0      0 127.0.0.1:38412         0.0.0.0:*               LISTEN      1000       29362       3198/jetbrains-tool
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      0          20943       1326/dnsmasq    
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          20736       906/cupsd       
tcp6       0      0 :::80                   :::*                    LISTEN      0          20405       1617/apache2    
tcp6       0      0 ::1:631                 :::*                    LISTEN      0          20735       906/cupsd       
udp        0      0 0.0.0.0:631             0.0.0.0:*                           0          19090       908/cups-browsed
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           110        17609       882/avahi-daemon: r
udp        0      0 0.0.0.0:34524           0.0.0.0:*                           110        17611       882/avahi-daemon: r
udp        0      0 0.0.0.0:56511           0.0.0.0:*                           65534      20031       1326/dnsmasq    
udp        0      0 127.0.1.1:53            0.0.0.0:*                           0          20942       1326/dnsmasq    
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          21761       1315/dhclient   
udp6       0      0 :::5353                 :::*                                110        17610       882/avahi-daemon: r
udp6       0      0 :::59902                :::*                                110        17612       882/avahi-daemon: r

#13

That causes the socket error. You have to initialize ccnet for cli use. What client version?


#14

I did a fresh intialisation for the cli client:

pinky@notebook:~/.ccnet$ seaf-cli init -c /media/pinky/DATA/Dokumente/uos-cloud/config-dir -d /media/pinky/DATA/Dokumente/uos-cloud/parent-dir
Writen seafile data directory /media/pinky/DATA/Dokumente/uos-cloud/parent-dir/seafile-data to /media/pinky/DATA/Dokumente/uos-cloud/config-dir/seafile.ini
pinky@notebook:~/.ccnet$ seaf-cli status
Traceback (most recent call last):
  File "/usr/bin/seaf-cli", line 866, in <module>
    main()
  File "/usr/bin/seaf-cli", line 862, in main
    args.func(args)
  File "/usr/bin/seaf-cli", line 660, in seaf_status
    tasks = seafile_rpc.get_clone_tasks()
  File "/usr/lib/python2.7/dist-packages/pysearpc/client.py", line 110, in newfunc
    ret_str = self.call_remote_func_sync(fcall_str)
  File "/usr/lib/python2.7/dist-packages/pysearpc/named_pipe.py", line 82, in call_remote_func_sync
    self.transport.connect()
  File "/usr/lib/python2.7/dist-packages/pysearpc/named_pipe.py", line 44, in connect
    self.pipe_fd.connect(self.socket_path)
  File "/usr/lib/python2.7/socket.py", line 228, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 111] Connection refused

#15

I installed the seafile from the ubuntu ppa repository and did before an apt-get update. But I do not know which version this is, I belife it should be an current version. I did not found any command to get the version number from seaf-cli (-v did not work).


#16

The first line in the log-file I posted in my very first posting it says:

[12/17/18 16:25:51] seaf-daemon.c(491): starting seafile client 6.2.4

Thus at least I am on that version. But as I said I installed it fresh today from the repository


#17

Try to compile version 6.2.9. with ccnet, I believe you got the issue during the removal of libsearpc. Or if you are one of those who like snaps, try sudo snap install seafile

Weird. On my Ubuntu machine the latest ppa version is 6.2.9. But I’m on bionic.


#18

Hmm, I am not that Linux savy to compile it myself. And I think snaps do not work on ubuntu 16.04 base, isn’t it introduced later on?


#19

NO they work, but compiling seafile is also easy. You just need space for the development packages.


#20

Do you know how I can get info about the installed seafile version? The log is from early december (the last time seafile worked) so it might be updated already to version 6.2.9 with apt-get update apt-get dist-upgrade. I do that regularly