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

run grpcui and got "Symbol not found: grpc.health.v1.Health" #82

Closed
plong009 opened this issue Aug 3, 2020 · 3 comments
Closed

run grpcui and got "Symbol not found: grpc.health.v1.Health" #82

plong009 opened this issue Aug 3, 2020 · 3 comments

Comments

@plong009
Copy link

plong009 commented Aug 3, 2020

hello,
I run grpcui 1.0.0 release on Windows and it failed.
E:>grpcui.exe -plaintext 127.0.0.1:50051
Failed to compute set of methods to expose: Symbol not found: grpc.health.v1.Health

but there is a grpc.health.v1.Health service, grpcurl can list it out.
E:>grpcurl.exe -plaintext 127.0.0.1:50051 list
grpc.health.v1.Health
grpc.reflection.v1alpha.ServerReflection
my_grpc.my_grpc_service

the service is wroten c++, almost same as the grpc example greeter_server.cc,
does anyone known how to resolve this issue?
thank you!

@plong009
Copy link
Author

plong009 commented Aug 3, 2020

looks like it's grpc.health.v1.Health issue, grpcurl also can't list methods.
E:>grpcurl.exe -plaintext 127.0.0.1:50051 list grpc.health.v1.Health
Failed to list methods for service "grpc.health.v1.Health": Symbol not found: grpc.health.v1.Health

sorry,
please close the issue.

@jhump
Copy link
Contributor

jhump commented Aug 3, 2020

@plong009, can you take a look at #40 and see if the suggestion there helps? The issue observed there was that a linker optimization discarded some of the data that is needed at runtime for reflection to work properly. That issue indicates linker options when building the C++ server that may help.

@jhump
Copy link
Contributor

jhump commented Feb 14, 2022

This is a duplicate of #40. Also, I believe it is fixed as of #160 as thus fixed in the next release.

I think it's possible that the root cause was the server's reflection implementation providing unexpected extra files in the response, and the reflection conflict making incorrect assumptions about the order of those files. Also see jhump/protoreflect#466.

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