Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Locks Not Clearing in File Explorer Despite being unlocked in Web UI #6998

Open
janm-at opened this issue Jul 22, 2024 · 1 comment
Open

Comments

@janm-at
Copy link

janm-at commented Jul 22, 2024

The outdated lock is removed (you can see this in the WebUI), but the desktop client is only refreshing the lock status when the locked file is closed - even if it was unlocked while open.


Description:
We've observed that file locks are not clearing properly in File Explorer. While the Web UI shows the file as unlocked (due to the lock_timeout setting), the file remains locked in File Explorer for both the user who opened it and other users. Our setup is running in Docker containers.

Steps to Reproduce:

Set the lock_timeout with the OCC command (I set it to 2 minutes for testing)
User1 opens a file (e.g., Test.docx) in File Explorer.
Wait for the lock timeout.
Check the lock status in the Web UI for User1 and User2 (file appears unlocked).
Check the lock status in File Explorer for User1 and User2 (file still shows as locked).
Lock status in File Explorer only gets cleared once the file is closed.

Current Workarounds Tried:

Removed and re-enabled lock_timeout setting.
Tried the cleanup_oc_files_lock py script by rakurtz (https://github.com/rakurtz/cleanup_oc_files_lock). They have the same effect, the file is unlocked in web UI while still showing unlocked in File Explorer
Ensured all systems and apps are up to date.

Expected Behavior:
Files should unlock in the database, reflecting the status shown in the Web UI. The file lock status should also get synced in the Nextcloud Client and the client updates the status in File Explorer.

It seems like there is another table in the database that the Nextcloud client reads for File locks?

Client Details:

Nextcloud Version: 29.0.3
Temporary Files Lock App Version: 29.0.1
Operating System: Windows 11
Web Browser: Chrome
Desktop Client Version: 3.13.2
Redis Version: 7.2.5

Server Details:

Operating System: Alpine Linux v3.20
Web Server: Apache 2.4.61
Database: PostgreSQL 16.3

Any guidance or steps to resolve this would be greatly appreciated. Thanks!

@susnux susnux transferred this issue from nextcloud/files_lock Aug 13, 2024
@Rello Rello removed the stable-3.13 label Dec 9, 2024
@nikobe123
Copy link

We have the same problem, makes the team frustrated because they cannot access files and need IT support to release locks that are stuck days and weeks

Client Details:

NC 28.0.12
Temporary Files Lock App Version: 28.0.7
Operating System: Mac
Web Browser: Firefox
Desktop Client Version: 3.15.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants