-
Notifications
You must be signed in to change notification settings - Fork 797
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Regression issue: sync errors with latest desktop client #7171
Comments
Same issue, got 2TB of files on server and local side. All synchronization fails after i updated the desktop client. On my other computer, i did not update the client, and it remains functional. Also, the main dialog would not open on the desktop client, i can only see the error messages in the settings page. |
This seems to apply to Mac OS X Desktop client also. As my customer reports same issue, while they haven't yet downgraded the client, I have urged them to do so. I don't have a Mac myself so I can't verify. On windows 11, with all latest updates, the desktop client simply crashes now with 3.14, 3.13.3, 3.13.4 complaining about: |
I have the same issue with windows client and there are no errors in server log. |
@mgallien this is an urgent call for action due to a high impact and regression issue with the latest desktop client. |
I have same problem. I cannot upload files larger than 10 MB via Windows (11) desktop client - ver 3.14. Uploading via web interface works fine. |
I have the same problem. Error log desktop client v3.14 "GOAWAY received, cannot start a request" |
Yup, same issue here on Ubuntu Desktop. |
Oh god! I was diagnosing my server all day! I just found this thread... Turns-out this release is simply broken! I can't give more context than what was already given... reverting to 3.13.[...] fixes it! |
same here on MacOS 15.0 |
Same here. Server version 30 with latest windows client, using VFS on windows 11 (latest updates as well). First the "connection close" message on a few select files, and now I get spammed with "Conflict when uploading a folder. It's going to get cleared" messages, NC renders the filesystem very unstable as well. Reverting to 3.13.4 fixed the issue. |
Yes, I was also debugging this issue myself late in the night for hours. Until I reverted back a desktop client version, the error messages were very misleading as if the server was the problem (spoiler: the server is not the issue)! You are right, all releases of 3.14.0 are borked under Linux. It's insane they even shipped this release. Did they even test it? It's even more insane nobody from Nextcloud responded yet to this ticket. It's a huge regression issue, large impact and high likelihood. Nextcloud didn't do anything for days now. The best thing they could do for now is pull back the release (or if they have a quick fix, fix it asap). For anybody reading this, please go to your Desktop client where the error occur(s)/occurred and click at Setting -> General -> "Create Debug Archive" and upload the file here. I'm not a nextcloud developer.. but I might blame potentially one of these PRs (or multiple): #6986 or: #6965, or: #6588 or even: #6987. Which feels like potential candidates of the root-cause of this issue. |
I am seeing the same thing. But I can add that there are lines like this in the webserver access log:
and corresponding lines in nextcloud log,
I don't know if this helps. |
This comment was marked as resolved.
This comment was marked as resolved.
Yep they need to just re-release 13.13.4 as a .1 to this version, been days now |
Experiencing this too |
Same issue with windows client. |
Shame the logs don't show much of anything besides the "connection closed" message. |
Same problem for me, after updating to 3.14 none of my files would synchronize, even after deleting the target folder and all app data (in .config, .cache and .local/share) and completely setting up the application from scratch. After downgrading to 3.13.4 everything worked again. I'm using NixOS and the Nix package. |
Debug-Archiv Windows-Client: Download... |
I believe I was correct... It's this PR that caused the issue: #6986 And I notice that the change is reverted in this PR (and just recently merged. aka 1 hour ago): #7182 I will update you, but I'm not part of the Nextcloud dev team. |
Same here.. Worked by reverting, but apart from people coming here... it's quiet sad for all the rest with auto-update who are stuck at the moment. Good luck! |
Unfortunately, Nextcloud has not yet withdrawn the update or released a patch. |
I am sorry for that, but I will call-out devs who contributed in the last few weeks to get a bit of attention on this major issue that impacts operations for many! Symptoms are server error messages that are in fact not server errors, but client errors ("connexion closed", "unauthorized", "server responded [blank]", etc.) The server does not even have info level errors in the log. If you are not the person that can deliver an emergency patch, could you please find who can? This issue makes Nextcloud client completely unusable at the moment, and is delivered as an auto-update for many user! (If calling devs here is not accepted, please let me know, and I will remove that message... I think we are just getting a little desperate for a word from the dev team to get our users back on track!) |
@Webbeh there are also daily builds for linux and windows https://download.nextcloud.com/desktop/daily/ |
Good to know, thanks! |
Same here. Enterprise production server and home lab server have the same behavior as the client (v. 3.14.0) when syncing many small files or even a few large files |
I understand that, but the issue is that I can't install a daily build on all my user's machines, just to reinstall a production version in a couple days from now... Nextcloud is a commercial product now, aiming to compete with G-Suit and O365, and should be treated as such! (I don't mean to sound harsh here, that is good news, it simply implies some changes in philosophy!) Edit: |
I can confirm that I have exactly the same behavior using Windows 11. If I'm not mistaken mine was showing |
I really don't understand how something like this could be released. Any common end-to-end test should immediately flag such a breaking issue. You need to step up your quality control. |
I don't think shaming is the solution, I am sure they did tests that did not include the exact situation we are in... "$h!t happens" as we say! |
Don't get me wrong, I really appreciate the work done, especially considering it's completely free, but maybe more beta testing should be done before release, it just creates unnecessary emotion and stress for everyone :). |
@bendschs The "free" argument doesn't fit exactly here because Nextcloud's development is funded by enterprise contracts. So this sort of thing should never happen. |
sure, just saying that i am probably not in the position to complain as i am not a paying customer. |
hello |
The first link gives a build with the GUI being extremely slow to respond (same as with the 3.14 official release) and it does not sync the files. I can't move the window around easily. The sync starts but doesn't give an error and is just stuck at the initial "synchronizing" phase. Took 10 minutes to click the "create debug archive" button and it just freezes explorer. Note that I am syncing the "Documents" windows folder with Nextcloud (where NC offers to save the debug archive at first) and I do NOT have onedrive installed so they don't eat each other. Basically this is the same issue as 3.14 before the "connection timeout" message happens. EDIT : also note that I rebooted the computer as prompted by the installer. |
Exactly the same behaviour with the second link but seems more responsive, I actually managed to create a debug archive. I am not expecting it to show much to be honest, besides the millions of lines like those :
No clue what those mean but I definitely don't have this in the 3.13.4 instance. Across all the sync folders, I have about 3TB of files synced spread across 48000 folders and 355500 files (according to |
Furthermore, after reverting back to 3.13.4 again, I got the same issue as last time : the charset of the folder syncs are wrong again. I guess it gets corrupted between 3.13.4 and 3.14. Sorry for the multiple posts. EDIT: @mgallien You guys are welcome to teamviewer request me if you want to see it in action on this computer. Anytime tomorrow is fine by me (swiss time). |
I guess that's #7188. |
Most likely. I wonder how much of an impact #7188 has on this issue, potentially resolving that one will help with this one? They're both tracked in the same issue so let's see. |
I cannot test because I am on Linux and these are windows install.. But please, for the love of god, @mgallien, can you contact whoever is in charge of versioning so that they create a version 3.14.1 based on the latest working 3.13.x, in an emergency, so that I stop getting call from users who have received a broken auto-update... We really don't care about the features of 3.14 for now as it just does not synchronize, which is the main purpose of the Nextcloud client. This solution would give the team time to test and fix the underlying issue... I am sorry to sound so negative, but this is really poor crisis management from the Nextcloud team! After an update, you get hundreds of issue tickets that the client stopped working... instead of continuing to receive new tickets, just revert!!! I have no idea who to talk to about this at Nextcloud, but this is major! EDIT: |
Is 3.14.1 the same as 3.13.4 in terms of this bug? Has everything been reverted to sync properly? |
It is not the same as 3.13.4 but it fixes the problem for me |
this is now solved with the release of 3.14.1 |
thanks to whoever made this happen 🙏 |
So this error doesn't happen again. However, now I am having I made sure the sync tasks were 100% done before updating to the release 3.14.1, and now everything is uploading again. I don't know what you guys changed in 3.14 regarding VFS but something is definitely broken, and those releases need much more testing and reviewing before shipping, especially since I mentioned there were still issues in my comments 3 days ago (a few posts above here on this very issue) and there was NO feedback on my comments. Putting this here as I honestly don't want to revive issue #3912 or #4636 when those errors never happened until 3.14. This is all related. Please reopen. Also link to the debug archive since it's too big for github : https://www.swisstransfer.com/d/c2494e8c-518c-451b-a65e-5847ad10dce4 |
Bug description
We got weird "operation canceled" errors according to the Nextcloud Desktop App.. While I do NOT see these kind of errors on the server side.
Going back to a older version (like desktop client 3.13.3) directly synced, no errors, no issues! And yes using the same server. Meaning we have a regression issue here (especially when there are large amount of files and folders on the server and client, the latest desktop client just fails hard).
Server side Nginx access log (no errors in the error log of Nginx), and even no errors in Nextcloud logs, which actually seems fine:
Also NO related errors in the Nextcloud log either. The errors you do see in the nextcloud app seems to be unrelated I believe.
The same sync errors are happening on both the Deb PPA as well as the AppImage. Meaning it doesn't matter which way you download the latest desktop client, it's not a packaging issue.
Steps to reproduce
Expected behavior
I do not expect regression with regard to the latest desktop client version (3.14.0). While I do not experience any issues by downgrading to 3.13.3 (v3.13.4 should also work).... After I downgraded and I now upgrade again to 3.14.0 and do NOT see the issues anymore..
Which doesn't mean that 3.14.0 is stable, it just means that whatever the error was, 3.13.3 and 3.13.4 could resolve the problem while 3.14.0 could NOT.
Which files are affected by this bug
/Algemeen (directories)
Operating system
Linux
Which version of the operating system you are running.
Linux Mint 21.3
Package
Official Linux AppImage
Nextcloud Server version
30.0.0
Nextcloud Desktop Client version
3.14.0
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
Related tickets: #5356 (it's an old ticket, while now I can pin-point exactly the issue between two desktop client version causing regression).
I'm happy to share the archive debug log, but not in public. I hope you understand.
The text was updated successfully, but these errors were encountered: