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.

Sign up for GitHub

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

Jump to bottom

Getting error "ConnectionResetError: [Errno 104] Connection reset by peer" when checking if directory exists in the azure file share #22244

Closed
sorin-bolos opened this issue Dec 21, 2021 · 4 comments
Closed

Getting error "ConnectionResetError: [Errno 104] Connection reset by peer" when checking if directory exists in the azure file share #22244

sorin-bolos opened this issue Dec 21, 2021 · 4 comments
Assignees
@vincenttran-msft
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)

Comments

@sorin-bolos
Copy link

  • Package Name: azure-storage-file
  • Package Version: latest
  • Operating System: Docker container Redhat UBI 8
  • Python Version: 3.8

Describe the bug
Getting error "ConnectionResetError: [Errno 104] Connection reset by peer" when checking if directory exists in the azure file share
The error happens randomly but fairly often.
The stack trace also says Max retries exceeded but I cannot tell how many retries were made if any. As the caller of azure.storage.file.FileService.exists() I cannot control the retry policy.

Expected behavior
The client should be able to check if a directory exists without any errors
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 21, 2021
@yunhaoling yunhaoling added bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. CXP Attention Storage Storage Service (Queues, Blobs, Files) and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 21, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 21, 2021
@yunhaoling
Copy link
Contributor

thanks for reaching out @sorin-bolos , we will investigate it ASAP.

@tasherif-msft
Copy link
Contributor

Hi @sorin-bolos thanks for opening the issue. This is a known issue that we are investigating and having discussions across languages to discuss what the best solution is. I will update you once I have more information!

@lmazuel lmazuel added Service Attention Workflow: This issue is responsible by Azure service team. and removed CXP Attention labels Jan 13, 2023
@ghost
Copy link

ghost commented Jan 13, 2023

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details
  • Package Name: azure-storage-file
  • Package Version: latest
  • Operating System: Docker container Redhat UBI 8
  • Python Version: 3.8

Describe the bug
Getting error "ConnectionResetError: [Errno 104] Connection reset by peer" when checking if directory exists in the azure file share
The error happens randomly but fairly often.
The stack trace also says Max retries exceeded but I cannot tell how many retries were made if any. As the caller of azure.storage.file.FileService.exists() I cannot control the retry policy.

Expected behavior
The client should be able to check if a directory exists without any errors

Author: sorin-bolos
Assignees: tasherif-msft
Labels:

bug, Storage, Service Attention, Client, customer-reported
Milestone: -

@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 13, 2023
@vincenttran-msft vincenttran-msft removed needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. labels Jan 26, 2023
@ghost ghost added the needs-team-triage Workflow: This issue needs the team to triage. label Jan 26, 2023
@github-actions github-actions bot removed the needs-team-triage Workflow: This issue needs the team to triage. label Jan 26, 2023
@vincenttran-msft
Copy link
Member

Hi @sorin-bolos Sorin, thanks for your inquiry about this issue. I can see that when you created this post, you were using the azure-storage-file package, which has now been replaced by azure-storage-file-share.

I have gone ahead and written a test script to check if directory exists with our new package and did not find any connection reset issues after letting the script run for ~15 minutes.

With that being said, I am going to mark this issue as resolved for the time being. Please reach out if you have any questions!

Thanks!

azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this issue Feb 28, 2023
@mozansaka
CodeGen from PR 22124 in Azure/azure-rest-api-specs
fbd30b3 
[Hub Generated] Review request for Microsoft.DBforPostgreSQL to add version stable/2022-11-08 (Azure#22124)

* Adds base for updating Microsoft.DBforPostgreSQL from version preview/2020-10-05-privatepreview to version 2022-11-08

* Updates readme

* Updates API version in new specs and examples

* empty commit (Azure#21932)

Co-authored-by: Ozan Saka <mesaka@microsoft.com>

* 2022 11 08 (Azure#22025)

* Add private endpoint con. and private link endpoints

* Add private link list example

* Cluster related endpoint and exampled changes

* Cluster changes and configuration updates

* Long running operation header additions

* Change server group to cluster

* Add systemData to examples, fix private endpoint con. property

* Fix private link resource name parameter

* Fix INVALID_TYPE boolean given as strings

* Update approve private endp. con. request body

* Fix OBJECT_ADDITIONAL_PROPERTIES and READONLY_PROPERTY_NOT_ALLOWED_IN_REQUEST

* Fix INVALID_TYPE

* Fix ModelValidation Errors

* Fix lint errors

* Fix lint errors

* Remove location from cluster examples

* Update example details, fix common types

* Update readme files, fix configuration example name

* Fix SDK generation by removing wrong pageable tags

* Update configuration response types, fix cluster name pattern

* Update configuration example names

* Readme changes and minor final state via fix

* Fix indentation on suppression items

* Update node count description, remove pec id

* Update cluster examples

* Style fix

* Update description

Co-authored-by: Ozan Saka <mesaka@microsoft.com>
Co-authored-by: Sena Gungor <segungor@microsoft.com>

* Fix credscan password (Azure#22127)

Co-authored-by: Ozan Saka <mesaka@microsoft.com>

* Add required parameters (Azure#22244)

* Add 200 resp. code to put&patch, change boolean to enum (Azure#22290)

* Add 200 resp. code to put&patch, change boolean to enum

* Update 200 responses

* Update 200 response schemas, enum casing

* Update configuration put requests

* Remove role no-op case

* fix private endp con list error, remove 200 code from role example

* Add coord/node config list endpoints

* fix sdk errors

* add 200 resp for configuration put requests

* Update readme

* Fix arm feedbacks (Azure#22334)

* Fix arm feedbacks

* Add pointInTimeUTC

* Update passwords and readme file

* Update response codes to 201, address feedbacks (Azure#22386)

* Update response codes to 201

* Add server configuration get

* Update password

* Fix duplicate operation id

* Update configuration example files

* Update configuration example files

* Fix credscan issue (Azure#22389)

* Fix PutRequestResponseScheme error (Azure#22408)

* Fix PutRequestResponseScheme error

* Update readme file

* Update x-ms-mutability

* Update property description

* Fix server properties (Azure#22772)

* Fix server properties

---------

Co-authored-by: mozansaka <ozan.saka@gmail.com>
Co-authored-by: Ozan Saka <mesaka@microsoft.com>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@vincenttran-msft vincenttran-msft

Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lmazuel @sorin-bolos @yunhaoling @tasherif-msft @vincenttran-msft