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?