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

please explain the error message #126

Open
Agent-Hellboy opened this issue Oct 4, 2024 · 5 comments
Open

please explain the error message #126

Agent-Hellboy opened this issue Oct 4, 2024 · 5 comments

Comments

@Agent-Hellboy
Copy link

Hi, what does below error mean ?

rpc error: code = DeadlineExceeded desc = received context error while waiting for new LB policy update: context deadline exceeded

@Agent-Hellboy Agent-Hellboy changed the title Explain error code please explain the error message Oct 4, 2024
@vadimi
Copy link
Owner

vadimi commented Oct 4, 2024

hello, the error is coming from grpc-go connectivity code - it means that it failed to connect to the service, most likely it's not accessible

@Agent-Hellboy
Copy link
Author

Agent-Hellboy commented Oct 7, 2024

received context error while waiting for new LB policy update:

This seems too internal , is it that load balancer is not able to pick a channel ? what is it? I am able to ping my grpc server port , btw it worked fine for one of my grpc server , Thanks for the amazing tool

@vadimi
Copy link
Owner

vadimi commented Oct 7, 2024

it's hard to tell what's going on in your environment - is your service behind some sort of proxy/load balancer? the port could be open, but if http/2 protocol is not properly exposed then it will cause connectivity issues.

@Agent-Hellboy
Copy link
Author

Hi @vadimi does the tool support secure mode? Does it require an SSH key or any other configuration for TLS? It's possible the error is related to running it in secure mode.

@vadimi
Copy link
Owner

vadimi commented Oct 15, 2024

yes, it does, if you run it with grpc-client-cli --help it will show the flags you need to pass: --tls, --cert, --certkey depending on your use case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants