-
Notifications
You must be signed in to change notification settings - Fork 107
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
Instant internal error: Attestation required #5238
Comments
This does not seem specific to Sapphire, but rather it has something to do with remote attestation failing. Initial logs indicate aesmd reporting a parameter error while obtaining a quote, was there recently an aesmd service update? After the restart the quote seemed to have been successfully generated. In any case, can you also provide a |
oasis-node control status -a unix:/home/oasis/sapphire/data/internal.sock | jq |
As an idea. The node works with cipher at one server. May be they conflicted with AESMd somehow, and got this result? Cipher works correct. Aesmd doesn't have any critical errors. |
Looks like your node is working fine now. The issue (attestation failure if the node is running during an aesmd/QE upgrade) has been fixed in master and the fix will be part of the next Core release. |
Ok, no problem. Waiting for update) Thank you! |
Instant filure of attestation.
According to my monitoring? there were no problems at hardware or with connection. But 21st of March at 17:40:57 UTC I had first "err":"runtime: internal error: attestation required" (file sapphire_logs...). At 18:00:09 it was registered.
23.03 at the morning it wasn't responding. Control status was not available.
I restarted it and got other errors (file sapphire_restart) at 23st of March 23 08:43:33.
Second time 08:43:59
My node is pruned for 2 weeks.
sapphire_logs_23_03.txt
sapphire_restart.txt
The text was updated successfully, but these errors were encountered: