Seadrive does not sync properly, server error

Hey there,

I am using Seafile with docker image seafileltd/seafile-pro-mc:13.0-latest, SeaDrive client 3.0.20, macOS Sequoia 15.6.1 and Tahoe 26.3.

I noticed issues currently (I don’t know for how long they lasted now) where the SeaDrive client on my two macs does not sync properly. That means, when e.g. trying to copy a directory from a library, it apparently does not download those files. Finder only shows “preparing to copy”, SeaDrive tray icon does not show download bandwidth being used and it never finishes. Accessing single files works most of the time but it takes a really long time until changes are reflected in SeaHub or the respective other machine.

Client logs seem fine, sometimes I get this error in the server log:

[fileserver] [2026-03-21 18:25:55] [ERROR] path /repo/6be91f8d-796c-49e6-a3a0-7b3c6e3ac73a/commit/HEAD/ internal server error: Fast forward merge for repo 6be91f8d-796c-49e6-a3a0-7b3c6e3ac73a is failed: stop updating repo 6be91f8d-796c-49e6-a3a0-7b3c6e3ac73a after 3 retries

I googled that but didn’t find anything useful.

Additionally, in my user account there are no linked devices despite me using two macs and an iPhone.

Unfortunately I don’t even know where to start troubleshooting - all worked fine for weeks. I tried reinstalling SeaDrive, rebooting my macs a couple of times, nothing helps.

Thanks for your help!

EDIT: Just found a lot of logs like this one in the MariaDB container logs:

2026-03-21 17:58:08 530 [Warning] Aborted connection 530 to db: ‘seafile_db’ user: ‘seafile’ host: ‘172.19.0.5’ (Got an error reading communication packets)

This error is usually caused by concurrent updates to the library, or it fails to update the library due to database errors. If you don’t have highly concurrent updates, you should check the connection from Seafile server to your database.