" to pick the location of where the desktop client will export the logs and the database to a zip file. Since 3.1: Under the "General" settings, you can click on "Create Debug Archive.
Manictime exclude files from folder how to#
Please advice how to find and extract and
Manictime exclude files from folder archive#
I have debug archive and Nextcloud_sync.log from the problematic period, but I'm not willing to upload complete file due to privacy reasons (debug archives are up to 25MB file with extracted log of 300MB). Storage backend (external storage): mysql Logs Nextcloud version: 21.0.2 (docker/apache) Installation path of client: Server configuration Client configurationĬlient version: Version 3.2.2stable-Win64 (build 20210527) After this happened 2 times I switched the specific folders to "Always available locally" and the client successfully downloaded all the files. removed files didn't reside in this huge folder but on the other one InstantUpload and 2-3 others (completely random in my eyes). The file was initially removed by the client and I recovered it from server trashbin. The client feels totally overloaded - click on settings or properties of every folder results in minutes of unresponsive UI and client using lot of CPU Maybe this is related: short time before I added huge folder with my photo archive (600GB,>50k files) but from my feeling it was synced successfully (with VFS) but might introduced some performance issues problems with the client. I have no clue how to find out if some process or service crashed - eventlogs don't say anything After client restart I can access placeholder files again.
Fortunately this happened to few hundreds of files and I could recover the files from server trashbin.īut the problem still existed and the client complained it could not create placeholder file, and removed the files again!Īt the same time access to existing placeholder files (with blue cloud icon) was not possible - the error was "0x8007016A The cloud file provider is not running." The error is often reported for OneDrive - and computer restart is recommended as solution. as a result a client folder had no files anymore and subsequent sync removed all the files on the server side. I have no idea why it even tried to create placeholder files - majority of affected files existed and successfully synced months before (at least client reported successful sync). #=#=#=#=# Propagation starts (last step: 368 msec, total: 368 msec)
0 kommentar(er)
