Hello @Torsten ,
Could you describe the operation steps in more detail, from the start of synchronization until the error occurs?
Hello @Torsten ,
Could you describe the operation steps in more detail, from the start of synchronization until the error occurs?
Thanks for the prompt reply.
When I am switching in the client’s GUI between the different accounts, at some point in time the library of one of my accounts isn’t synchronized anymore. This does not happen all the time I am switching the accounts, but quite regularly. The last time this happened, I found the following related log entries (strings in ++ for anonymization):
applet.log:
[13.08.2025 09:24:14] unsync local library ++hash++/++lib-name++ because you don't have permission to access it
(/root/seafile-client/src/repo-service.cpp:316)
seafile.log:
[08/13/25 09:24:17] repo-mgr.c(7007): Removing store ++home++/.ccnet/seafile-data/deleted_store/commits/++hash++
[08/13/25 09:24:17] repo-mgr.c(7007): Removing store ++home++/.ccnet/seafile-data/deleted_store/fs/++hash++
Btw: Is there a possibility to limit the size of the log files?
Hello @Torsten ,
Do your two servers share seafile storage data or seafile database? If you keep only one server configured on the client, does the problem still occur?
Hello @feiniks ,
While playing around in order to answer your questions, I might have found the cause of unintended unsync’ing. This only happens if
After changed the Name in all accounts to unique strings, I wasn’t able to reproduce the issue anymore. Let’s hope that this persists.
Is Name used somewhere as a sort of user name? Maybe related, in my SeaDrive logs I have seen something like:
adding account ++sevrer-url++ ++username++ ++Name++_++server-url++
where Name is actually combined with the server url. The resutling identifier(?) is the same for different accounts having the same Name in the profile.
Hello @Torsten ,
The client determines the ownership of a synced library based on the server url and username. If both are the same, then when switching accounts, since the other account does not have the corresponding library on the server, but the client can still find the corresponding library locally based on the server url and username, the synchronization will be stopped.
Hello @feiniks ,
Do you mean by “username” the login data or the name that can be chosen in the profile settings? The latter can be freely chosen and is most probably the same if one person has several different accounts on the same server (with different login-usernames). And this issue did not show up in version 9.0.13.
Hello @Torsten ,
Thank you for your feedback. Here, “username” refers to the username in the profile settings. Therefore, if two accounts have the same username, it will cause an incorrect unsynchronization. We will optimize this issue in the next release.