Solved - [Sea RPC] Bad response: 102 processor is dead


#1

Hi there,

I recently upgraded an Ubuntu Desktop box to 18.04 and now I realised that Seafile data is not up to date. Changes are seen in the GUI client (6.1.8) but not synced to disk.
So I decided to start from scratch (it’s anyway a PC I don’t use very often) but I always run into the same issue:
Deleted ~./Seafile and ~./ccnet directories, logged in through the client, everything is fine, all libraries shown. As soon as I start to sync a library nothing happens.

Applet.log shows this:
[04.12.2018 10:09:51][Sea RPC] Bad response: 515 peer down.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.
[04.12.2018 10:09:51][Sea RPC] Bad response: 102 processor is dead.

Not sure how to debug this. The box has been running fine w/o any issues for years. All other (Windows) clients and the Seafile server itself are also running fine …


#2

I removed the client and all its dependencies and after reinstallation it seems to work now,