langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Uploaded data status keep queuing #4518

New Issue
Closed
opened 2026-02-21 18:06:50 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 18:06:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @vekrumk on GitHub (Jul 9, 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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.13

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Upload documents in knowledge, they do not get processed just keep queuing.
image

✔️ Expected Behavior

Expected file to process.

❌ Actual Behavior

Keeps queuing and never processes. This issue was closed last year year as Issue #696 but is happening again.

Originally created by @vekrumk on GitHub (Jul 9, 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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.13 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Upload documents in knowledge, they do not get processed just keep queuing. ![image](https://github.com/langgenius/dify/assets/13925050/3abe1297-874c-4b12-8ef8-9d725bba509f) ### ✔️ Expected Behavior Expected file to process. ### ❌ Actual Behavior Keeps queuing and never processes. This issue was closed last year year as Issue #696 but is happening again.
yindo added the 🐞 bug label 2026-02-21 18:06:50 -05:00
yindo closed this issue 2026-02-21 18:06:50 -05:00
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 9, 2024):

Please provide the containers' logs if you are using docker.

@crazywoola commented on GitHub (Jul 9, 2024): Please provide the containers' logs if you are using docker.
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@vekrumk commented on GitHub (Jul 9, 2024):

Yes using Docker. Logs for which container?

@vekrumk commented on GitHub (Jul 9, 2024): Yes using Docker. Logs for which container?
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 9, 2024):

In this case you should check api and worker.

@crazywoola commented on GitHub (Jul 9, 2024): In this case you should check api and worker.
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@vekrumk commented on GitHub (Jul 9, 2024):

For Weaviate:
docker logs 1254bd8e9b33
{"action":"startup","default_vectorizer_module":"none","level":"info","msg":"the default vectorizer modules is set to "none", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2024-07-09T14:33:33Z"}
{"action":"startup","auto_schema_enabled":true,"level":"info","msg":"auto schema enabled setting is set to "true"","time":"2024-07-09T14:33:33Z"}
{"action":"grpc_startup","level":"info","msg":"grpc server listening at [::]:50051","time":"2024-07-09T14:33:33Z"}
{"action":"restapi_management","level":"info","msg":"Serving weaviate at http://[::]:8080","time":"2024-07-09T14:33:33Z"}

@vekrumk commented on GitHub (Jul 9, 2024): For Weaviate: docker logs 1254bd8e9b33 {"action":"startup","default_vectorizer_module":"none","level":"info","msg":"the default vectorizer modules is set to \"none\", as a result all new schema classes without an explicit vectorizer setting, will use this vectorizer","time":"2024-07-09T14:33:33Z"} {"action":"startup","auto_schema_enabled":true,"level":"info","msg":"auto schema enabled setting is set to \"true\"","time":"2024-07-09T14:33:33Z"} {"action":"grpc_startup","level":"info","msg":"grpc server listening at [::]:50051","time":"2024-07-09T14:33:33Z"} {"action":"restapi_management","level":"info","msg":"Serving weaviate at http://[::]:8080","time":"2024-07-09T14:33:33Z"}
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@vekrumk commented on GitHub (Jul 9, 2024):

Does the default_vectorizer_module need to be set to something other than none? None is the default setting int he .env.
image

@vekrumk commented on GitHub (Jul 9, 2024): Does the default_vectorizer_module need to be set to something other than none? None is the default setting int he .env. ![image](https://github.com/langgenius/dify/assets/13925050/984f4bad-ead5-403f-9112-c3b9a1ffab74)
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 9, 2024):

I mean the logs of api and worker not the vector db.

Does the default_vectorizer_module need to be set to something other than none? None is the default setting int he .env.

If you choose to use weaviate, you can leave all those variables untouched. They have already configured as a template.

@crazywoola commented on GitHub (Jul 9, 2024): I mean the logs of api and worker not the vector db. > Does the default_vectorizer_module need to be set to something other than none? None is the default setting int he .env. If you choose to use weaviate, you can leave all those variables untouched. They have already configured as a template.
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@vekrumk commented on GitHub (Jul 9, 2024):

Looks like it was a wrong Redis password in the Celery config in the .env file. The logs said it was not able to connect to Redis and started working now. But it doesn't process the old queued docs, should I delete them and re-upload?

@vekrumk commented on GitHub (Jul 9, 2024): Looks like it was a wrong Redis password in the Celery config in the .env file. The logs said it was not able to connect to Redis and started working now. But it doesn't process the old queued docs, should I delete them and re-upload?
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@vekrumk commented on GitHub (Jul 9, 2024):

BTW, what is the limit on how many documents in a knowledge store?

@vekrumk commented on GitHub (Jul 9, 2024): BTW, what is the limit on how many documents in a knowledge store?
yindo commented 2026-02-21 18:06:51 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 9, 2024):

Looks like it was a wrong Redis password in the Celery config in the .env file. The logs said it was not able to connect to Redis and started working now. But it doesn't process the old queued docs, should I delete them and re-upload?

Yes

BTW, what is the limit on how many documents in a knowledge store?

It depends on your computer. We don't have a limitations of how many documents can be uploaded in CE version.

@crazywoola commented on GitHub (Jul 9, 2024): > Looks like it was a wrong Redis password in the Celery config in the .env file. The logs said it was not able to connect to Redis and started working now. But it doesn't process the old queued docs, should I delete them and re-upload? Yes > BTW, what is the limit on how many documents in a knowledge store? It depends on your computer. We don't have a limitations of how many documents can be uploaded in CE version.
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
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#4518
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?