mc2-project / mc2-project/mc2

Issue running mc2 client

Open
#207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
304
Forks
45
PR merge metrics
No merged PRs in 30d

Description

I am constantly getting this issue: how to resolve this?
File "/mc2/client/mc2.py", line 192, in
mc2.configure_job(config)
File "/usr/local/lib/python3.6/dist-packages/mc2client-0.0.1-py3.6.egg/mc2client/core.py", line 1215, in configure_job
_attest(head_address, simulation_mode, enclave_signer_pem)
File "/usr/local/lib/python3.6/dist-packages/mc2client-0.0.1-py3.6.egg/mc2client/core.py", line 1271, in _attest
response = stub.GetRemoteEvidence(attest_pb2.AttestationStatus(status=0))
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 = "failed to connect to all addresses"
debug_error_string = "{"created":"@1732308449.684310175","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3008,"referenced_errors":[{"created":"@1732308449.684306938","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at /mc2/client/mc2.py line 192, then trace configure_job in mc2client/core.py around lines 1215 and 1271, where _attest calls GetRemoteEvidence. Investigate the gRPC UNAVAILABLE error and failed connection addresses; done means documenting the cause and a reproducible resolution for this client setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc, python
Domain
api, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.