Nextcloud desktop client conflict without a reason #943
Comments
|
I manage a nextcloud and this has happened multiple times to two of my users too. The fles have all been Excel files. There is nothing in the log. Only one user using the system at the time and continuous online connection, so an actual conflict not possible, file marked as conflicted after saving. |
|
I got into this problem too. It's really annoying. I know I'm the only one person, who make changes to the file about to be synced with Nextcloud, but for some reason, the conflicted copy file is created, resulting in refusal of successful upload. Maybe it's some kind of race condition? How else would Nextcloud have newer version of the file than me? I'm absolutely 100% sure I'm the only one editor of the file. |
|
Okay, it happened again yesterday. I'm seriously thinking about migrating to Dropbox or something, it's taking too much effort, to find out which of the copies are latest, in large files especially. |
|
I still have the same issue. I tried server 13.x to 15.0.7 with desktop clients up to recent version 2.5.2git. |
|
Same problem here, i get it on windows 10 with .pptx and .docx files, also sure that i am the only one editing the files. |
|
I regret jumping from owncloud to nextcloud... |
|
I believe I have the same problem: one of my user keeps having conflicts on the file he is working on, for no reason as he is the only owner of the file and the only one editing it. More precisely, his text editing software keeps telling him something like "the file has changed on the disk, do you want to reload it?", because nextcloud keeps undoing his changes. This is a really big problem, he cannot work anymore. |
|
We've a similar issue here. On one client it was edited and on the other client we got a conflct |
|
I have the same issues, even with the 2.6 client on linux. I have only a single client in use, and I keep getting conflicts. Please let me know how I can help to get this fixed! |
|
I have the same problem too. Windows client 2.6. Every time I am editing MS Office or Libreoffice document and do "Save as" previous version gets conflicted copy. Sever is v 17 on docker. Any help idea? Thanks. |
|
Seems I also run into this issue: Nextcloud Server 16.0.5 User is the only one editing a file, it's a xlsx file, instantly there's a conflict, no one else touched the file. |
|
Same problem here. I work exclusively on the files alone. For docx files I regularly get conflicted copies. Nextcloud Desktop Client Version 2.6.0stable-Win64 (build 20190927) on Windows 10 |
|
Potentially related |
|
nextcloud client package maintainer on Fedora/EPEL here. Example of conflict |
|
I'm gonna give my personal feedback as I'm suffering from this since years. Since owncloud 9 or something. I have the PortableApp launcher installed on my nextcloud folder. Both client are not live at necessarily the same time. For instance, I regularly have the following conflicts:
Anyway there's never been an edit of these files on both clients at the same time: as I stated above, I turn on my home machine after my work client has done the updates, so the update path is very clear, it should go from work -> home, and the file timestamp are definitely not ambiguous. Also, one last thing: the file with the 'conflict' in its name is always a previous version or something older. I now usually search+delete all the 'conflicted copy' files to get rid of the conflicts warnings. |
|
I've the same problem, synchronizing a developpement folder with Wing / Wingware. And this is really, really annoying ! |
|
I have the problem when working on a Godot project in a synchronized folder. Unfortunately Godot will just silently accept external changes. So a fixed bug will suddenly reappear without much warning. When it happens the timestamp of the downloaded file from the server is older than of the conflict file. |
The same problem here. Nextcloud Desktop is finally dangerous to use ! This is incredible, how can the client replacing local more recent file with older network file ? |
|
Is there any response from Nextcloud team? Thanks. |
|
It's happening the same here, today my client is downloading 40GB of "conflicted files" he never touched for years. |
|
Hey all, I'd like to reproduce the issue but it's quite hard to reproduce it. Could anyone try to provide a reproducible pattern? For example and test file / some test server config hints? And does this also occur with our 2.7 Beta 1? Just to be sure that we didn't miss a fix from master in our 2.6 branch: Thanks! |
I've seen many people complaining while editing |
|
New the the GitHub support but I have the same issue on the latest android app with a txt file I upload of sms and call logs everynight and one of my clients has the issue with Outlook pst and QuickBooks files. I don't know if that's all there is. I'm on 18.0.3 but the issue started some time around upgrading to nc18.0.1 or later |
@Orm1server this is the issue tracker of the desktop sync client. For Android issues, please check here: |
|
Hello sorry if I wasn't clear, my issue is the Android client, my customers issue is 2.6.4 windows 10 client. |
|
Hello, The client conflicts the opened libreoffice files, when we save the file, and sometimes even when we don't do anything. It seems the conflicts are produced every 15min, problem with crontab job? |
|
Hey People, SuspicionTherefore, my ping can reach easily 200ms. I suspect the transaction latency influenced by the ISP and the location to be the case at least for some people in this issue. This could match with the behavior appearing on mobile devices as well as being resolved for @RedKage when changing the internet connection. Possibilities to verifyCan any of you that have the problem check if it still appears when syncing in a local network with the Nextcloud server to eliminate most network latency. Possible hintsSadly I didn't find any document about the Nextcloud sync protocol that describes the detailed handling but Nextcloud Docs on conflict also say:
Where someone else could also be your submitting a change with a delay while your program is updating locally quite quickly after you submit because you use some kind of auto-save feature. After that the remote version of the file would have changed later than the local version and would produce a conflict in the next sync cycle. Possible workaroundsFor users For Developers
Suggestions for solving the Problem.Use a revision-id (instead of the timestamp) that is coupled to the document state(instead of the creation time) and requires the latest revision-id to be submitted with the newly updated document in order to not create a conflict-file. Hope I didn't miss something out on this. |
|
Additionally, I found this in the Appendix of the documentation:
In the event a file has changed on both the local and the remote repository since the last sync run, it can not easily be decided which version of the file is the one that should be used. However, changes to any side will not be lost. Instead, a conflict case is created. The client resolves this conflict by renaming the local file, appending a conflict label and timestamp, and saving the remote file under the original file name. This would indicate that Nextcloud could fix the issue by using the existing ETag like I described with the revision id. And would indicate that the unwanted behavior I described before could take place by design. |
|
@er-vin We are also meeting this issue with the latest version of the desktop client (3.1 and up). I have the feeling that I see that when I save (or rename) the document while the sync was not completed yet. But I can't confirm nor reproduce the exact pattern. Could you please share the procedure to share the logs which can help you analyse the issue? |
|
With 3.1 you can just click on the create debug archive button in the settings dialog shortly after the issue showed up. |
|
I have this problem with linux and windows clients on one specific instance and can not get rid of it. I have two other instances on the same server and same clients, which work fine though. Config is the same on all instances apart from the obvious URL, datadir, database, etc. part. As others mentioned, the issue occurs every time I save a file and try to update the file afterwards. I am using groupfolders on all instances. |
|
Same here, conflict issues on desktop client. Here's my setup: I use external storage to map remote user homedirs to Nextcloud through SFTP. Everything is working pretty fine with WebUI. ServerOS: Ubuntu 20.04.2 LTS Remote SFTP hostOS: Ubuntu 18.04.4 LTS ClientOS: Ubuntu 20.04.2 LTS To reproduce issue :
I watched access/modify/status change time of the file locally and on remote server
local:
Access: 2021-04-08 17:31:22.815919499 +0200
Modify: 2021-04-08 17:31:22.815919499 +0200
Change: 2021-04-08 17:31:22.815919499 +0200
nc-server:
Access: 2021-04-08 17:31:27.201098437 +0200
Modify: 2021-04-08 17:31:27.201098437 +0200
Change: 2021-04-08 17:31:27.230100431 +0200Sync takes about 4s. (17:31:22 -> 17:31:27)
local:
Access: 2021-04-08 17:31:22.815919499 +0200
Modify: 2021-04-08 17:31:49.267835816 +0200
Change: 2021-04-08 17:31:49.267835816 +0200
nc-server:
Access: 2021-04-08 17:31:27.201098437 +0200
Modify: 2021-04-08 17:31:53.635919403 +0200
Change: 2021-04-08 17:31:53.635919403 +0200Here again sync takes about 4s. (17:31:49 -> 17:31:53)
local:
Access: 2021-04-08 17:31:22.815919499 +0200
Modify: 2021-04-08 17:32:11.687764448 +0200
Change: 2021-04-08 17:32:11.687764448 +0200
nc-server:
Access: 2021-04-08 17:31:27.201098437 +0200
Modify: 2021-04-08 17:31:53.635919403 +0200
Change: 2021-04-08 17:31:53.635919403 +0200And watched the sync fails...
local:
Access: 2021-04-08 17:31:53.000000000 +0200
Modify: 2021-04-08 17:31:53.000000000 +0200
Change: 2021-04-08 17:32:20.587736013 +0200
nc-server:
Access: 2021-04-08 17:31:27.201098437 +0200
Modify: 2021-04-08 17:31:53.635919403 +0200
Change: 2021-04-08 17:31:53.635919403 +0200It is not clear why first write operation is successfully synchronised whereas the following one fail (might be a coincidence in my case, if someone wants to check same commands i did on his setup). touch file.txt
echo "1st entry" >> file.txt
echo "2nd entry" >> file.txtSync failed on second echo on my side It's been +2 years the issue was opened, I am quite surprised it hasn't been addressed yet. |
|
@elchusco Thanks for your detailed report. Version 2.6.2 Is a pretty old version. The most recent pre release is 3.2.0-rc3. We will release the final release 3.2.0 in a few days. There have been a lot of changes in the sync engine. Maybe a newer release solves your problem. That is the link to the latest pre release: #943 (comment) Having that said, I tried to take the same steps to reproduce the problem (with the newest version) but was not successful. However, I use no external storage. |
|
@FlexW That's great news, I didn't report it later on, but I did exact same steps with Nextcloud-3.1.3-x86_64.AppImage client and observed the same results as with nextcloud-desktop 2.6.2-1build1 client. Thank you for testing 😉 I'm looking forward to test 3.2.0 version, I'll probably try pre-release. |
|
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
|
@FlexW Hi, Repeated same operations on latest client version for Linux, Nextcloud-3.2.0, but nothing different. I didn't had enough time to test it without external storage though. I'll try to provide more information as soon as I can. |
|
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
|
The same is happening with the latest Nextcloud and Nextcloud Desktop 3.2.2 on Ubuntu and Windows 10.... What more info can we collect and share? |
|
Please provide the desktop client logs:
|
|
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
Sure thing. That's the least I can do to get closer to solving this, after having this bug for the past few years on different machines.
Clicking that new button does nothing on 3.3.1. Clicking it does not even generate any debug lines when I opened the logwindow using the method below.
Thank you, that one worked as intended. Here you get a sanitized and cleaned-up log (at least I hope it's sanitized enough). I have write permission to everything on that server and it all works without any error messages via the web UI, just not the desktop client. I have a second server connected with that desktop client, which never had that problem. I do have that same setup on my laptop though, and I am regularily running into the same permission problem as shown here. |
|
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
Really GitHub? 😐 |
|
This is probably aduplicate of #2467 I suggest we let this one closed and just focus on the other one. |
|
Duplicate of #2467 |
|
Unfortunately now the newer issue is more active, so we cannot keep this older one. |
and others
Nextcloud desktop client conflict without a reason.
Expected behaviour
Updates from the single client should be sent to the server. If files change, new versions should be sent to the server.
Actual behaviour
Initial synchronization works. The subsequent synchronizations fails with "Conflict: Server version downloaded, local copy renamed and not uploaded."
Steps to reproduce
Client configuration
Client version:2.5.1
Operating system:
Ubuntu 18.04 Neon flavour
OS language:
English
Qt version used by client package (Linux only, see also Settings dialog):
no QT info in settings dialog
Client package (From Nextcloud or distro) (Linux only):
http://ppa.launchpad.net/nextcloud-devs/client/ubuntu
Installation path of client:
/usr/bin/nextcloud
The text was updated successfully, but these errors were encountered: