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

startup broken because of missing shard init #1520

Closed
brenzi opened this issue Dec 11, 2023 · 0 comments · Fixed by #1521
Closed

startup broken because of missing shard init #1520

brenzi opened this issue Dec 11, 2023 · 0 comments · Fixed by #1521
Assignees
Labels
F2-bug Something isn't working

Comments

@brenzi
Copy link
Collaborator

brenzi commented Dec 11, 2023

The last PR reordered the startup sequence. I we run the service without the -c clean reset flage, we get:

We are the primary worker on this shard and the shard is untouched. Will initialize it
�[0m�[38;5;8m[�[0m2023-12-11T08:53:13Z �[0m�[34mDEBUG�[0m enclave_runtime�[0m�[38;5;8m]�[0m initializing shard creation header: Integritee
�[0m�[38;5;8m[�[0m2023-12-11T08:53:13Z �[0m�[1m�[31mERROR�[0m enclave_runtime�[0m�[38;5;8m]�[0m Failed to initialize first relevant parentchain header [Integritee]: Other("shard not initialized")
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Sgx(SGX_ERROR_UNEXPECTED)', service/src/main_impl.rs:542:22
@brenzi brenzi added the F2-bug Something isn't working label Dec 11, 2023
@brenzi brenzi changed the title startup broken becasue of missing shard init startup broken because of missing shard init Dec 11, 2023
@brenzi brenzi self-assigned this Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
F2-bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant