Hi Salamy, Sami,
Thanks for getting back, please try below troubleshooting steps:
The error ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
typically indicates that the connection to the Azure service was abruptly closed by the remote server.
- How can I get more info regarding this error? To get more information about the error, you can enable debug logging in the
libcloud
library, check Azure Service Health, and If the error is due to rate limiting or other server-side issues, the response headers might contain useful information. - What is the default timeout for the AZURE_ARM configured driver? The default timeout for the
AZURE_ARM
driver inlibcloud
is typically 60 seconds for both connection and read timeouts. This is defined in thelibcloud.http.LibcloudConnection
class. - Which params should we add in order to manually change the timeout, can I use
timeout=GENERAL_TIMEOUT
orex_connection_kwargs={'timeout': (CONNNECTION_TIMEOUT, READ_TIMEOUT)}
You can change the timeout by passing thetimeout
parameter when initializing the driver. Thetimeout
parameter can be a single value (for both connection and read timeouts) or a tuple(connection_timeout, read_timeout)
. Alternatively, you can useex_connection_kwargs
to pass additional connection arguments. - What other reasons might return such general error? Rate limit? Can we increase it? The
ConnectionResetError
could occur due to several reasons like Network issues, Server-side issues, Rate limiting, Firewall or security settings, Timeouts.
If you have any further queries, please do let us know. If the answer is helpful, please click "Accept Answer" and "Upvote it"