File is locked - how to unlock

[icho40]

I had to set up a new nextcloud and had the same error.

I don’t use redis but memcached.
I commented out the entry for memcached in
/var/www/nextcloud/config/config.php:

#‘memcache.local’ => ‘\OC\Memcache\APCu’,

Now the sync works properly

[jonathanmmm]

solved the issue for me, thanks.

1. sudo -u www-data php occ maintenance:mode --on
   (in Nextcloud folder)
2. sudo redis-cli -s /var/run/redis/redis.sock
3. flushall (OK was response)
4. exit
5. sudo -u www-data php occ maintenance:mode --off
   (in Nextcloud folder)
6. sudo -u www-data php occ files:scan --all
   (in Nextcloud folder)

But there was no password in redis? Is this right?

[ryu]

Thanks for pedropt laying this out so clearly. Fixed me up good!

[Blanka_Cao]

It works for me, thanks a lot!

[tjwmagic1]

Just had to do this for a folder on my install. Thanks, tflidd!

[Ady_Suryadi]

@castillo92

‘filelocking.enabled’ => false,

add ‘filelocking.enabled’ => false, in config/config.php:
thanks

[isuru]

Thanks. This was helpful.

[johnnycloud]

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.

[vin100vin]

It’s too difficult for me to do it by terminal.
Could someone tell me what I have to delete by phpMyAdmin

Delete everithing?

[tflidd]

On the overview of the tables, you normally have a button to empty (‘vider’) a table. You need to keep the table and its structure as it is.

[vin100vin]

@tflidd Thanks !
I put the image for the next neebee (as me)

[rhua]

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?

[Mati]

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.

[anon57501651]

Why do you suggest to update the cache with occ files:scan --all and then clean the cache immediately with occ files:cleanup? I do not understand your logic.

Maybe we need to clean the cache at first and to fill it after?

[rhua]

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.

@mwallace

'filelocking.enabled' => false,

@castillo92

Shared hosting (others who can’t install redis): You can disable the file locking, edit your configuration file config/config.php:

‘filelocking.enabled’ => false,

However, disabling is not a good solution. You can run into problems when several processes try to write to a file (especially online editors in the web-interface). In single-user and single-client environments, it’s probably less of a problem.

@webunraveling

If I remember right, that error is caused by a locked file. Take a look at the following URL, under " Manually disable locking state ".
[from Error when deleting file or folder - #2 by webunraveling]

[imit_L]

Is it written like this? ?
‘Filelocking.enabled’ => false
After I add it, my php can’t be used directly

[francois-ferrandis]

Hello all! I have a question.

The usual solution given to wipe stale locks is the following:

1. DELETE all the rows from oc_file_locks
2. Run occ files:scan --all

I am thus wondering why it would not be reasonable to set lock to 0 on all non-zero rows, like this :

UPDATE `oc_file_locks` 
SET `oc_file_locks`.`lock` = 0
WHERE `oc_file_locks`.`lock` != 0;

Would that be asking for trouble? (given maintenance mode is enabled, of course)

[rhua]

Nextcloud 19.0.1 Problem with deleting files/folders

I first tried following the next instruction: Which at step one resulted in mayor errors and the process being killed: Starting scan for user 1 out of 3 (Some_user_without_groupfolder_access) Starting scan for user 2 out of 3 (Some_user_with_Groupfolder_access) Exception during scan: An exception occurred while executing 'SELECT `fileid` FROM `oc_filecache` WHERE (`storage` = ?) AND (`path_hash` = ?)' with params [1, "1e6013faa7e8570d55f5164261dc1b4d"]: SQLSTATE[HY000]: General error: 2…

[vatolin]

@tflidd

DELETE FROM oc_file_locks WHERE 1

If

DELETE FROM oc_file_locks WHERE 1

results in:

ERROR: argument of WHERE must be type boolean, not type integer LINE 1: DELETE FROM oc_file_locks WHERE 1

modify the command:

DELETE FROM oc_file_locks WHERE true