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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nextcloud 3.2.1stable-Win64: Hung on client start #3318
Comments
Might be same issue as #3243? I have similar error log. |
I doubt it, my client completely freezes instead of crashing. |
I have the same error as you and I just posted it there since there's more activity and I thought it may have some connections. Do you have any other cloud storage programs installed on your device? Also does your explorer.exe work when the client freezes? |
I am also having this issue. On initially adding the sync it works as expected, but after a reboot it just sits there burning CPU. I left it for over 24 hours and no progress or further log messages. I have a virtual files sync to the root of my 177gb account, mostly flac files. I am seeing nearly 800 B/sec being written to C:\Windows\System32\LogFiles\Cloudfiles\CldFlt3.etl. Joplin on the desktop/Android is able to sync so the Nextcloud instance itself seems fine.
|
So, when syncing small folders, the client always work fine? Does the issue only happen when syncing at least one large folder? |
What I just noticed: Deleting the file .sync-exclude.lst from the synced directory solves that issue for me. I can restart the Nextcloud client without any issues after removing just that file. Recreating that file and trying to free up the space for that file, causes the same issue again, so I guess despite my experiences above it's just related to this single file. So I guess this could be solved two ways:
OneDrive is installed by default on Win10, but I'm not using it (not logged in), it's not running and as far as I can see there's no directory linked to it.
Yes, the explorer mostly works and I can browse the synced directories, except when the actual files have not been downloaded. Right clicking on a file to get the context menu causes the explorer to hang. Trying to copy a file that has not been downloaded results in:
I think that was a biased observation on my part as I only have a .sync-exclude.lst in my large folder. |
I updated the description in the first post with a workaround that works for me. |
I was having a similar issue with one of my machines where the client was running in virtual drive mode. Machine A - where the .sync-exclude.lst file was created. Sync worked fine, never had any hangs Machine B - would hang when converted to virtual drive. Additionally I wiped the machine with a new reinstall of Windows 10 21H1 and still had the issue. I could not open the client by right-clicking the taskbar item. Additionally, if I attempted to hydrate any of the files (regardless of where they exists, note that the exclude file was not in the root folder, that explorer session would hang until I killed the NextCloud process. When looking at the logs, this is what I found:
After finding this article, I killed the NextCloud process, and removed the exclude.lst from the subfolder. I then restarted NextCloud and everything worked as expected. I have now recreated the exclude file on Machine B and marked it as always online, and it seems as though Machine B is now working properly. Machine A already had that file marked as always online - which is not something I did, but it is where I originally created the ignore files list. Therefore, even with these updates/recreates, Machine A continues to work as expected. |
This was it! This really has to be fixed on next update. |
Thank you for discovering this. We'll see if we can put a fix into a next patch. |
How to use GitHub
Expected behaviour
Nextcloud client starts and syncs files.
Actual behaviour
Nextcloud client reliably hangs on start, not reacting to anything. Icon grey.
Last log entries:
This might be related to virtual files, as I had no issues until I told the client to free up space. On the next restart the client started hanging.
Steps to reproduce
Workaround to fix the issue
Make sure to always have the file .sync-exclude.lst available locally before exiting the Nextcloud client, e.g. by right-clicking on it and selecting "Always keep on this device".
Client configuration
Client version: 3.2.1stable-Win64 (build 20210428) Qt 5.12.9 SSL OpenSSL 1.1.1g 21 Apr 2020
Operating system:
OS language: German
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client: c:\Program Files\Nextcloud
Server configuration
Nextcloud version:
Storage backend (external storage):
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Since 3.1: Under the "General" settings, you can click on "Create Debug Archive ..." to pick the location of where the desktop client will export the logs and the database to a zip file.
On previous releases: Via the command line:
nextcloud --logdebug --logwindow
ornextcloud --logdebug --logfile log.txt
(See also https://docs.nextcloud.com/desktop/3.0/troubleshooting.html#log-files)
Web server error log:
I don't have access to those.
Server logfile: nextcloud log (data/nextcloud.log):
The text was updated successfully, but these errors were encountered: