-
Notifications
You must be signed in to change notification settings - Fork 21
[Ppal Node]: Retries for connecting to sgx.enigma.co #98
Comments
@elichai: I have seen this error thrown by |
@lacabra There principal node isn't explicitly retrying these requests. It is calling |
@fredfortier As I mentioned above both |
@lacabra are you still experiencing this issue? I'm interested in making order in the KM issues. Thanks! |
I have not experienced this particular issue recently, but I don't think this has been addressed either, and in my opinion is worth improving: adding retrials for both core and the km to get the report from our IAS proxy. We are trying to avoid that if for any reason the first attempt fails, either piece of code would crash and bring down the node. |
@AvishaiW (Cc: @moriaab): I have experienced this issue twice right now, once with As far as I can tell it is hard to reproduce because it depends on sgx.enigma.co being temporarily down. |
Is your feature request related to a problem? Please describe.
I got the following error while launching the Principal Node:
I don't know if this would also be an issue in Core? Cc: @elichai
https://sgx.enigma.co/api was indeed online at the time, and a subsequent manual request succeeded.
Describe the solution you'd like
I would suggest coding in at least 3 retries for trying this connection, otherwise the Principal Node crashes.
Describe alternatives you've considered
N/A
Additional context
backtrace of the error above:
The text was updated successfully, but these errors were encountered: