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

rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake #3215

Closed
darmawan01 opened this issue Nov 28, 2019 · 4 comments

Comments

@darmawan01
Copy link

try to run golang with grpc healt check in container with docker run,
get som problem timed out waiting for server handshake. I was added
GRPC_GO_REQUIRE_HANDSHAKE=off but it still error

Here is my specifications:

  • Go version 1.12
  • grpc 1.25.1
  • google.golang.org/grpc/health/grpc_health_v1 latest version

log when i added GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info

INFO: 2019/11/28 12:35:09 parsed scheme: ""
INFO: 2019/11/28 12:35:09 scheme "" not registered, fallback to default scheme
INFO: 2019/11/28 12:35:09 ccResolverWrapper: sending update to cc: {[{localhost:8000 0  <nil>}] <nil>}
INFO: 2019/11/28 12:35:09 ClientConn switching balancer to "pick_first"
INFO: 2019/11/28 12:35:09 pickfirstBalancer: HandleSubConnStateChange: 0xc000021540, CONNECTING
INFO: 2019/11/28 12:35:29 transport: loopyWriter.run returning. connection error: desc = "transport is closing"
WARNING: 2019/11/28 12:35:29 grpc: addrConn.createTransport failed to connect to {localhost:8000 0  <nil>}: didn't receive server preface in time. Reconnecting...
INFO: 2019/11/28 12:35:29 pickfirstBalancer: HandleSubConnStateChange: 0xc000021540, TRANSIENT_FAILURE
rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: timed out waiting for server handshake
@menghanl
Copy link
Contributor

menghanl commented Dec 4, 2019

As said in #2406, the option to not wait for handshake was entirely removed, and the client always expect server to send handshake now.

What server is the client talking to? If you are using cmux, please try soheilhy/cmux#64 (comment).

@darmawan01
Copy link
Author

It's working fine if using grpc 1.20.1

@menghanl
Copy link
Contributor

menghanl commented Dec 5, 2019

I believe the option was removed in https://github.com/grpc/grpc-go/releases/tag/v1.23.0

@darmawan01
Copy link
Author

thanks @menghanl , i will learn about the issues your given.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants