langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

knowledge base : Cannot release a lock that's no longer owned #6869

New Issue
Closed
opened 2026-02-21 18:17:45 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:17:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @IceNiro on GitHub (Nov 21, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

I'm trying to upload a txt file to build a knowledge base, but it's giving me the error: cannot release a lock that's no longer owned。
but it seems that the document is still worked,the segment status is available。
and I cannot find any error log message in the work server log file

image

✔️ Expected Behavior

what is the reason for this error ?
how can I fix the document status to green ?

❌ Actual Behavior

No response

Originally created by @IceNiro on GitHub (Nov 21, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.10.1 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce I'm trying to upload a txt file to build a knowledge base, but it's giving me the error: cannot release a lock that's no longer owned。 but it seems that the document is still worked,the segment status is available。 and I cannot find any error log message in the work server log file <img width="1552" alt="image" src="https://github.com/user-attachments/assets/ced38fcc-77b5-4b87-821d-9bd70c176cb6"> ### ✔️ Expected Behavior what is the reason for this error ? how can I fix the document status to green ? ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:17:45 -05:00
yindo closed this issue 2026-02-21 18:17:45 -05:00
yindo commented 2026-02-21 18:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 21, 2024):

Hey @IceNiro! I'm here to help you with bug fixes, answer your questions, and guide you on becoming a contributor. Let's tackle this issue together and get it resolved!

I found a similar discussion titled "bug：cannot release a lock that's no longer owned" in the Dify repository, but it remains unsolved [1]. Unfortunately, there isn't a specific solution provided for this error in the available data.

For troubleshooting, you might want to try the following general steps:

  1. Retry the Operation: Sometimes, transient issues can cause such errors. Retrying the upload might resolve the problem.

  2. Check for Updates: Ensure that you are using the latest version of Dify, as updates may contain bug fixes for known issues.

  3. Review Configuration: Double-check your configuration settings related to lock management and document processing to ensure they are correctly set.

  4. Consult Documentation: Review the Dify documentation for any notes on lock management or related settings that might affect your setup.

If these steps do not resolve the issue, you might need to wait for further updates from the Dify team or community discussions that address this specific error.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 21, 2024): <!-- Greeting --> Hey @IceNiro! I'm here to help you with bug fixes, answer your questions, and guide you on becoming a contributor. Let's tackle this issue together and get it resolved! <!-- Answer --> I found a similar discussion titled "bug：cannot release a lock that's no longer owned" in the Dify repository, but it remains unsolved <sup>[[1]](https://github.com/langgenius/dify/discussions/3582)</sup>. Unfortunately, there isn't a specific solution provided for this error in the available data. For troubleshooting, you might want to try the following general steps: 1. **Retry the Operation**: Sometimes, transient issues can cause such errors. Retrying the upload might resolve the problem. 2. **Check for Updates**: Ensure that you are using the latest version of Dify, as updates may contain bug fixes for known issues. 3. **Review Configuration**: Double-check your configuration settings related to lock management and document processing to ensure they are correctly set. 4. **Consult Documentation**: Review the Dify documentation for any notes on lock management or related settings that might affect your setup. If these steps do not resolve the issue, you might need to wait for further updates from the Dify team or community discussions that address this specific error. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 21, 2024):

This has been resolved in later versions, please upgrade to latest version.

@crazywoola commented on GitHub (Nov 21, 2024): This has been resolved in later versions, please upgrade to latest version.
yindo commented 2026-02-21 18:17:45 -05:00
Author
Owner
Copy Link
Copy Source

@berg-wang commented on GitHub (Jan 2, 2025):

This has been resolved in later versions, please upgrade to latest version.

I have met the same problem in version 0.12.1
image
I found the log in console:
raise LockError("Cannot release a lock that's no longer owned")
redis.exceptions.LockError: Cannot release a lock that's no longer owned
how to solve this problem?

@berg-wang commented on GitHub (Jan 2, 2025): > This has been resolved in later versions, please upgrade to latest version. I have met the same problem in version 0.12.1 ![image](https://github.com/user-attachments/assets/862573be-b255-4679-931c-a85fbc83be9c) I found the log in console: raise LockError("Cannot release a lock that's no longer owned") redis.exceptions.LockError: Cannot release a lock that's no longer owned how to solve this problem?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug 🤔 cant-reproduce
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6869
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?