Opened 12 years ago

Closed 12 years ago

#37000 closed defect (worksforme)

sshfs: incompatible libfuse version

Reported by: jonlederman@… Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc:
Port: sshfs

Description (last modified by raimue (Rainer Müller))

HI,

I am unable to run sshfs, which was installed via macports. When I type the command, I get:

sudo echo password | sshfs jon@192.168.2.11:/opt ~/mnt -o
dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid
dyld: Library not loaded: /opt/local/lib/libfuse.2.dylib
  Referenced from: /opt/local/bin/sshfs
  Reason: Incompatible library version: sshfs requires version 11.0.0 or later, but libfuse.2.dylib provides version 10.0.0
Trace/BPT trap: 5

Any help appreciated. Thanks.

Jon

Change History (8)

comment:1 Changed 12 years ago by raimue (Rainer Müller)

Description: modified (diff)

Please use WikiFormatting.

comment:2 Changed 12 years ago by raimue (Rainer Müller)

Owner: changed from macports-tickets@… to dports@…
Port: sshfs added

Your command line shown above is incomplete, -o would expect more parameters for sshfs.

Can you use sshfs the normal way and just enter your password at the password prompt? Giving a password as a program argument is dangerous and should not be used. Use authentication using ssh-keys if you want to avoid typing your password each time.

comment:3 in reply to:  2 Changed 12 years ago by jonlederman@…

Replying to raimue@…:

Your command line shown above is incomplete, -o would expect more parameters for sshfs.

Can you use sshfs the normal way and just enter your password at the password prompt? Giving a password as a program argument is dangerous and should not be used. Use authentication using ssh-keys if you want to avoid typing your password each time.

comment:4 Changed 12 years ago by drkp (Dan Ports)

Summary: sshfssshfs: incompatible libfuse version

It appears you have an older version of libfuse installed, which MacPorts should not normally allow to happen.

What is the output of port -v installed sshfs fuse4x fuse4x-kext?

comment:5 Changed 12 years ago by jonlederman@…

Hi, Here is the output of the command. Please advise.

Thanks.

-Jon

Jons-MacBook-Pro:~ Jon$ port -v installed sshfs fuse4x fuse4x-kext The following ports are currently installed:

fuse4x @0.9.2_0 (active) platform='darwin 12' archs='x86_64' fuse4x-kext @0.9.2_0+universal (active) platform='darwin 12' archs='i386 x86_64' sshfs @2.4_2 (active) platform='darwin 12' archs='x86_64'

comment:6 Changed 12 years ago by jonlederman@…

Hi,

If anyone can help me I would be greatly appreciative. I installed sshfs via macports several days ago and it was working fine. I was connecting to an ubuntu instance. Today it stopped working. The only thing that changed as far as I know is the ip address of the ubuntu instance I am trying to connect to. Now, I get the following error:

Jons-MacBook-Pro:~ Jon$ sshfs localhost:~/Desktop/ ~/mnt -o idmap=jon fuse4x failed to mount /dev/fuse4x0 to /Users/Jon/mnt : Operation not permitted

I also get a dialog box message that says: "The fuse4x failed to mount path". I have no idea what has changed. It sounds like some kind of permissions issue or something with ssh keys. I tried removing ~/.ssh/known_hosts. Is there a way to completely reset sshfs and the configuration and data it may be looking at? But maybe something else is amiss. Any help would be greatly appreciated.

Thanks.

-Jon

comment:7 Changed 12 years ago by drkp (Dan Ports)

The version of the fuse4x package you have installed should be providing libfuse.dylib with version 11.0, not 10.0, so something seems to be wrong with your installation. (Maybe something outside of MacPorts installed an older version of fuse4x on top of the one you have?)

In any case, removing and reinstalling the fuse4x-kext, fuse4x, and sshfs packages should get things working again...

comment:8 Changed 12 years ago by drkp (Dan Ports)

Resolution: worksforme
Status: newclosed

Closing due to lack of response

Note: See TracTickets for help on using tickets.