Since it has been up to 39 months since the quoted users have submitted a post on this topic, I believe that it is necessary to ask for an update: has anyone experienced any problems as a result of disabling file lock? The admin is making a cautious decision regarding the file lock configuration on an installation with one user on Notes, Calendar, and Deck at a time. Please provide the version numbers in your reply to provide readers a more informed decision.
My site is hosted on Cloudways. This automatically installs the Varnish Cache which turns out not to work with nextcloud. Turning off Varnish in the Cloudways settings resolved this for me.
I am experiencing issues with locked files that I cannot delete or move, but I have a subscription with a provider and thus have no admin access. Is there really no end-user-accessible way to escape from this situation? If so, any chance at getting one added?
Iām having similar problems. First of all, I have to say my head is spinning a bit from looking at these help pages because I am a total novice when it comes to coding and stuff like that. I didnāt think Iād have to know such things when I left Google Drive for NextCloud.
Iām having problems moving folders. I keep getting messages that say ācould not moveā and sometimes ātarget exists.ā
Can someone help me figure this out in simple English?
I have exactly the same problem.
Moreover, when synchronizing a large file, somewhere around 180GB through the Nextcloud client. Error message 423 Locked appears, and after a while everything starts to synchronize all over again. In the log I see the following error "Error PHP Error: fopen (/ var / nextcloud / uploads / 1939388670/00000839): failed to open stream: No such file or directory at / var / www / nextcloud / lib / private / Files / Storage / Local.php # 354 "
What to do with it? in php.ini the maximum time is 10400.
" Empty table oc_file_locks"
Oh ok. Itās nice if you wrote how to do it, because itās not written anywhere ā¦
One problem generates another. Opensource world.
we had the same issue several times already but the solutions described so far cannot be applied: the lock table is empty, so the SQL statements will not work. Disabling filelocking is not a solution for us.
We came up with a different solution which workes just fine:
Log on as with an admin account via ssh
Go to the directory where the file should be, check for any partially uploaded files and delete them
Upload the file via scp and move it to the destination directory
Itās now nearly 6 years later, yet here we are, the bug still persists, this is ridiculous⦠Just give us a gui option for admins to unlock the files