Your best friend for file transfer.

Fetch application logoFetch

Upload stalls / restarts for large files (9 posts)

  • Started 4 years ago by bjudson
  • Latest reply 4 years ago from Scott McGuire
  • bjudson Member

    Hi - I've looked through the message boards and see similar but not identical problems. I have been trying to upload some fairly large MySQL dump files to my web host (17 and 35 mb respectively), and each time Fetch stalls at the very end of the file and automatically restarts the transfer from the beginning. I am using version 5.5.1. I successfully uploaded the smaller file with Coda's FTP feature, so I'm fairly certain this isn't an issue with the hosting server.

    The automatic restart is frustrating because it keeps me from checking the partially uploaded file -- pretty much as soon as it stalls, Fetch attempts to re-upload the file, so the partial upload is deleted.

    Here's a sample transcript:

    Unsuccessful transfer of database.mysql as text file (18,137,108/18,590,535 bytes, 13,424 bytes/sec, 22:31 elapsed) stopped at 9/1/09 10:19 AM (error: 2,-30036)
    ftp_store: 2,-30036 (state == RPUT_CLOSING)
    retry_failed_operation derr = 2, -30036 retry_state = RPUT_SETTING_UP cancel_cur_cmd = 1 force_reconnect = 0 tw->retry_reconnect_count = 0 making_progress = 0, tw->retry_count = 0
    Upload of database.mysql stalled, retrying
    tw->ftp_store_retry_resume_upload = 0 tw->binary_xfer = 0 tw->macbin_xfer = 0 tw->stou_xfer = 0 7579

    Posted 4 years ago #

  • Jim Matthews Administrator

    Hi,

    Thanks for reporting this problem. I'd be interested in seeing the complete transcript -- could you send it to mailto:bugs@fetchsoftworks.com ?

    Also, do you notice whether Coda stalls for a while at the end of its uploads?

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 4 years ago #

  • bjudson Member

    I just uploaded the other file with Coda, this one does seem to have been successful as well. Unfortunately I got pulled away from my computer near the end, so I couldn't tell if it stalled at the end of the upload or not. Coda's transcripts are much less detailed than Fetch's, so that won't be much help either. I emailed the full Fetch transcript.

    Posted 4 years ago #

  • Jim Matthews Administrator

    Apparently Fetch is uploading the .mysql file as a text file. Have you tried uploading it in Binary (Raw Data) format?

    Posted 4 years ago #

  • bjudson Member

    I haven't, but I did try uploading some smaller .mysql files using the default settings, and they worked fine. Since I figured out I could upload the larger ones with Coda, this isn't such a pressing issue for me anymore, but when I get a chance I'll try uploading one of these files in binary format to see what happens.

    Thanks.

    Posted 4 years ago #

  • Brett Member

    I am having the same problems this user reported. I am uploading a large (600+ MB) .zip file and it stalls out and then restarts. I have emailed the transcript to bugs@fetchsoftworks.com.

    Posted 4 years ago #

  • bjudson Member

    This is a reply I received from the Fetch folks about this problem:

    It may be that this host takes a while to finish uploads, and that Fetch is too quick to consider the transfers stalled. You can adjust the timeout Fetch uses by giving this command in Terminal:

    defaults write com.fetchsoftworks.Fetch StallTimeout -int 60

    Posted 4 years ago #

  • Brett Member

    @bjudson: thanks for the info. so changing the number from 60 to 180 would increase the timeout to 3 hours?

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Brett,

    We received the transcript you sent, and we'll look into it and let you know our thoughts.

    Regarding the command line command bjudson mentioned, no, that changes the timeout from to 180 seconds (3 minutes). Note this is not the timeout for the entire transfer; it's how long Fetch waits before retrying an upload when it sees that no progress is being made. That is, normally, if you're in the middle of an upload and Fetch notices that no new data has been uploaded for 60 seconds, Fetch will stop the current transfer and try again. Changing the value means that Fetch will wait until there has been no data uploaded for 180 seconds before decided the transfer has stalled.

    I'm not sure it will help in your situation, but you can give it a try and let us know if it helps.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 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.