[grpc-io] Re: grpc.channel_ready_future throw inactive rpc error

2023-05-10 Thread Christian Reiser
I had the wrong server IP. Thanks Richard On Wednesday, May 10, 2023 at 9:09:42 PM UTC+2 Christian Reiser wrote: > Hi, did you solve this error? I am having the same one. > > > ~/.local/lib/python3.7/site-packages/grpc/_channel.py in __call__(self, > request, timeout, metadata, credentials, wai

[grpc-io] Re: grpc.channel_ready_future throw inactive rpc error

2023-05-10 Thread Christian Reiser
Hi, did you solve this error? I am having the same one. ~/.local/lib/python3.7/site-packages/grpc/_channel.py in __call__(self, request, timeout, metadata, credentials, wait_for_ready, compression) 944 state, call, = self._blocking(request, timeout, metadata, credentials, 945 wait_for_ready,

[grpc-io] Re: grpc.channel_ready_future throw inactive rpc error

2021-06-16 Thread 'Richard Belleville' via grpc.io
It seems that the client is failing to connect to the server: "failed to connect to all addresses", Are you sure that the server is listening on that port? Try running netstat on the server to verify. Are there firewall rules getting in the way? Try using nmap from the client to verify. On Fri