-
Notifications
You must be signed in to change notification settings - Fork 114
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
Link has been severed #38
Comments
I can confirm that this affects CentOS 6.0 |
Identified the same issue under EL6:
|
This is a bummer, since I don't really want to switch to debian. I tried strace against the fuse mount process and don't see any smoking guns. If anyone has any idea how I can track down the problem, let me know? Maybe compile with debug and run through gdb? Happy to help with the fix anyway I can. |
Running CentOS6.2 here. Compiled a version of libcurl that was on my Cent5 instances (7.15.0) and compiling against that fixes this. I will try to look at the api differences (changes from libcurl.so.3 to libcurl.so.4) up to 7.19.7-26.el6_2.4.x86_64 when I have a chance. |
This also worked for me with 7.18.2 but breaks on 7.19.0 (both non RH related sources) |
Is there a way to make cloudfuse work in Centos6.2? |
For cent6.2/3 I built curl/libcurl from source version 7.18.2 as static libraries and linked against libcurl.a from that instead of -lcurl in the cloudfuse Makefile. Building the shared versions overrides the system one and broke some python stuff for me. |
Any updates on Centos 6? Does Rackspace actively contribute too? Seems they are completely unaware it is busted. |
I am also having this issue with CentOS/EL 6, it appears that the latest version of libcurl is causing some issues. It works fine on older versions. |
Hey all, some wonderful person has compiled a cloudfuse binary dynamically linked to the old version of curl here: http://www.transdimensia.ravenhurst.com/2012/08/cloudfuse-on-cenos6.html It worked for me on CentOS 6.3! |
Thanks! Hey all, some wonderful person has compiled a cloudfuse binary dynamically linked to the old version of curl here: http://www.transdimensia.ravenhurst.com/2012/08/cloudfuse-on-cenos6.html It worked for me on CentOS 6.3!
|
I'm not an expert at compiling things, so it took me a few minutes to figure out how to statically link libcurl - it was easier than I expected. Again, it's been a long time - they may have been an (even) easier way to do this.
All told: You can verify that this binary doesn't dynamically load libcurl by running "ldd cloudfuse". You'll notice that libcurl isn't in the list. |
This was kind of an ugly problem to track down, and I didn't fix it the way I wanted to, but cloudfuse should at least work on these systems now. I'll try to get it the way I want later. 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. |
on ubuntu/debian: apt install libcurl4-openssl-dev |
Running Fedora release 15 (Lovelock)
When i mount a folder to cloudfiles i get an error after trying to list the buckets under the mount point.
cloudfuse /mnt/cloudfiles/
[root@ul966js ~]# :Server )ls -l /mnt/cloudfiles/
ls: reading directory /mnt/cloudfiles/: Link has been severed
total 0
When i run the mount command with the -f parameter everything mounts and works as intended.
cloudfuse -f /mnt/cloudfiles/
I've repeated the exact same process i used to compile/configure cloudfuse on a Debian machine and it works perfectly without the -f flag.
I found the -f flag fix from this URL: http://makewhatis.com/2011/05/mounting-your-rackspace-cloudfiles-in-centosrhel-5-55-6-via-cloudfuse so it looks like this issue affects Centos/RHEL 5.5/5.6 as well.
The text was updated successfully, but these errors were encountered: