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.

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

curl ssl problems #23

Closed
h0nIg opened this issue Mar 7, 2014 · 5 comments
Closed

curl ssl problems #23

h0nIg opened this issue Mar 7, 2014 · 5 comments

Comments

@h0nIg
Copy link

h0nIg commented Mar 7, 2014

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

Mar  7 10:04:30 vm s3fs: connecting to URL https://bucket123.s3-eu-west-1.amazonaws.com?delimiter=/&prefix=path/file/&max-keys=1000
Mar  7 10:04:30 vm s3fs: HTTP response code 200
Mar  7 10:04:30 vm s3fs: contents_xp->nodesetval is empty.
Mar  7 10:04:30 vm s3fs: contents_xp->nodesetval is empty.
Mar  7 10:04:30 vm s3fs: copying... [path=/path/file]
Mar  7 10:04:30 vm s3fs: connecting to URL https://bucket123.s3-eu-west-1.amazonaws.com/path/file
Mar  7 10:06:13 vm s3fs: ### CURLE_RECV_ERROR
Mar  7 10:06:15 vm s3fs: ### retrying...
Mar  7 10:06:15 vm s3fs: Retry request. [type=2][url=https://bucket123.s3-eu-west-1.amazonaws.com/path/file][path=/path/file]
Mar  7 10:06:15 vm s3fs: ###curlCode: 35  msg: SSL connect error
@worpet
Copy link
Contributor

worpet commented 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.

curl --version
curl 7.32.0 (x86_64-redhat-linux-gnu) libcurl/7.32.0 NSS/3.15.2 zlib/1.2.8 libidn/1.28 libssh2/1.4.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz Metalink

When it breaks, in /var/log/messages this line appears:

###curlCode: 35  msg: SSL connect error

@ggtakec
Copy link
Member

ggtakec commented 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
Copy link
Member

ggtakec commented 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
Copy link
Member

ggtakec commented 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
Copy link
Member

ggtakec commented 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.

@ggtakec ggtakec closed this as completed Apr 19, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants