This error/bug has been driving me crazy. Because there was so much variety in the user posts, I created a more standardized testing environment and replicated the bug with a standardized dataset on clean new installs using both postgres & mysql. In the process I created a one-run install script that requires minimal configuration/expertise to use. Doing the file/redis maintenance options are not actually solutions if the bug is evident on clean installs (they merely temporize the issue). Any recommendations on where to look (e.g. in nextcloud codebase) to get this bug fixed would be appreciated!
I want to see nextcloud succeed, and for it to do so this issue needs fixing!
That part for me didn’t work. I closed my nextcloud docker to avoid any changes. Then manually deleted the files I needed and yes. The container changed the permissions for the files creating that situation. After I moved everything manually then the problem disappeared of course.
I was wondering why so many people have this issue. it seems the only time I need to perform this is when I’m doing a files:scan and the terminal session gets dumped for some reason. out side of that I’ve never had a locked file.
Would like to know the risks of disabling the file lock?
One of the contributors to this topic, @mwallace, mentioned that he “turned off file locking on [his installation hosted on] a shared server.” To help those who have considered or have tried on this option, how should someone in similar circumstances monitor the installation for unintended effects?
Hi all! I still experience the same issue. Tried to use solution proposed above with keys deleting in redis, however did not work. Problem occured, when I changed one of scss files to add an extra icon.
My version now is 18.0.9
I tried with enabled and sisabled file.locking in config file.
It seem to be no files within files_locks table where value of ‘lock’ was different than 0. WHen table empty also did not work. Still was given a log message that file is locked for SCSS cacher.
Restarting redis and apache was useless as well.
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.