mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #23] curl ssl problems #14
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @h0nIg on GitHub (Mar 7, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/23
as described on
https://code.google.com/p/s3fs/issues/detail?id=343&can=1
https://code.google.com/p/s3fs/issues/detail?id=257&can=1
https://code.google.com/p/s3fs/issues/detail?id=235&can=1
the problem with curl error 35 (CURLE_SSL_CONNECT_ERROR) still exists with version 1.74. on my case it was caused by a heavy mv with 180 files, 1gb per file
system: ubuntu 12.04
@worpet commented on GitHub (Mar 19, 2014):
I am also seeing this issue with the latest version. I cannot consistently reproduce it, but it seems to most often happen during heavy usage, like when copying many files.
When it breaks, in /var/log/messages this line appears:
@ggtakec commented on GitHub (Mar 21, 2014):
I fixed a bug against #18, and branched codes as "bugfix#18" .
The bug is in retries logic, and I think that as possibly these ssl connect error is caused by it.
("... Retry request. [type=2]..." message in your log.)
If you can, please use "bugfix#18" branch and check it.
Thanks in advance for your help.
@ggtakec commented on GitHub (Mar 22, 2014):
I'm sorry, your problem is not same as #18 (which is error in parallel request).
I continue this problem and check it.
Regards.
@ggtakec commented on GitHub (Apr 4, 2014):
I have beed checked this ssl error reason(from on googlecodes), but could not find it.
I think the reason maybe depends on users network or etc.
So, I added error handling for CURLE_SSL_CONNECT_ERROR in curl.cpp.
If CURLE_SSL_CONNECT_ERROR is occurred, s3fs waits 2 second and retry to send last request again after waiting.
I commit new branch “sslproblem#23”, please try to use this branch and report results.
Regards,
@ggtakec commented on GitHub (Apr 19, 2014):
I merged #32 codes to master branch.
Please try to use it, and if you have same problem, please let me know.
I closed this issue, but you can reopen this issue when latest codes can not solve your problem.
Thanks.