-
I've been trying to upgrade our chain to SDK 0.47, to start I am going through the upgrade steps in this repo that has a module we depend on in sommelier (fork of Gravity). The issue I'm having is that the gRPC server seems to not be starting after making the recommended service registration changes. The app.toml has gRPC enable on port 9090. Using grpcurl errors saying the server does not support reflection, and our sidecar processes that query the chain are unable to establish a connection. The query routes seem to at least be wired correctly as RPC queries via the CLI are working. I've been stuck on this for a while, has anyone seen this issue before? The WIP branch can be found here: https://github.com/PeggyJV/gravity-bridge/tree/collin/sdk-0.47 You'll find that I've completed the following steps: Register queries in RegisterTxService Register node service method and gateway routes Register module services Implement RegisterGRPCGatewayRoutes I think there were a few other steps I can't remember offhand, but I've had several people look at this and nothing has stood out. Hopefully I'm missing something obvious; help is much appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi @cbrit, by any chance could you post the following:
Also, to be clear, you CAN execute queries against the :1337 HTTP API? e.g. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Thank you for the help. I've fixed it now and the cause seems to be twofold:
golang:alpine
, but had changed the pinned go version for the app, and apparently there was an incompatibility. Instead of failing to build or run, it was just silently killing gRPC? I still don't understand why this happened. By pinning to an image that uses the same go version I was able to to get gRPC working from inside the container.