Loading Profile...
FTP volumes won't mount!
After I add the FTP drive settings, I click connect, it turns yellow then green, the after 3 seconds, the status light disappears... And its not mounted anywhere.
I’m sad
8
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
-
Inappropriate?This used to happen to me too but now all I'm getting is a 'could not connect' message and 'bad packet length 842149933, 2'
I’m confused
-
Inappropriate?Stavros -
That problem is generally when you're in SFTP mode intead of FTP/FTPS mode.
-Jeff6 Comments
Add a comment
This solves the problem
-
Well, I am in FTP/FTPS mode and have exactly the same problem. Is there a way to enable some logging to see what is going on? -
Interested in doing an iChat screensharing session to demonstrate the problem?
-
Sure, let me stop Adium and start iChat
-
So, how do I contact you?
-
Did y'all make any progress debugging this yesterday?
-
Not really, but there is a SW update coming out soon, I was told.
-
Inappropriate?Actually, I'm not getting as far as a green light. About all I see is a flash of yellow, then ... nothing.
I’m sad
-
Inappropriate?Same thing here - though only on some ftp-servers. -
Inappropriate?We have a known problem with some configurations when there is an FTP-aware firewall between you and the server. The symptoms are the same as you are describing. If that does turn out to be your problem, I'm pleased to report it will be fixed by our next update.
-
Inappropriate?We just released 1.3.1 which addresses a lot of the FTP compatibility issues people were seeing. Give it a spin and let us k now how it goes.
-
Inappropriate?Great - fixed it for me!
However, people should know that the failed attempts left invisible directories named "ftp server", "ftp server 1", "ftp server 2", etc in the /Volumes folder which should be deleted using the terminal.
Otherwise the successful attempt will mount as "ftp server 6" or however many times you tried before.
Thanks for the quick fix, again!1 Comment Add a comment
This solves the problem
-
This issue with the additional directories is indeed troubling. Not only is the ftp still not working for me (some python issue), but now I have empty (mountpoint) directories for every entry in ExpanDrive for every time I started it ...
-
-
Inappropriate?Yeah, verily, I have tasted of the FTP begat by ExpanDrive and I have wept for joy.
I’m enjoy-lated
-
Inappropriate?I'm running the 1.3.1 upgrade, and still getting the "blink... oh no wait.. that didn't work" thing. Trying both an ftp and an sftp connection. I can however connect straight through with Transmit or via browser. One thing which might help - I vaguely seem to recall something about using passive mode in Transmit...
Is there some log somewhere that I could be checking?
I’m sad
-
Inappropriate?Richard - Sorry you're having trouble!
I'm surprised you cannot access FTP or SFTP. Our FTP support is brand new, and there are some likely incompatibilities, but SFTP has been around and kicking for a while.
Could you check Console.app to see if anything interesting is being logged by ExpanDrive?1 Comment Add a comment
This solves the problem
-
I think I have figured out the problem for me :) - in looking at the console log I see ExpanDrive manipulating the userid it uses to signon - I am using Yahoo Hosting so my signon needs to be exactly what I put for the userid - if the site is ftp.xxx.com then either it needs to allow just the name I use (marvin) or allow me to enter the full name as marvin@xxx.com not use marvin@ftp.xxx.com - the error I get in the log isn't much help though - it's:
EXPANDRIVE_AUTH_PASSWORD:marvin^citycomber.com@ftp.citycomber.com
2008-10-16 17:56:57.232 ExpanDrive[1420] EXPANDRIVE_CONNECT_FAILURE:
2008-10-16 17:56:57.233 ExpanDrive[1420] Couldn't connect because
the time I tried to use marvin@citycomber.com - since normally a ftp client allows you to enter the full name yourself - notice y'all changed the @ to the ^ -
Inappropriate?See if this helps -
16/10/2008 22:49:32 ExpanDrive[158] EXPANDRIVE_AUTH_PASSWORD:u35107196@dyce.com
16/10/2008 22:49:32 ExpanDrive[158] EXPANDRIVE_CONNECT_PROGRESS:drive_connected
16/10/2008 22:49:32 ExpanDrive[158] EXPANDRIVE_MKDIR_MOUNTPOINT:/Volumes/motoproj 3
16/10/2008 22:49:32 ExpanDrive[158] Traceback (most recent call last):
16/10/2008 22:49:32 ExpanDrive[158] File "/expandrive/fs/ftpfs/Driver.py", line 257, in <module>
16/10/2008 22:49:32 ExpanDrive[158] File "/expandrive/fs/ftpfs/Driver.py", line 243, in main
File "/expandrive/fs/ftpfs/Driver.py", line 211, in start_ftpfs
File "/expandrive/fs/fstools/fuse.py", line 372, in __init__
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 353, in __getattr__
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 358, in __getitem__
AttributeError: dlsym(RTLD_DEFAULT, fuse_main_real): symbol not found
</module>
Seems like something awry with the fuse driver thingambob?
I’m puzzled
-
Inappropriate?Could you give the output for SFTP too?
thanks1 Comment Add a comment
This solves the problem
-
Any ideas yet?
-
Inappropriate?Here's both together, one after the other...
16/10/2008 23:06:50 ExpanDrive[133] File "/expandrive/fs/ftpfs/Driver.py", line 257, in <module>
File "/expandrive/fs/ftpfs/Driver.py", line 243, in main
File "/expandrive/fs/ftpfs/Driver.py", line 211, in start_ftpfs
File "/expandrive/fs/fstools/fuse.py", line 372, in __init__
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 353, in __getattr__
16/10/2008 23:06:50 ExpanDrive[133] File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 358, in __getitem__
AttributeError: dlsym(RTLD_DEFAULT, fuse_main_real): symbol not found
16/10/2008 23:06:56 ExpanDrive[133] Traceback (most recent call last):
16/10/2008 23:06:56 ExpanDrive[133] File "/expandrive/ExpanDrive.py", line 9, in </module><module>
File "/expandrive/pyfuse/fuse.py", line 26, in </module><module>
ImportError: dlopen(/Applications/ExpanDrive.app/Contents/ExpanDrive/pyfuse/fuseparts/_fusemodule.so, 2): Library not loaded: /usr/local/lib/libfuse.0.dylib
Referenced from: /Applications/ExpanDrive.app/Contents/ExpanDrive/pyfuse/fuseparts/_fusemodule.so
Reason: image not found
</module>
Hope that helps -
Inappropriate?CityComber: The message you see after the label "EXPANDRIVE_AUTH_PASSWORD" is constructed merely for the purpose of prompting the human at the controls. The actual username sent to the FTP server is literally what you typed into the Username field in the New Drive window. So, if you entered "marvin^citycomber.com" that's what gets sent as the user name.1 Comment Add a comment
This solves the problem
-
Thanks M.J. but it is changing my entry as noted in these messages:
2008-10-16 22:14:38.769 ExpanDrive[1420] EXPANDRIVE_AUTH_PASSWORD:marvin^citycomber.com@ftp.citycomber.com
2008-10-16 22:14:39.201 ExpanDrive[1420] EXPANDRIVE_CONNECT_FAILURE:
2008-10-16 22:14:39.202 ExpanDrive[1420] Couldn't connect because
I typed in marvin@citycomber.com & it changed the @ to ^ & appended the ftp.citycomber.com on its own! -
Inappropriate?CityComber: As I said before, the "@ftp.citycomber.com" is only shown in that message for the purpose of prompting you for the password---it's not sent to the server. However, if you didn't type in the ^ the first time, then that's something we have to look at!
-
Inappropriate?Hi,
Have tried the 1.3.2b3 update. Still no joy. I know that the connection details are ok, as Transmit works fine. Latest console for sftp connection gives:
29/10/2008 16:36:29 ExpanDrive[1502] Traceback (most recent call last):
29/10/2008 16:36:29 ExpanDrive[1502] File "/expandrive/ExpanDrive.py", line 9, in <module>
29/10/2008 16:36:29 ExpanDrive[1502] File "/expandrive/pyfuse/fuse.py", line 26, in </module><module>
29/10/2008 16:36:29 ExpanDrive[1502] ImportError: dlopen(/Applications/ExpanDrive.app/Contents/ExpanDrive/pyfuse/fuseparts/_fusemodule.so, 2): Library not loaded: /usr/local/lib/libfuse.0.dylib
Referenced from: /Applications/ExpanDrive.app/Contents/ExpanDrive/pyfuse/fuseparts/_fusemodule.so
Reason: image not found
</module>
Trying
ls /usr/local/lib/libfuse*
gives nothing. Is there some libraries I need to install? Any ideas?
I’m frustrated
-
Inappropriate?Well downloaded MacFUSE 1.7 from googlecode, and two out of the three are suddenly working...
I’m happy
-
Inappropriate?I just upgraded to 1.3.2b3 and now get this
10/29/2008 29 Oct 11:36:47 ExpanDrive[397] EXPANDRIVE_CONNECT_PROGRESS:drive_connected
10/29/2008 29 Oct 11:36:47 ExpanDrive[397] EXPANDRIVE_MKDIR_MOUNTPOINT:/Volumes/limelight
10/29/2008 29 Oct 11:36:47 ExpanDrive[397] Traceback (most recent call last):
10/29/2008 29 Oct 11:36:47 ExpanDrive[397] File "/expandrive/fs/ftpfs/Driver.py", line 264, in <module>
File "/expandrive/fs/ftpfs/Driver.py", line 250, in main
File "/expandrive/fs/ftpfs/Driver.py", line 215, in start_ftpfs
File "/expandrive/fs/fstools/fuse.py", line 367, in __init__
File "/expandrive/fs/fstools/fuse.py", line 418, in get_library
10/29/2008 29 Oct 11:36:47 ExpanDrive[397] File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 340, in __init__
OSError: dlopen(/usr/local/lib/libfuse.dylib, 6): Symbol not found: _iconv
Referenced from: /usr/local/lib/libfuse.dylib
Expected in: flat namespace
</module>
I’m stumped
2 Comments Add a comment
This solves the problem
-
And I don't have MacFuse installed anymore
-
Jan, if you don’t have MacFUSE installed then ExpanDrive should prompt you to install it when it starts. Is this not happening?
-
Inappropriate?Turns out that the kernel extension is still loaded ...
> kextstat | grep fuse
125 0 0x81260000 0x12000 0x11000 com.google.filesystems.fusefs (1.7.1) <7>
can't get rid of it ... don't want to reboot ... help ...1 Comment Add a comment
This solves the problem
-
You shouldn’t have to reboot. OS X can’t unload the kext if an application is still using it. Make sure that you’ve quite ExpanDrive. If ExpanDrive crashed, then it’s possible that you still have “zombie” processes running in the background. You can find and kill these in Activity Monitor, where they’ll be called “expandrive”. If that still doesn’t do it, then some programs besides ExpanDrive also use MacFUSE, such as Parallels.
-
Inappropriate?Reinstalled MacFUSE via the ExpanDrive launch and I still get the same error message
10/29/2008 29 Oct 12:40:44 ExpanDrive[1688] EXPANDRIVE_CONNECT_PROGRESS:drive_connected
10/29/2008 29 Oct 12:40:44 ExpanDrive[1688] EXPANDRIVE_MKDIR_MOUNTPOINT:/Volumes/limelight 3
10/29/2008 29 Oct 12:40:44 ExpanDrive[1688] Traceback (most recent call last):
10/29/2008 29 Oct 12:40:44 ExpanDrive[1688] File "/expandrive/fs/ftpfs/Driver.py", line 264, in <module>
File "/expandrive/fs/ftpfs/Driver.py", line 250, in main
File "/expandrive/fs/ftpfs/Driver.py", line 215, in start_ftpfs
File "/expandrive/fs/fstools/fuse.py", line 367, in __init__
File "/expandrive/fs/fstools/fuse.py", line 418, in get_library
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 340, in __init__
OSError: dlopen(/usr/local/lib/libfuse.dylib, 6): Symbol not found: _iconv
Referenced from: /usr/local
> find /usr/local/lib -name libfuse\* -ls
27870782 8 lrwxr-xr-x 1 root jhm 15 Oct 29 12:40 /usr/local/lib/libfuse.0.0.0.dylib -> libfuse.0.dylib
27870783 616 -rwxr-xr-x 1 root wheel 314816 Jun 30 13:40 /usr/local/lib/libfuse.0.dylib
27870784 2024 -rw-r--r-- 1 root wheel 1035888 Jun 30 13:40 /usr/local/lib/libfuse.a
27870785 8 lrwxr-xr-x 1 root jhm 15 Oct 29 12:40 /usr/local/lib/libfuse.dylib -> libfuse.0.dylib
27870786 8 -rwxr-xr-x 1 root wheel 804 Jun 30 13:40 /usr/local/lib/libfuse.la
</module>1 Comment Add a comment
This solves the problem
-
Hi Jan. This must be really frustrating, I’m sorry you’re having this trouble.
The ownership of /usr/local/lib/libfuse.0.0.0.dylib and /usr/local/lib/libfuse.dylib doesn’t look right. They should be owned by root:wheel, just like everything else in libfuse.
If you haven’t already tried this, you could try manually uninstalling MacFUSE, and then reinstall it. I think that the pkg installer has trouble when it wants to copy onto files that already exist hand have the wrong permissions or ownership. If you uninstall macfuse first, then you should be able to get a totally clean installation. For good measure, you could also run “sudo rm -fr /usr/local/lib/libfuse.*"
You can uninstall macfuse manual by running “sudo /Library/Filesystems/fusefs.fs/Support/uninstall-macfuse-core.sh” at the command line. Then you can reinstall macfuse, or let ExpanDrive do it for you. -
Inappropriate?I deleted everything and re-installed it from scratch, but no difference. Error message is the same.1 Comment Add a comment
This solves the problem
-
Ugh - Sorry! Thanks for not totally giving up on us [I'm sure you're close]
You said you deleted everything, did you manually sudo rm -fr /usr/local/lib/libfuse.* too?
Have you any success using SSHFS from the MacFUSE distribution?
http://code.google.com/p/macfuse/down... -
Inappropriate?It seems like something has broken iconv in your system
two things to try
check the output of
ls -al | grep '.*iconv.*'
while you're in /usr/lib
mine looks like:
lrwxr-xr-x 1 root wheel 16B Feb 27 2008 libiconv.2.4.0.dylib@ -> libiconv.2.dylib
-rw-r--r-- 1 root wheel 4.0M Sep 23 2007 libiconv.2.dylib
lrwxr-xr-x 1 root wheel 20B Feb 27 2008 libiconv.dylib@ -> libiconv.2.4.0.dylib
-rw-r--r-- 1 root wheel 795B Feb 19 2008 libiconv.la
then try
for arch in i386 ppc7400 x86_64 ppc64; do echo $arch; nm -arch $arch libiconv.2.4.0.dylib | grep '.*iconv.*'; done
mine looks like
i386
libiconv.2.4.0.dylib(single module):
000f5020 D __libiconv_version
0000b892 T _iconv
0001582e T _iconv_canonicalize
0000b8e8 T _iconv_close
000150bd T _iconv_open
0000b8fd T _iconvctl
0000baef T _iconvlist
0000bc8d T _libiconv
0000fe45 T _libiconv_close
00015825 T _libiconv_open
00015fd6 T _libiconv_relocate
00015fc7 T _libiconv_set_relocation_prefix
0000bc96 T _libiconvctl
0000bc9f T _libiconvlist
ppc7400
libiconv.2.4.0.dylib(single module):
000f7004 D __libiconv_version
0000da28 T _iconv
00018d4c T _iconv_canonicalize
0000da70 T _iconv_close
0001854c T _iconv_open
0000da94 T _iconvctl
0000dce4 T _iconvlist
0000de7c T _libiconv
000129e4 T _libiconv_close
00018d48 T _libiconv_open
00019498 T _libiconv_relocate
00019494 T _libiconv_set_relocation_prefix
0000de80 T _libiconvctl
0000de84 T _libiconvlist
x86_64
00000000000f90e0 D __libiconv_version
000000000000b45c T _iconv
00000000000151ff T _iconv_canonicalize
000000000000b48f T _iconv_close
0000000000014b24 T _iconv_open
000000000000b49c T _iconvctl
000000000000b658 T _iconvlist
0000000000015972 T _libiconv_relocate
0000000000015968 T _libiconv_set_relocation_prefix
ppc64
00000000000f8008 D __libiconv_version
000000000000dd9c T _iconv
0000000000019c04 T _iconv_canonicalize
000000000000dde4 T _iconv_close
0000000000019330 T _iconv_open
000000000000de08 T _iconvctl
000000000000e078 T _iconvlist
000000000001a43c T _libiconv_relocate
000000000001a438 T _libiconv_set_relocation_prefix
2 Comments Add a comment
This solves the problem
-
OK, so here is my /usr/local/lib
-rw-r--r-- 1 root jhm 986000 May 11 17:06 libiconv.2.4.0.dylib
lrwxr-xr-x 1 root jhm 20 May 11 17:06 libiconv.2.dylib@ -> libiconv.2.4.0.dylib
lrwxr-xr-x 1 root jhm 20 May 11 17:06 libiconv.dylib@ -> libiconv.2.4.0.dylib
-rw-r--r-- 1 root jhm 801 May 11 17:06 libiconv.la
and
> for arch in i386 ppc7400 x86_64 ppc64; do echo $arch; nm -arch $arch libiconv.2.4.0.dylib | grep '.*iconv.*'; done
i386
libiconv.2.4.0.dylib(single module):
000dd004 D __libiconv_version
00013f20 T _iconv_canonicalize
000132d0 T _libiconv
00013330 T _libiconv_close
00013710 T _libiconv_open
00014740 t _libiconv_relocate
00014650 T _libiconv_set_relocation_prefix
00013350 T _libiconvctl
00013590 T _libiconvlist
ppc7400
nm: file: libiconv.2.4.0.dylib does not contain architecture: ppc7400
x86_64
nm: file: libiconv.2.4.0.dylib does not contain architecture: x86_64
ppc64
nm: file: libiconv.2.4.0.dylib does not contain architecture: ppc64
I think we are getting somewhere :)
Where is this library coming from? (still don't know how to figure that out on Mac OS X - would know on solaris ...) -
So I'm more interested in what is in /usr/lib, rather than /usr/local/lib
Are you actually listing /usr/lib? [I would expect that is the case, because libfuse is in /usr/local/lib] -
Inappropriate?Fair enough :)
So /usr/lib/libiconv.2.4.0.dylib produces exactely the same result as you have. I removed /usr/local/lib/libiconv* and all is well.
I’m you fixed it
1 Comment Add a comment
This solves the problem
-
We fixed it! WOHOO! I was having my doubts.
-
1 Comment Add a comment
This solves the problem
-
AH! Is it showing anything? Anything getting printed to console.app?
-
Inappropriate?It shows one file in the Finder window, but none of the subdirectories. Console doesn't complain
EMPLOYEE
EMPLOYEE
