Hello all
Could someone give me some hints/ideas how to troubleshoot the following issue on Winsows 10 desktop client 3.1.1? After upgrading from 2.6.5 to 3.1.1 the following error message is displayed after the start of the desktop client: " Changes in synchronized folders could not be tracked reliably" (in German: āĆnderungen in synchronisierten Ordnern konnten nicht zuverlƤssig nachverfolgt werdenā)
Iāve configured 3 folder synchronisations on the client what used to work very stable in the past. Now, after the upgrade, just one of it seems to have this issue. When I add a file to a synchronized folder itās almost synched immediately to the server on two of those sync targets. But on one of those 3 it doesnāt work.
I havenāt tested in both directions and I didnāt wait for a long time yet.
Iāve deleted the faulty folder synchronisation on the desktop client and added it again. No success. I de- and reinstalled the desktop client (just in the Windows control panel, didnāt remove some files manually). The error still appears.
Because it was working before, it looks a bit like a regression which means this is a good candidate for a bug report. Logfiles are interesting, if you find any difference in the folders, I donāt know perhaps different file system on the client, or data from external storage. Or is it always the third one, try to add a forth one and a different as third one.
Iād take a look at the bug tracker: Issues Ā· nextcloud/desktop Ā· GitHub, regressions easily qualify for a bug report. Just make sure that there isnāt already a topic. Ideally you find a way and procedure to easily reproduce this problem. It can also help if others with similar problems share their configuration.
OK, here are the results of my additional testing and some more information:
Removed the folder that is not synched automatically and added a new folder (completely new partnership). The message still appeared after restart of the desktop client but it was one of the other folders that isnāt synchronized then. Then I added the one again that I removed and it can synch now. So the folder or its contents is obviously not the problem.
Synched the folder to another PC and that worked too.
Activated the log with F12 and canāt see something special (like an error). The log is really big and Iām a bit lost because I donāt know what to look for.
2-Way synch for all other folders are working fine
Within the folder that doesnāt synchronize Iāve added a testfile. All other files have the green tick but the new one hasnāt. So obviously it isnāt recognized by the sync clientā¦
Copied the contents of the unsynchronizable folder to another place on the same HDD, then deleted the synch partnership and added it for the new folder where the contents are copied to. Still the same problemā¦
Not yet. I havenāt spent more time on it. But Iāll contact the user soon to do a check directly on her computer, because she told me that she thinks everything is synchronized and fine so far. (probably with a delay?)
And meanwhile weāve upgraded to NC Server version 19.x, so the whole environment has changed.
In any case Iāll post an update here. That issue is just not the highest prio for me, thatās why it takes longer
@mschwizer, I was and am on Nextcloud 20.0.6 and the error message is not there anymore when I start my computer. No clue what it was, but it is gone. I have never seen files that where not synced. All folders give nice green checks. So hopefully for your user this also disappears after a while.
Hi!
I have this too.
I am on Client Version 3.1.3 (Windows).
All my local data is on an external hard disk
Nextcloud is a Core appliance instalation on my RPi Nextcloud box (data also on external disk)
When in dual boot Manjaro I dont have it
I also cant quite read all the info on the toast notification in windows - could you tell me the whole message, please?
Everything seems to be working well tho, AFAICS
After a long while Iāve checked the situation again. The folders are basically synched but the error message is still appearing. As I can see the files are not synched in āreal timeā so probably only after user log-on/-off or system boot.
Iām having the same issue, on exactly one out of three windows systems.
The system in question is pretty much a cripple (AMD A9 with 8gig ram), the other two are much fasterā¦ so could this possibly a performance thing? The message appears only on the first login after boot for me.
