Single files stop to be synched

Hello,

I have the problem that single files I was working on stop to sync for unknown reasons. Sometimes they get the orange icon, sometimes they are even with the green icon and pretend to be synched perfectly.

Even manually synchronizing again the whole library does not help.I would hope to get the latest file from the server but instead my local file Version appears again.

I have the feeling that this happens only with people in the team who use their seafile account on more them one device (i.e. desktop pc plus laptop). We use macOS.

Does someone have an idea how to solve this problem or has the same issue?

This behavior on macOS, where specific files seem stuck or show incorrect status icons, can usually be diagnosed and resolved with the following steps:

1. Check the “File Sync Errors” Dialog

The most direct way to see why a file isn’t syncing is through the client itself:

  • Click on the Seafile tray icon.
  • Select File sync errors.
  • This window should list specific files and the reason for the failure (e.g., “Permission denied”, “File locked”, or “Conflict”).

2. Reset the FinderSync Extension

Incorrect icon overlays (orange when finished, or green when not synced) are often caused by the macOS FinderSync extension becoming unresponsive. You can restart it without rebooting:

  • Open Seafile Settings.
  • Uncheck Enable FinderSync Extension and click OK.
  • Re-open Settings, re-check Enable FinderSync Extension, and click OK.

3. Check for File Locks

On macOS, some applications (like Microsoft Office or specialized creative tools) can place an exclusive lock on a file while it is open. Seafile cannot sync a file that is actively locked by another process. Try closing the application using the file to see if the sync completes.

4. Inspect the Logs

If the steps above don’t help, the seafile.log will contain the specific technical error.

  • You can find the logs at: ~/.ccnet/logs/seafile.log (or via the menu item: Open Logs Folder).
  • Look for lines containing “Failed to write chunk”, “Permission denied”, or “Upload failed”.

5. Multi-device Conflicts

Since you mentioned using multiple devices, ensure that there aren’t “Conflict” files created in the folder (e.g., filename (SFConflict username date).ext). If Seafile detects simultaneous changes, it may stop updating the original file to prevent data loss, requiring you to manually resolve the conflict.

For more details on troubleshooting macOS sync issues, you can refer to similar discussions in the Seafile Forum.

Had a similar issue once - in my case it turned out to be a locked file or permission problem. You might want to check the ‘File sync errors’ list in the client, it usually tells exactly why that specific file isn’t syncing. Also try closing any app using that file and maybe re-sync the library if it’s stuck. That fixed it for me.