Seaf-cli not sync local files after upgrade to Seafile 8.0.7

Seafile Client
,
1

Hello,
I have been a well satisfied Seafile CE Server user since over 3 years - Thanks for developing it!

Lastly I have updated it to version 8.0.7 (from 7.0.5 - where seaf-cli works good) and unfortunately local files syncing stopped working properly.

I’m using Raspberry Pi 4 with Debian Buster distro. Since beginning I have used seaf-cli together with Seafile to sync local files on Raspberry. Seafile with MySQL (MariaDB)

After upgrade (clean install was also tried) the seaf-cli sync folder going through all statuses (commiting, uploading, syncronized) and the files shows in Seafile webside but they are just “shells” without content (cannot be downloaded or displayed).

I noticed that seafile-data folder size is also not increased.
When I upload files through website, everything works correctly.

When uploading files, I noticed that the seafile-data folder increases in size and then shrinks back to its previous size (this behavior repeats over and over again when uploading files)

After looking into seaf-cli logs:

[08/23/21 11:11:10] seaf-daemon.c(511): starting seafile client 8.0.3
[08/23/21 11:11:10] seafile-session.c(384): client id = fd1214c9a0358f3b4fc6f1f22898b94451154560, client_name = unknown
[08/23/21 11:11:10] seaf-daemon.c(538): rpc server started.
[08/23/21 11:11:11] sync-mgr.c(1341): File syncing protocol version on server http:/ /localhost is 2. Client file syncing protocol version is 2. Use version 2.
[08/23/21 11:11:12] sync-mgr.c(583): Repo 'PABLOS_CLOUD' sync state transition from 'synchronized' to 'committing'.
[08/23/21 11:11:12] repo-mgr.c(3946): All events are processed for repo ce412cee-ee05-46a8-8b25-729c3cbaf651.
[08/23/21 11:11:12] sync-mgr.c(583): Repo 'PABLOS_CLOUD' sync state transition from 'committing' to 'initializing'.
[08/23/21 11:13:02] sync-mgr.c(583): Repo 'PABLOS_CLOUD' sync state transition from 'synchronized' to 'committing'.
[08/23/21 11:13:02] repo-mgr.c(3946): All events are processed for repo ce412cee-ee05-46a8-8b25-729c3cbaf651.
[08/23/21 11:13:02] sync-mgr.c(583): Repo 'PABLOS_CLOUD' sync state transition from 'committing' to 'uploading'.
[08/23/21 11:13:02] http-tx-mgr.c(1161): Transfer repo 'ce412cee': ('normal', 'init') --> ('normal', 'check')
[08/23/21 11:13:02] http-tx-mgr.c(1161): Transfer repo 'ce412cee': ('normal', 'check') --> ('normal', 'commit')
[08/23/21 11:13:02] http-tx-mgr.c(1161): Transfer repo 'ce412cee': ('normal', 'commit') --> ('normal', 'fs')
[08/23/21 11:13:02] http-tx-mgr.c(1161): Transfer repo 'ce412cee': ('normal', 'fs') --> ('normal', 'data')
[08/23/21 11:13:02] http-tx-mgr.c(1161): Transfer repo 'ce412cee': ('normal', 'data') --> ('normal', 'update-branch')
[08/23/21 11:13:02] http-tx-mgr.c(1161): Transfer repo 'ce412cee': ('normal', 'update-branch') --> ('finished', 'finished')
[08/23/21 11:13:02] sync-mgr.c(583): Repo 'PABLOS_CLOUD' sync state transition from 'uploading' to 'initializing'.
[08/23/21 11:13:02] sync-mgr.c(882): Removing blocks for repo PABLOS_CLOUD(ce412cee).

I do not understand why seaf-cli remove blocks after uploading, so I assume that problem is related to this sync-mgr.c(882) file.

Can you help me with understanding this?

2

Hi,
I am still looking for the cause of the problem. A new observation is that seaf-cli starts deleting all commits as soon as it starts.

use case:

  • add repo and some data
  • restart Raspberry and start seafile, heahub and seaf-cli one by one
  • when “seaf-cli start” it clears all the data from library (I must mention that I did not synchronize any library with seaf-cli before)

It looks that here is something bad with seaf-cli. It simply do something with “seafile-data” structure and this causes all problems.
Log from seaf-cli after start:

[08/25/21 13:52:12] seaf-daemon.c(511): starting seafile client 8.0.3
[08/25/21 13:52:12] seafile-session.c(384): client id = 66d6d1ac60b5b77b608a5477e01ac82e4d50a7d5, client_name = unknown
[08/25/21 13:52:12] seafile-session.c(514): Moving commits for deleted repo 5bde99c2-6cf8-4eab-9055-7105c66707ab.
[08/25/21 13:52:12] seaf-daemon.c(538): rpc server started.
[08/25/21 13:52:12] seafile-session.c(514): Moving commits for deleted repo 327f6daf-3bc6-41cd-995d-73e60f684ac8.
[08/25/21 13:52:12] seafile-session.c(514): Moving fs for deleted repo 5bde99c2-6cf8-4eab-9055-7105c66707ab.
[08/25/21 13:52:12] seafile-session.c(514): Moving blocks for deleted repo 5bde99c2-6cf8-4eab-9055-7105c66707ab.
[08/25/21 13:52:13] repo-mgr.c(5933): Removing store /home/pi/seafile/seafile-data/deleted_store/commits/5bde99c2-6cf8-4eab-9055-7105c66707ab
[08/25/21 13:52:13] repo-mgr.c(5933): Removing store /home/pi/seafile/seafile-data/deleted_store/commits/327f6daf-3bc6-41cd-995d-73e60f684ac8
[08/25/21 13:52:13] repo-mgr.c(5933): Removing store /home/pi/seafile/seafile-data/deleted_store/fs/5bde99c2-6cf8-4eab-9055-7105c66707ab
[08/25/21 13:52:13] repo-mgr.c(5933): Removing store /home/pi/seafile/seafile-data/deleted_store/blocks/5bde99c2-6cf8-4eab-9055-7105c66707ab

maybe now some of you can help with finding solution of that problem?

3

Found solution:

I accidentally mixed seaf-cli “seafile-data” folder with seafile “seafile-data” folder.
They should be separated (different destinations)
So as an example when perform an seaf-cli init you should use:

seaf-cli init -d /home/pi/seafile/seafile-data/seafile-client

and NOT:

seaf-cli init -d /home/pi/seafile

like I did.