Closed IceNiro closed 1 day ago
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:
Retry the Operation: Sometimes, transient issues can cause such errors. Retrying the upload might resolve the problem.
Check for Updates: Ensure that you are using the latest version of Dify, as updates may contain bug fixes for known issues.
Review Configuration: Double-check your configuration settings related to lock management and document processing to ensure they are correctly set.
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.
This has been resolved in later versions, please upgrade to latest version.
Self Checks
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
✔️ Expected Behavior
what is the reason for this error ? how can I fix the document status to green ?
❌ Actual Behavior
No response