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

Must restart CI multiple times because of an aesm error #1403

Open
clangenb opened this issue Aug 1, 2023 · 2 comments
Open

Must restart CI multiple times because of an aesm error #1403

clangenb opened this issue Aug 1, 2023 · 2 comments

Comments

@clangenb
Copy link
Contributor

clangenb commented Aug 1, 2023

It has been a while since I filed a few PRs, so I can't say how recent this is:

[init ../../../psw/ae/aesm_service/source/core/ipc/UnixCommunicationSocket.cpp:225] Failed to connect to socket /var/run/aesmd/aesm.socket
[2023-08-01T05:15:25Z ERROR integritee_service::ocall_bridge::ffi::init_quote] [-]  Failed to init quote: InitQuote(SGX_ERROR_SERVICE_UNAVAILABLE)
[2023-08-01T05:15:25Z ERROR itp_stf_executor::executor] Fatal Error. Failed to attempt call execution: Sgx(SGX_ERROR_SERVICE_UNAVAILABLE)

It occurred on #1398 and on #1399 often enough so that I am not 100% sure that my change has nothing to do with it. On the other hand, #1375 was merged quite recently, it could also just be that it is not stable. My belief about instability is further strengthened by the fact that it mostly seems to occur with the long-running indirect invocation tests, where the socket is just crashes at some point.

@clangenb clangenb changed the title Must restart CI multiple times because of an aesmd error Must restart CI multiple times because of an aesm error Aug 1, 2023
@clangenb
Copy link
Contributor Author

clangenb commented Aug 1, 2023

Ah, just saw this comment, which hardens my suspicion that it is unrelated to my PRs regarding the provisioning of the light client: #1375 (comment)

@brenzi
Copy link
Collaborator

brenzi commented Aug 7, 2023

this could be partially mitigated (or at least made less frequent) by #1405

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