I also have encrypted libraries on the server, not sure if that comes into play at all. Sometimes this caused the problem of the android client overwriting a newer server copy. If I opened a Word doc, PDF, etc in this program from the Seafile client, then it would somehow think the file was changed an eventually upload over the server copy. I ran into a similar issue with my android client uploading files that had not changed when I opened them in an Office App (WPS Office I think) on my phone. I am pretty sure that opening it in this app creates a separate local copy that Seafile is not keeping an eye on, so it doesnt try to upload the copy again. I used KeePassDroid on my Android phone to read my keepass db. I occasionally have an issue with file conflicts, in which case a conflict database is saved that I can merge, but not had an old database show up. I also use Keepass (2.28) on a few Windows computers.
I know that I can manually upload a file in the Android client, but does the app contain any “feauture” to auto-upload a file if it things it was changed? I can not find any occurrence of either the obj_id or commit_id of the 2)-file in the access.log files…Īs far as I can tell the Android client caused the problem. Only log entries in nginx access.log at around that time: Looking at the logs it looks pretty normalĤ days ago (Seafile mouse hover: 6. Uploaded (“7 days ago”) by “N-Laptop” (Windows Client) I went through the nginx access.log, at least for an hour or two …
0 kommentar(er)
