By using AWS re:Post, you agree to the Terms of Use

Socket closed error when running inference using Greengrass

0

Hello

We are using Greengrass v2 with the Sagemaker component in order to do inference on the edge. The following error is seen intermettently while running our application. Could you please advise of anything we can do to avoid it?

File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 946, in call return _end_unary_response_blocking(state, call, False, None) File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking raise _InactiveRpcError(state) grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "Socket closed" debug_error_string = "{"created":"@1650459124.460491853","description":"Error received from peer unix:/tmp/aws.greengrass.SageMakerEdgeManager.sock","file":"src/core/lib/surface/call.cc","file_line":906,"grpc_message":"Socket closed","grpc_status":14}"

1 Answer
0

Hi,

Would you be able to provide the full log at /greengrass/v2/logs/aws.greengrass.SageMakerEdgeManager.log , along with any other relevant log files?

Could you also turn on the debug mode with the SagemakerEdgeLogVerbose config option specified here? https://docs.aws.amazon.com/greengrass/v2/developerguide/sagemaker-edge-manager-component.html#sagemaker-edge-manager-component-log-file

Are there any other applications that could interfere with that socket?

Thanks!

answered 5 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions