Skip to content
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

[Bug]: RPC error: [__internal_register], <MilvusException: (code=1, message=Incorrect port or sdk is incompatible with server, please check your port or downgrade your sdk or upgrade your server)> #38255

Open
1 task done
meseguera opened this issue Dec 5, 2024 · 3 comments
Assignees
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@meseguera
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

root@vpshost:~/milvus_compose# python3 ./hello_milvus.py

=== start connecting to Milvus ===

RPC error: [__internal_register], <MilvusException: (code=1, message=Incorrect port or sdk is incompatible with server, please check your port or downgrade your sdk or upgrade your server)>, <Time:{'RPC start': '2024-12-05 18:10:05.874863', 'RPC error': '2024-12-05 18:10:05.876054'}>
Traceback (most recent call last):
File "/root/milvus_compose/./hello_milvus.py", line 32, in
connections.connect("default", host="localhost", port="19530")
File "/usr/local/lib/python3.10/dist-packages/pymilvus/orm/connections.py", line 451, in connect
connect_milvus(**kwargs, user=user, password=password, token=token, db_name=db_name)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/orm/connections.py", line 402, in connect_milvus
gh._wait_for_channel_ready(timeout=timeout)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/client/grpc_handler.py", line 157, in _wait_for_channel_ready
raise e from e
File "/usr/local/lib/python3.10/dist-packages/pymilvus/client/grpc_handler.py", line 150, in _wait_for_channel_ready
self._setup_identifier_interceptor(self._user, timeout=timeout)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/client/grpc_handler.py", line 268, in _setup_identifier_interceptor
self._identifier = self.__internal_register(user, host, timeout=timeout)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/decorators.py", line 141, in handler
raise e from e
File "/usr/local/lib/python3.10/dist-packages/pymilvus/decorators.py", line 137, in handler
return func(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/decorators.py", line 176, in handler
return func(self, *args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/decorators.py", line 116, in handler
raise e from e
File "/usr/local/lib/python3.10/dist-packages/pymilvus/decorators.py", line 86, in handler
return func(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/pymilvus/decorators.py", line 213, in handler
raise MilvusException(message=msg) from e
pymilvus.exceptions.MilvusException: <MilvusException: (code=1, message=Incorrect port or sdk is incompatible with server, please check your port or downgrade your sdk or upgrade your server)>

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@meseguera meseguera added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 5, 2024
@meseguera
Copy link
Author

  • Milvus version: Milvus cli version: 0.3.2
    Pymilvus version: 2.2.1

  • Deployment mode(standalone or cluster): standalone

  • MQ type(rocksmq, pulsar or kafka):

  • SDK version(e.g. pymilvus v2.0.0rc2):

  • OS(Ubuntu or CentOS): Ubuntu 22.04 server

  • CPU/Memory: 8gb

  • GPU: na

  • Others:

@yanliang567
Copy link
Contributor

which milvus version are you running?
/assign @meseguera
/unassign

@sre-ci-robot sre-ci-robot assigned meseguera and unassigned yanliang567 Dec 5, 2024
@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 5, 2024
@XuanYang-cn
Copy link
Contributor

This error msg is released last week at PyMilvus==2.4.10, @meseguera Please double check your pymilvus also

milvus-io/pymilvus#2378

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants