-
Notifications
You must be signed in to change notification settings - Fork 34
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
can't invoke by server.start() #185
Comments
it seems some service can't start normally. log is : |
which milvus lite are u using? |
I'm using v2.2.16-lite |
Hi @Austin-Phoenix, the older version of Milvus Lite <2.4.x is no longer actively maintained. Looks like you are using v2.2.16-lite in Windows. The older version is known to have issues like crashing after restarting, due to stability issues. We encourage you to use the latest version of Milvus Lite, which can run on Windows through WSL (https://learn.microsoft.com/en-us/windows/wsl/install). Native windows support is also coming soon, tracked by #176. Alternatively, you can use the Milvus Standalone mode on Docker, following https://milvus.io/docs/install_standalone-docker.md, which also supports Windows. |
thanks codingjaguar,i'll try docker for 2.4x milvus version. |
Dear all,
I already used latest milvus by windows docker desktop.
It seems my docker desktop runs normally.
Message ID: ***@***.***>
i wand to download latest new milvus, but download failed by following logs:
PS D:\Ubuntu_WSL\Milvus> docker compose up -d
time="2024-07-16T17:56:19+08:00" level=warning msg="D:\\Ubuntu_WSL\\Milvus\\docker-compose.yml: `version` is obsolete"
[+] Running 0/16
- minio [⠀⠀⠀⠀⠀⠀] Pulling 146.2s
- c7e856e03741 Retrying in 1 second 112.8s
- c1ff217ec952 Retrying in 1 second 112.8s
- b12cc8972a67 Retrying in 1 second 112.8s
- 4324e307ea00 Waiting 112.8s
- 152089595ebc Waiting 112.8s
- 05f217fb8612 Waiting 112.8s
- standalone [⠀⠀⠀⠀⠀⠀⠀⠀] Pulling 146.2s
- d5fd17ec1767 Waiting 112.8s
- ca3a09d8ea0c Waiting 112.8s
- 838ea2fc0c5a Waiting 112.8s
- 25e4b36fd223 Waiting 112.8s
- 5e94f6dcda58 Waiting 112.8s
- 1f27396f6efc Waiting 112.8s
- fe556ec02776 Waiting 112.8s
- 4f4fb700ef54 Waiting 112.8s
error pulling image configuration: download failed after attempts=6: dialing production.cloudflare.docker.com:443 container via direct connection because static system has no HTTPS proxy: connecting to 128.242.240.85:443: dial tcp 128.242.240.85:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Could you please tell me how to resolve this problem?
just configure in docker by this one? i have no idea....... thanks very much.
|
highly recommend to run milvus on a docker but don't use WSL. we don't have any experience and test on windows system |
but the root cause is minio and standardalone can't using docker pull successfully.
only etcd can docker pull successfully.
also i download
but it doesn't work.
using
docker pull mbackes/milvus-lite
docker run -d --name milvus -p 3000:80 milvusdb/milvus
so can you tell me if using docker run , how does paramters will be filled? or in 2.4.5 how can i download minio and standardalone component?
can't docker pull with me. only etcd is fine for me
Thanks
…------------------ 原始邮件 ------------------
发件人: "milvus-io/milvus-lite" ***@***.***>;
发送时间: 2024年7月16日(星期二) 晚上6:58
***@***.***>;
***@***.***>;"State ***@***.***>;
主题: Re: [milvus-io/milvus-lite] can't invoke by server.start() (Issue #185)
- c7e856e03741 Retrying in 1 second
highly recommend to run milvus on a docker but don't use WSL. we don't have any experience and test on windows system
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
debug log as below:
[2024/07/02 17:14:46.181 +08:00] [WARN] [retry/retry.go:39] ["start to reset connection because of specific reasons"] [module=Proxy] [client_role=rootcoord] [error="rpc error: code = Unknown desc = expected=%!s(int64=112), actual=%!s(int64=119): server ID mismatch"]
[2024/07/02 17:14:50.186 +08:00] [WARN] [retry/retry.go:39] ["start to reset connection because of specific reasons"] [module=Proxy] [client_role=rootcoord] [error="rpc error: code = Unknown desc = expected=%!s(int64=112), actual=%!s(int64=119): server ID mismatch"]
[2024/07/02 17:14:58.194 +08:00] [WARN] [retry/retry.go:39] ["start to reset connection because of specific reasons"] [module=Proxy] [client_role=rootcoord] [error="rpc error: code = Unknown desc = expected=%!s(int64=112), actual=%!s(int64=119): server ID mismatch"]
[2024/07/02 17:14:58.195 +08:00] [WARN] [grpcclient/client.go:287] ["retry func failed"] [module=Proxy] ["retry time"=4] [error="rpc error: code = Unknown desc = expected=%!s(int64=112), actual=%!s(int64=119): server ID mismatch"]
[2024/07/02 17:15:08.404 +08:00] [WARN] [retry/retry.go:39] ["start to reset connection because of specific reasons"] [module=Proxy] [client_role=rootcoord] [error="rpc error: code = Unknown desc = expected=%!s(int64=112), actual=%!s(int64=119): server ID mismatch"]
[2024/07/02 17:15:09.425 +08:00] [WARN] [grpcclient/client.go:367] ["fail to get grpc client"] [module=Proxy] [client_role=indexcoord] [error="find no available indexcoord, check indexcoord state"]
[2024/07/02 17:15:09.425 +08:00] [WARN] [retry/retry.go:39] ["grpc client is nil, maybe fail to get client in the retry state"] [module=Proxy] [client_role=indexcoord]
[2024/07/02 17:15:09.425 +08:00] [WARN] [grpcclient/client.go:291] ["fail to get grpc client in the retry state"] [module=Proxy] [client_role=indexcoord] [error="find no available indexcoord, check indexcoord state"]
[2024/07/02 17:15:10.429 +08:00] [WARN] [retry/retry.go:39] ["grpc client is nil, maybe fail to get client in the retry state"] [module=Proxy] [client_role=indexcoord]
The text was updated successfully, but these errors were encountered: