qingqingdaxia opened a new issue, #1046: URL: https://github.com/apache/rocketmq-clients/issues/1046
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq-clients/issues) and [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Programming Language of the Client Python ### Runtime Platform Environment mac=15.5 (24F74) python = 3.10 rocketmq-python-client=5.0.6 ### RocketMQ Version of the Client/Server server：rocketmq-all-5.0.0-bin-release client：rocketmq-python-client>=5.0.6 ### Run or Compiler Version _No response_ ### Describe the Bug 自定义集成producer的时候报错 grpc.aio._call.AioRpcError: <AioRpcError of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "failed to connect to all addresses; last error: UNAVAILABLE: ipv4:192.168.7.166:9876: Socket closed" debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"failed to connect to all addresses; last error: UNAVAILABLE: ipv4:192.168.7.166:9876: Socket closed", grpc_status:14}" ### Steps to Reproduce 然后我直接用example的代码跑一下，只是修改了endpoints，还是报相同的错误 https://github.com/apache/rocketmq-clients/blob/master/python/example/normal_producer_example.py <img width="798" height="669" alt="Image" src="https://github.com/user-attachments/assets/fe4e3351-f500-4d55-b9f1-757515af0155"; /> ### What Did You Expect to See? 请教一下，这里的endpoints填写方式不对吗？ ### What Did You See Instead? 或者是不是服务端部署的时候需要修改什么配置？ 麻烦了，谢谢 ### Additional Context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
