A weird issue index out of range: 3 + 116> 76

1,002 views
Skip to first unread message

gaoyong li

unread,
Mar 15, 2021, 5:07:20 AM3/15/21
to grpc.io
Please see the FAQ in our main README.md before submitting your issue.
I encountered a weird problem using grpc-go. An error is reported when calling the grpc interface, and the error message is "Internal desc = index out of range: 3 + 116> 76". Sometimes it is normal, sometimes an error is reported.

My gateway application will parse the http request body and then call the remote rpc method.

This is my request body,This is my request body, which is exactly 76 bytes

WechatIMG53.png
I have no problems running locally, but when I deploy the application to kubernetes, the above problems sometimes occur, but in most cases it works normally
Under what circumstances will an error in this format appear?

This is the version information of my dependency

WechatIMG54.png

Now I have no way to repeat the error. I worry about this in a live environment.

Please help me. I'd appreciate it

Menghan Li

unread,
Mar 17, 2021, 1:58:02 PM3/17/21
to grpc.io
Can you provide more details of what the client/server do?
And also check kubernetes error logs?

It's not clear to me where the error is from. And this looks like a recovered panic.
gRPC code doesn't use recover. Do you have recover in your code? Or it might be the proxies?

Gaoyong Li

unread,
Mar 17, 2021, 11:23:49 PM3/17/21
to grpc.io
Thanks for your reply!
This is my client code:
WechatIMG57.png
WechatIMG56.png
After the error, I added the code to print the stack, but the error did not reappear.
My client is a gateway service, and the gateway service parses the http request through the gin framework and calls the back-end grpc service.
The GRPC request body is a bytes of json.The back-end grpc server parses the json body and deserializes it into the parameters of the grpc server interface by registering the json codec.
WechatIMG58.png
error message is "A weird issue index out of range: 3 + 116> 76". My request body is exactly 76 bytes, but I don't know what 3 and 116 are.
At the time of the error, kubenetes also had no related logs.
Now this error no longer appears, but I am very worried that it will appear in the live environment

Please help me, thank you very much!!!

Ishaan Kaustav

unread,
Aug 28, 2024, 1:33:44 PMAug 28
to grpc.io
Is this issue resolved ? 
we are getting the similar error , which says index out of bound in response while sending http/2 request to the postman echo server . 
Reply all
Reply to author
Forward
0 new messages