[GH-ISSUE #126] Commit `045f1e7` breaks s3fs v1.78 on CentOS 5 with CURL v7.19.7 #76

New issue

Closed

opened 2026-03-04 01:41:48 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:41:48 +03:00

Owner

Originally created by @AbrahamLopez10 on GitHub (Feb 19, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/126

Please see this issue reported on Google Code:
https://code.google.com/p/s3fs/issues/detail?id=447

Reverting the aforementioned commit 045f1e7 fixes the issue.

Commit needs to be reviewed to ensure it doesn't breaks compatibility with CentOS5, which comes with CURL v7.19.7.

Originally created by @AbrahamLopez10 on GitHub (Feb 19, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/126 Please see this issue reported on Google Code: https://code.google.com/p/s3fs/issues/detail?id=447 Reverting the aforementioned commit 045f1e7 fixes the issue. Commit needs to be reviewed to ensure it doesn't breaks compatibility with CentOS5, which comes with CURL v7.19.7.

kerem closed this issue

2026-03-04 01:41:48 +03:00

kerem commented

2026-03-04 01:41:49 +03:00

Author

Owner

@JordanMagnuson commented on GitHub (Mar 2, 2015):

Same issue on Ubuntu 12.04 with fuse 2.8.6 and curl 7.22.0:

s3fs_init(2660): init InitShareCurl(340): curl_share_setopt(SSL SESSION) returns 1(Unknown share option) s3fs: Could not initiate curl library.

Reverting to s3fs v1.77 fixed the problem.

@JordanMagnuson commented on GitHub (Mar 2, 2015): Same issue on Ubuntu 12.04 with fuse 2.8.6 and curl 7.22.0: `s3fs_init(2660): init InitShareCurl(340): curl_share_setopt(SSL SESSION) returns 1(Unknown share option) s3fs: Could not initiate curl library.` Reverting to s3fs v1.77 fixed the problem.

kerem commented

2026-03-04 01:41:49 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 21, 2015):

@JordanMagnuson
I merged #156 for this issue.
libcurl older than 7.23.0 does not support ssl session shared, so this problem is occurred.
By merged codes s3fs will run with older libcurl.
In other ways, if you do not use ssl session shaing or dns sharing, you can use "nodnscache" and "nosscache" option.(those option are not listed in man page)

Please try to test latest codes, and if you can not run s3fs please post new issue.
Regards,

@ggtakec commented on GitHub (Mar 21, 2015): @JordanMagnuson I merged #156 for this issue. libcurl older than 7.23.0 does not support ssl session shared, so this problem is occurred. By merged codes s3fs will run with older libcurl. In other ways, if you do not use ssl session shaing or dns sharing, you can use "nodnscache" and "nosscache" option.(those option are not listed in man page) Please try to test latest codes, and if you can not run s3fs please post new issue. Regards,