Open taowang1993 opened 5 days ago
The errors you're encountering seem to be related to the initialization and state management of components in the Dify platform, particularly with Milvus components like rootcoord
and querycoord
, as well as MinIO storage.
RootCoord and QueryCoord Errors: The messages "find no available rootcoord, check rootcoord state" and "find no available querycoord, check querycoord state" suggest that these components are not starting up correctly. This could be due to configuration issues, network problems, or resource constraints. Ensure that all necessary services are running and properly configured in your Docker setup. Check the logs for any additional error messages that might provide more context.
MinIO Bucket Error: The error "Your previous request to create the named bucket succeeded and you already own it" indicates that the MinIO bucket already exists. This is generally a warning rather than a critical error. You can verify the bucket's existence and permissions to ensure that the application can access it correctly.
Configuration Check: Double-check your .env
file and Docker Compose configuration to ensure that all environment variables and service dependencies are correctly set up. The VECTOR_STORE=milvus
setting indicates that Milvus is being used as the vector database, so ensure that Milvus is correctly configured and running [1].
Etcd Connectivity: The logs show multiple attempts to connect to etcd, which are successful. However, ensure that etcd is fully operational and accessible by all components.
Resource Allocation: Ensure that your Docker environment has sufficient resources (CPU, memory) allocated to handle the services you're running, as resource constraints can lead to initialization failures.
If these steps do not resolve the issue, consider checking for any updates or patches for the Dify platform or Milvus that might address these startup issues.
To continue talking to Dosu, mention @dosu.
After investigation, I discovered that these errors are caused by code changes after 0.11.2.
There must be a bug in recent commits or pull requests.
Maybe it's related to python version. We are now supporting 3.12 in our code repo, maybe you can try to install the deps again with 3.12.
Self Checks
Dify version
0.11.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
When I run
docker compose up -d
, I ran into the following errors:Steps to Reproduce
git clone https://github.com/langgenius/dify.git cd dify/docker cp .env.example .env set VECTOR_STORE=milvus docker compose up -d
logs
✔️ Expected Behavior
No response
❌ Actual Behavior
No response