Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

708
Views
grpc method call error: Failed to pick subchannel

gRpc Client: Python:3.8 grpcio: 1.38.1

gRpc Server: Dotnet core 5.0 LoadBalancer AKS: 1.19.7

I'm getting below error when my python client calls a method. Any help to resolve is really appreciated.

Python code snippet

with open('chain.pem', 'rb') as f:
        trusted_certs = f.read()

credentials = channel = grpc.ssl_channel_credentials(root certificates=trusted_certs)

# 10.200.3.24 is the K8S service IP with 3 replicas
channel = grpc.secure_channel('10.200.3.24:443', credentails, options=(('grpc.enable_http_proxy', 0),))

stub = query_pb2_grpc.QueryStub(channel)

empty = google_dot_protobuf_dot_empty__pb2.Empty()
data = stub.TestMethod(empty)

error

_InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
    status = StatusCode.UNAVAILABLE
    details = "Empty update"
    debug_error_string = "{"created":"@1625180429.368158115","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3008,"referenced_errors":[{"created":"@1625178894.878505214","description":"Empty update","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":201,"grpc_status":14}]}"
>
over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

This is resolved now. Updating if it helps anyone out there with similar issue. First enable gRpc trace using below two exports and then run your code see the error in detail.

export GRPC_TRACE=all
export GRPC_VERBOSITY=DEBUG

In my case, there was this below error

handshake failed: {"created":"@1582571630.967438000","description":"Peer 
name 10.200.3.24 is not in peer certificate", "file":
"src/core/lib/security/security_connector/ssl/ssl_security_connector.cc",
"file_line":55}

My server self-signed cert (subject:/C=US/ST=US/O=Self Signed/CN=10.100.3.250) did not have subjectAltName extension. After adding subjectAltName extension (IP.1=10.100.3.250), stuff started working fine.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!