Your best friend for file transfer.

Fetch application logoFetch

Dropped Connection (28 posts)

  • Started 4 years ago by matt
  • Latest reply 3 years ago from Jim Matthews
  • matt Member

    Keep getting a dropped connection when uploading and downloading large files via FTP in excess of 1GB. I have been in contact with my ISP regarding this issue as I suspect there is some throttling going on. Also contacted the server admin and they recommended direct afp access through the finder and am doing a test now. Here are the transcript notes from Fetch after a drop:

    Fetch 5.3.1 (5D226) PowerPC running on Mac OS X 10.5.8 (9L30) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHED003-2Q2J-D331 T
    Connecting to 84.238.114.204 port 21 (Mac OS X firewall is allowing connections) (11/19/09 9:40:51 PM)
    Connected to 84.238.114.204 port 21 (11/19/09 9:40:51 PM)
    220 superfiles FTP server ready.
    USER propellerhead
    331 Password required for propellerhead.
    PASS
    230 User propellerhead logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 MACB ENABLE: command not understood.
    CWD propheadz/PORCELAIN_FINAL/
    250 CWD command successful.
    PWD
    257 "/propheadz/PORCELAIN_FINAL" is current directory.
    Retrieved 6 items from file list cache, stored 11/19/2009 09:25 PM
    TYPE I
    200 Type set to I.
    SIZE PORCELAIN_PIRATES.toast
    213 11561205760
    MDTM PORCELAIN_PIRATES.toast
    213 20091012130321
    PASV
    227 Entering Passive Mode (84,238,114,204,216,248)
    Making data connection to 84.238.114.204 port 55544
    RETR PORCELAIN_PIRATES.toast
    150 Opening BINARY mode data connection for 'PORCELAIN_PIRATES.toast' (11561205760 bytes).
    Update check skipped at 11/19/2009 09:42 PM (next check after 11/20/2009 02:23 PM)
    Unsuccessful transfer of PORCELAIN_PIRATES.toast (1,056,095,024/11,561,205,760 bytes, 293,278 bytes/sec, 1:00:01 elapsed) stopped at 11/19/09 10:41:13 PM (error: 2,-30014)
    ftp_retrieve: 2,-30014 (state == RGET_RETRIEVING)

    Posted 4 years ago #

  • Eric Colvin Member

    5.5.3 on PPC 10.5.8

    Same exact problem that Matt described above. I too contacted my ISP, and have since downloaded Cyberduck and it's working fine.

    Something is definitely not right with Fetch. Long time, happy user by the way…

    Posted 4 years ago #

  • matt Member

    Just an FYI. I am having the same problem with Cyberduck as well as via Firefox browser. AFP has been working so far without any disconnects.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    Could you please give Fetch 5.5.3 a try and see if it helps? I believe you should definitely see an improvement with uploading, and it may well help with the downloading problems as well.

    Let us know if that makes a difference.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Eric,

    Is this a new problem that you started experiencing just after the upgrade to Fetch 5.5.3?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Eric Colvin Member

    Yes, this seems new to 5.5.3, but then again, I have not downloaded anything larger than 500GB in quite a while.

    I was dealing with a 7.59GB, 7.59GB and 5GB batch that simply kept booting me off after each approximate increment of 1GB.

    As I mentioned, Cyberduck is chugging away. It's completed 6.2GB out of a 12.9GB download.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Eric,

    Okay, so, it sounds like we can't really say if your problem is new to 5.5.3 or not. (It sounds like you and Matt may be experiencing different problems.)

    Actually, you don't need to do a new test with Fetch to get the transcript. Could you please send us your Fetch.log instead? That should have the info we need to get started looking into this.

    To find the Fetch.log file:

    * Click the desktop background to select the Finder.
    * Choose "Home" from the Go menu in the Finder
    * Open the Library folder
    * Open the Logs folder
    * Find the file named "Fetch.log"

    Please attach it to an email to bugs@fetchsoftworks.com .

    Since the file may be large, you might want to compress (zip) it before sending it to us.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • matt Member

    Thats strange. I thought I was using 5.5.3 but it only updated to 5.3.1 yesterday. Will try the new version and see how it goes.

    m.

    Posted 4 years ago #

  • matt Member

    Still happening with 5.5.3:

    Fetch 5.5.3 (5E778) PowerPC running on Mac OS X 10.5.8 (9L30) PowerPC English
    StuffIt Engine 0x820, StuffIt SDK Version 10.1.1b1
    Partial serial FETCHED003-2Q2J-D331 T
    Connecting to 84.238.114.204 port 21 (Mac OS X firewall is allowing connections) (11/20/09 4:02 PM)
    Connected to 84.238.114.204 port 21 (11/20/09 4:02 PM)
    220 superfiles FTP server ready.
    USER propellerhead
    331 Password required for propellerhead.
    PASS
    230 User propellerhead logged in.
    SYST
    215 UNIX Type: L8
    PWD
    257 "/" is current directory.
    MACB ENABLE
    500 MACB ENABLE: command not understood.
    CWD propheadz/PORCELAIN_FINAL/
    250 CWD command successful.
    PWD
    257 "/propheadz/PORCELAIN_FINAL" is current directory.
    Retrieved 6 items from file list cache, stored 11/20/09 11:34 AM
    TYPE I
    200 Type set to I.
    SIZE PORCELAIN_PIRATES.toast
    213 11561205760
    MDTM PORCELAIN_PIRATES.toast
    213 20091012130321
    PASV
    227 Entering Passive Mode (84,238,114,204,217,50)
    Making data connection to 84.238.114.204 port 55602
    RETR PORCELAIN_PIRATES.toast
    150 Opening BINARY mode data connection for 'PORCELAIN_PIRATES.toast' (11561205760 bytes).
    Update check skipped at 11/20/09 4:04 PM (next check after 11/21/09 9:03 AM)
    Unsuccessful transfer of PORCELAIN_PIRATES.toast as binary data (1,027,708,248/11,561,205,760 bytes, 285,395 bytes/sec, 1:00:01 elapsed) stopped at 11/20/09 5:03 PM (error: 2,-30014)
    ftp_retrieve: 2,-30014 (state == RGET_RETRIEVING)

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    Thanks for trying Fetch 5.5.3 and sending the followup transcript.

    Just to make sure I understand correctly - when you said "AFP has been working so far without any disconnects," you have connected to the server using the AFP protocal in the Finder, not using FTP in the Finder? (The Finder does have limited read-only FTP capabilities.)

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Eric,

    Thanks for sending the Fetch.log file; I have asked one of my colleagues to look at it and one of us will get back to you.

    Scott McGuire
    Fetch Softworks

    Edited 4 years ago #

  • Eric Colvin Member

    Thanks Scott.

    FWIW, Cyberduck had no problems with the download.

    Posted 4 years ago #

  • matt Member

    Hey Scott. Yes I am connecting to the server using the AFP protocal in the Finder. I am not using FTP in the Finder. So far, I have been resuming the file transfer in Fetch manually and I have been able to download around 6GB but am still getting disconnected every couple hours or so.

    Matt.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    AFP and FTP are completely different ways of communicating and transferring files between two computers, and the server is running two different pieces of software to do each kind (AFP or FTP) of transfers.

    My guess is that either the server's FTP software has some limitation that results in the dropped FTP connections after about 1 GB of downloading, and the server's AFP software doesn't have that limitation; or that perhaps one of your pieces of network equipment (either your router/wireless base station or the modem) has some flaw that causes long FTP transfers to be dropped, but not AFP transfers. We have definitely seen routers that drop FTP connections after certain amounts of time, even when they do not drop other kinds of connections.

    It's hard to say which is the case here; if you experience this problem when downloading large files via FTP from other servers, it's probably your network equipment. If it only happens with this one server, then it's probably something on the server's end. Since it happens with multiple FTP clients, though, I don't think it's a problem with Fetch or the other FTP clients.

    You might want to see if the server supports transferring files via SFTP instead of FTP (Fetch supports both); often SFTP does not have this sort of problem when FTP does. The other alternatives are to continue to use AFP for this one particular server, or continue to use Fetch's resume download feature.

    I hope that clarifies things, please let us know if you have further questions.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Scott McGuire Administrator

    We've looked into this and we believe we have found and fixed the problem that was causing Eric's dropped connections.

    Matt, we have also made changes that we believe will help with your dropped connections as well. If you're still having those problems, could you please send us an email at bugs@fetchsoftworks.com and we'll give you something to try?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Dick Member

    I am no longer able to download from a Crush 5 site using Fetch 5.5.3 (5E778) Intel running on iMac OS X 10.6.2 and had to change over to Transmit that works.

    I can connect, can upload and delete files, but cannot download anything (small or large)

    The Fetch transcript always ends the same with

    Unsuccessful transfer of AD4PU.jpg (0/131,088 bytes, 0 bytes/sec, 0:30 elapsed) stopped at 12/10/09 1:06 PM (error: 2,-30036)
    ftp_retrieve: 2,-30036 (state == RGET_RETRIEVING)

    I used to be able to download from the site with Fetch.

    Guess I will just have to use Transmit until the Fetch issue is resolved.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Dick,

    Sorry to hear you're having problems, we'll see if we can fix the problems.

    Did this problem start as soon as you upgraded to Fetch 5.5.3? If so, do you know which version of Fetch you were using before that?

    Or have you been using Fetch 5.5.3 successfully with this server, and it suddenly stopped working?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Dick Member

    Scott,

    I am not sure but I think it started after I upgraded to 5.5.3. The (state == RGET_RETRIEVING)
    seems happen only when attempting a download from a Crush 5. What is weird is I can upload
    but cannot download.

    As a workaround I can download using the Crush web page interface. Fetch used to work
    with Crush and for reasons I do not understand it no longer works. Fails 100% of the time.

    Dick

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Dick,

    Thanks for the additional information.

    I have tried Fetch 5.5.3 with a test CrushFTP server and had no problem downloading from it, so this does not appear to be a general problem with Fetch 5.5.3; but it could be that the server I tried is running a different version of the software or different settings than the server you tried.

    We'd like to see your entire transcript from an attempt to download (this will give us additional information about Fetch's interaction with the server). Could you please do the following?

    * Quit Fetch, if it's running.
    * Open Fetch again.
    * Connect to the problem server.
    * Try downloading again.
    * After you receive the error, go to the Window menu, and choose Fetch Transcript.
    * Copy the entire contents of the transcript window, and paste them into an email to bugs@fetchsoftworks.com .

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Dick Member

    The requested information has been sent. I hope it helps

    Good luck

    Dick

    Posted 4 years ago #

  • Dick Member

    Scott,

    You are The Man!

    The following email tip from you did the trick and Fetch 5.5.3
    now works perfect with the Crush 5 server.

    Thank you very much

    Dick

    Note from Scott:

    * Close any open connection to the server.
    * Go the Fetch menu, and choose Preferences.
    * Click the Obscure tab.
    * Check the "Do not send MACB probe" checkbox.
    * Connect to the server again.
    * Try downloading.

    Does that make a difference?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Dick,

    You're welcome, I'm glad to hear that fixed the problem.

    Please let us know if you have any further questions.

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Sean Member

    I'm a tv producer needing to upload large files, 5GB+ to an FTP server at our post production house. I'm really getting frustrated by the fact that my uploads keep having the server drop the connection. I can do a "put" and "resume" but I'm sick of baby sitting this. Is there any automatic resume after it fails option?

    Posted 3 years ago #

  • Scott McGuire Administrator

    Hi Sean,

    Yes, our current version of Fetch, version 5.6, will automatically resume failed or stalled uploads and downloads.

    If you're already using Fetch 5.6 and that's not happening for you, let us know and we'll investigate and try to find out why the automatic resume isn't working for you.

    Otherwise, please give Fetch 5.6 a try and see if that helps.

    Please note that Fetch 5.6 may not be a free upgrade for you. It is free to users who purchased Fetch on or after January 29, 2009; otherwise, it costs $10. For more details about upgrading, see http://fetchsoftworks.com/fetch/upgrade .

    You can learn what else is new in Fetch 5.6 by visiting http://fetchsoftworks.com/fetch/update/info/fetch-5.6

    However, you can try Fetch 5.6 free for 15 days, and if it fixes the problems, we hope you'll consider upgrading.

    If Fetch 5.6 doesn't help with your upload problems, or if you have additional questions, please let us know.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 3 years ago #

  • Sean Member

    Thank you Scott for your kind and thorough reply. I will purchase 5.6 right away. I'm assuming "auto-resume" is an option I can select in 5.6 correct?

    Posted 3 years ago #

  • Scott McGuire Administrator

    Hi Sean,

    You're welcome.

    No, there's no option you need to turn on - Fetch 5.6 does auto resume, er, automatically. :-) That is, it will always try to auto resume when necessary.

    Let us know how it goes!

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 3 years ago #

  • Reid Member

    Hello,

    I know this is an old post but I am currently experiencing problems similar to this thread. I am trying to upload a 2.64 gig file to our servers with Fetch 5.6. This morning when I first tried it, it would stall, stop, and then continue on its merry way. It got to 1.81 gigs before it stalled, stopped, and restarted! My heart sank but I let it go, but unfortunately this problem has gotten worse all day. I have been doing Put, Resume, over and over, (I didnt know about that until after I deleted the 1.8 gig file and started over...) but now it can barely go 100mb without stalling and restarting and its going no where. Is there a way to make Fetch resume the file automatically instead of restart?

    Another question I have is what are these .pureftpd-upload.... files? I think they are my big file in mid upload but it has a different name than the file I am trying to Put. Whats strange is sometimes the file I am uploading will appear in the file list as a smaller file size as well. Can I Put, Resume these .pureftpd files even though the file name is different than my original file Im trying to upload?

    Here is the copy of Log file when it stalls, stops, and restarts: (I can send you the whole thing if you want)

    250 OK. Current directory is /public_html/bs-sfn2/pool
    TYPE I
    200 TYPE is now 8-bit binary
    SIZE sha1-4DDB495FAEF0736BA3D32DB0E9549FE44936CEAC
    550 Can't check for file existence
    PASV
    227 Entering Passive Mode (74,220,215,79,102,68)
    Making data connection to 74.220.215.79 port 26180
    STOR sha1-4DDB495FAEF0736BA3D32DB0E9549FE44936CEAC
    150 Accepted data connection
    Upload of sha1-4DDB495FAEF0736BA3D32DB0E9549FE44936CEAC stalled with 162987904 bytes transferred, tw->ftp_store_high_water_mark == 118640648 (state == PUT_SENDING)
    Unsuccessful upload of sha1-4DDB495FAEF0736BA3D32DB0E9549FE44936CEAC as binary data (162,987,904/2,639,484,557 bytes, 545,110 bytes/sec, 4:59 elapsed) stopped at 7/25/11 4:10 PM (error: 2,-30036)
    retry_failed_operation derr = 2, -30036 retry_state = PUT_SETTING_UP cancel_cur_cmd = 1 force_reconnect = 0 tw->retry_reconnect_count = 1 making_progress = 1, tw->retry_count = 0
    Upload of sha1-4DDB495FAEF0736BA3D32DB0E9549FE44936CEAC stalled, retrying
    ABOR
    ftp_abort: 2,-30014 (state == RETRY_CANCELING)
    Connecting to yorgo.org port 21 (Mac OS X firewall is allowing connections) (7/25/11 4:10 PM)
    Connected to 74.220.215.79 port 21 (7/25/11 4:10 PM)

    As some background, the file I am trying to upload is an SHA1, Unix Exicutable File. It has to be transferred in Binary, which is great because it can be Resumed. I have called my ISP and we are paying for increased upload speeds and have been guaranteed there is no throttling or stopping of our connections. We have called our web host and they told us that while its uncommon for people to want to upload such large files to their servers they do not limit uploads in any way. I have so far used 4 different FTP programs and not one has worked. Fetch has however gotten the farthest of them all. Is Fetch The One? Any help would be so greatly appreciated!!!

    Thank you so much for reading this super long post.

    Best,
    -Reid

    Posted 3 years ago #

  • Jim Matthews Administrator

    Hi Reid,

    Thanks for reporting this problem. My guess is that you are out of space on the server. One reason might be that the FTP server creates temporary files with names that start ".pureftpd-upload", and they can be left around after a failed upload, taking up space.

    So the first thing I would try is deleting any files you don't need, including the .pureftpd files. If you get a permission error trying to delete those, contact the server administrator for help. And verify that there is room in your account for a 2.6GB upload.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 3 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.