Issue 257 in s3fs: Issue with newer versions of curl and s3fs
s3...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 257 by ad...@digitaltactics.co.uk: Issue with newer versions of
curl and s3fs
http://code.google.com/p/s3fs/issues/detail?id=257
Detailed description of observed behavior:
This exists within other comments but I don't think it's flagged an issue
in its own right... Seems to be a curl 7.19.7 issue (poss other versions
also affected)
mount /bucket with https s3 endpoint
ls /bucket
ls: reading directory /bucket: Software caused connection abort
ls /bucket
ls: cannot access /s3fs/irb-podcast/: Transport endpoint is not connected
mount /bucket with http s3 endpoint
ls /bucket
returns file list
What steps will reproduce the problem - please be very specific and
detailed. (if the developers cannot reproduce the issue, then it is
unlikely a fix will be found)?
Build and install s3fs on an amazon linux image updated to the most recent
versions of software
===================================================================
The following information is very important in order to help us to help
you. Omission of the following details may delay your support request or
receive no attention at all.
===================================================================
Version of s3fs being used (s3fs --version):
1.61 but issue goes back to at least 1.40
Version of fuse being used (pkg-config --modversion fuse):
2.8.6
System information (uname -a):
Linux ip-xx-xx-xx 2.6.35.14-106.53.amzn1.x86_64 #1 SMP Fri Jan 6 16:20:10
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Distro (cat /etc/issue):
Amazon Linux AMI release 2011.09
Kernel \r on an \m
s3fs command line used (if applicable):
mountpoint /bucket || /usr/local/bin/s3fs -o default_acl=public-read -o
url=https://s3.amazonaws.com my-bucket /bucket
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog):
s3fs: init $Rev: 367 $
s3fs: ###curlCode: 35 msg: SSL connect error
s3...@googlecode.com
Comment #1 on issue 257 by ad...@digitaltactics.co.uk: Issue with newer
http://code.google.com/p/s3fs/issues/detail?id=257
the
ls: cannot access /s3fs/irb-podcast/: Transport endpoint is not connected
should read
ls: cannot access /bucket: Transport endpoint is not connected
The was testing this in another area too
s3...@googlecode.com
Comment #2 on issue 257 by nick.gre...@gmail.com: Issue with newer versions
http://code.google.com/p/s3fs/issues/detail?id=257
same issue. tested on Amazon Linux AMI release 2011.09
fuse 2.8.6-1.10.amzn1 (and 2.8.5-99.vitki.01.amzn1)
libcurl-7.19.7-26.21.amzn1.i686
s3fs 1.40 1.58 1.61
s3...@googlecode.com
Comment #3 on issue 257 by nick.gre...@gmail.com: Issue with newer versions
http://code.google.com/p/s3fs/issues/detail?id=257
FYI version s3fs 1.33 works well
s3...@googlecode.com
Comment #4 on issue 257 by nsw...@gmail.com: Issue with newer versions of
This same issue is noted at
http://code.google.com/p/s3fs/issues/detail?id=235 and is still unresolved
s3...@googlecode.com
Comment #5 on issue 257 by m...@scene53.com: Issue with newer versions of
This looks similar to issues over at the CloudFuse project. They traced the
problem back to libcurl.
https://github.com/redbo/cloudfuse/issues/38
If you want to know: libcurl on rhel-like OSs is linked against NSS instead
of OpenSSL, like I'm used to. NSS has some weird thing where it stops
working if you initalize it, then fork() (which is why everything worked
fine if you ran it in the foreground, no fork to detach it). I just moved
authentication to after the fork, so NSS gets initialized in the new
process instead. This means there's less user feedback for auth problems,
but at least it works.
s3...@googlecode.com
Comment #6 on issue 257 by m...@scene53.com: Issue with newer versions of
...More specifically, I worked around the issue by linking against
curl-7.18.2. I used a similar process as I documented in the cloudFuse
ticket ( https://github.com/redbo/cloudfuse/issues/38 )
The only difference here is that I let s3fs compile everything, then I
re-linked everything afterwards. In addition to the compiled libcurl.a, I
needed to add "-lidn -lz -lssl":
g++ -g -O2 -Wall -D_FILE_OFFSET_BITS=64 -o s3fs s3fs.o curl.o cache.o
string_util.o /home/ec2-user/s3fs/curl-7.18.2/lib/.libs/libcurl.a -pthread
-L/lib64 -lfuse -lrt -ldl -lxml2 -lcrypto -lidn -lz -lssl
s3...@googlecode.com
Status: Fixed
Comment #7 on issue 257 by ggta...@gmail.com: Issue with newer versions of
Hi
Revision 430 fixes issue 235 which is one of "Transport endpoint is not
connected" error.
And latest version, I use and check it, and it seems that s3fs works good
on this version.
Please use latest revision(not packaged now), and if you have a problem
yet, please re-post new issue.
Thanks in advance for your help.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
s3...@googlecode.com
Status: Accepted
Comment #8 on issue 257 by ggta...@gmail.com: Issue with newer versions of
I'm sorry for this issue is not fixed.
s3fs has "SSL connect error" trouble now, but I'll fix it soon.
So that, I reopen this issue.
Thans.
s3...@googlecode.com
Status: Fixed
Comment #9 on issue 257 by ggta...@gmail.com: Issue with newer versions of
New version v1.70(r434) is updated.
It fixes this issue.
Please use this version, and if you have a trouble, please post new issue.
Thanks a lot.
s3...@googlecode.com
Comment #10 on issue 257 by a...@artaman.net: Issue with newer versions of
Centos 6.4, just compiled s3fs 1.71 with curl-7.31.0 and fuse-2.9.3.
Problem is still there when trying to connect via https.
s3...@googlecode.com
Comment #11 on issue 257 by nicho...@nicholaswilliams.net: Issue with newer
Yes, with curl-7.28 I can confirm that this is still broken. Can't use
HTTPS at all, which is unfortunately very insecure. Can we get a fix for
this ASAP?
I will create another issue per your June 1 comment.
s3...@googlecode.com
Comment #12 on issue 257 by ggta...@gmail.com: Issue with newer versions of
Hi, all
This issue was succeeded in Issue 359.
Nicholas, Thanks for your assistance.
Regards.
s3...@googlecode.com
Comment #13 on issue 257 by mamtapre...@gmail.com: Issue with newer
Hi, I am trying to mount a S3 bucket in an Amazon Ec2 (Red Hat Enterprise
Linux 6.4 for Cluster Instances machine). T get the following messages.
[root@ip-172-31-9-231 s3fs]# s3fs -o allow_other -o use_cache=/tmp
bryteflowcdc /mnt/s3/bryteflowcdc
[root@ip-172-31-9-231 s3fs]# grep s3fs /etc/mtab
s3fs /mnt/s3/bryteflowcdc fuse.s3fs rw,nosuid,nodev,allow_other 0 0
[root@ip-172-31-9-231 s3]# ls -l
ls: cannot access bryteflowcdc: Transport endpoint is not connected
total 0
Other details
[root@ip-172-31-9-231 s3]# pkg-config --modversion fuse
2.9.1
[root@ip-172-31-9-231 s3fs]# s3fs --version
Amazon Simple Storage Service File System 1.73
Copyright (C) 2010 Randy Rizun <rri...@gmail.com>
License GPL2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Any ideas on how to rectify the Transport endpoint not connected error.
Thanks
MP