-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
https://docs.dify.ai/getting-started/install-self-hosted/local-source-code #6157
Comments
Hey @yanguangcang2019! I'm here to help you with your Dify issue. I'm a bot that can assist you with bug fixes, answer questions, and guide you on how to become a contributor. Let's tackle this issue together! To address the issue where the progress of your file upload to the knowledge base remains at 0 when running Dify using Docker, you need to ensure that the Celery worker service is running correctly. Here are the steps to verify and start the worker service:
By following these steps, you should be able to determine if the worker service is running and diagnose any issues that might be causing the file upload progress to remain at 0 [1][2][3][4]. |
all is right,but why? |
embeding model in xinference is running,and it is setted right in dify,can you help me? |
Please do not modify the template. |
Yes you do not need to run that command. And please use the right markdown syntax to format code and tracing logs. And you need to provide the logs of the worker container. Not |
(diy_env) root@cuda22: |
Are these logs of the worker container?thanks |
Who can help me? |
I run Dify in docker,not local-source-code,I am also encountering the same issue where the progress of my file upload to the knowledge base is always at 0. I've been waiting for a long time, but the progress number has disappeared, and the "Next Step" button is ineffective. What could be the reason? I am using the Docker method to start, and I don't need to execute the command celery -A app.celery worker -P gevent -c 1 --loglevel INFO -Q dataset,generation,mail,ops_trace, right?
pls check your worker service is started or not @dwq370
Originally posted by @JohnJyong in #4295 (comment)
The text was updated successfully, but these errors were encountered: