Fetch Softworks

File uploads keep stalling (11 posts)

• Started 7 years ago by John C
• Latest reply 6 years ago from Jim Matthews

• John C Member

  I am having trouble uploading files. I have been using Fetch for years with this particular web/ftp host and never had any trouble before. Fetch uploads a few files and then stalls, aborts and has to reconnect to continue uploading. It finishes eventually but takes a very long time, even with pretty small (~50kb) files. I have a lot of image files to upload, so this kind of stalling is not going to work. Transfers using the web host's built-in file manager work fine, but I'd rather use Fetch.

  Here is a part of the transcript showing two things: it switched to PASV mode after image 1950.jpg even though it started in PORT mode and I have unchecked the "use passive mode transfers" option (at the recommendation of my web host company); it aborts during upload of 1963.jpg, reconnects then completes the upload).

  PORT 10,20,56,27,236,58
  200 PORT command successful. Consider using PASV.
  STOR 1942.jpg
  150 Ok to send data.
  226 Transfer complete.
  MDTM 20160519180326 1942.jpg
  213 File modification time set.
  STAT 1942.jpg
  213-Status follows:
  -rw-r--r-- 1 515 515 2570829 May 19 18:03 1942.jpg
  213 End of status
  Successful upload of 1942.jpg as binary data (2,570,829 bytes, 642,707 bytes/sec, 0:04 elapsed) completed at 5/20/16 11:42 AM
  PWD
  257 "/html/images"
  PORT 10,20,56,27,236,157
  200 PORT command successful. Consider using PASV.
  STOR 1950.jpg
  150 Ok to send data.
  226 Transfer complete.
  MDTM 20160519180332 1950.jpg
  213 File modification time set.
  STAT 1950.jpg
  213-Status follows:
  -rw-r--r-- 1 515 515 2347452 May 19 18:03 1950.jpg
  213 End of status
  Successful upload of 1950.jpg as binary data (2,347,452 bytes, 586,863 bytes/sec, 0:04 elapsed) completed at 5/20/16 11:44 AM
  PASV
  227 Entering Passive Mode (205,153,119,8,39,29).
  Making data connection to 205.153.119.8 port 10013
  STOR 1952.jpg
  150 Ok to send data.
  226 Transfer complete.
  MDTM 20160519180332 1952.jpg
  213 File modification time set.
  STAT 1952.jpg
  213-Status follows:
  -rw-r--r-- 1 515 515 2435317 May 19 18:03 1952.jpg
  213 End of status
  Successful upload of 1952.jpg as binary data (2,435,317 bytes, 608,829 bytes/sec, 0:04 elapsed) completed at 5/20/16 11:44 AM
  PASV
  227 Entering Passive Mode (205,153,119,8,39,166).
  Making data connection to 205.153.119.8 port 10150
  STOR 1956.jpg
  150 Ok to send data.
  226 Transfer complete.
  MDTM 20160519180334 1956.jpg
  213 File modification time set.
  STAT 1956.jpg
  213-Status follows:
  -rw-r--r-- 1 515 515 2634719 May 19 18:03 1956.jpg
  213 End of status
  Successful upload of 1956.jpg as binary data (2,634,719 bytes, 658,679 bytes/sec, 0:04 elapsed) completed at 5/20/16 11:44 AM
  PASV
  227 Entering Passive Mode (205,153,119,8,40,143).
  Making data connection to 205.153.119.8 port 10383
  STOR 1958.jpg
  150 Ok to send data.
  226 Transfer complete.
  MDTM 20160519180334 1958.jpg
  213 File modification time set.
  STAT 1958.jpg
  213-Status follows:
  -rw-r--r-- 1 515 515 2535178 May 19 18:03 1958.jpg
  213 End of status
  Successful upload of 1958.jpg as binary data (2,535,178 bytes, 633,794 bytes/sec, 0:04 elapsed) completed at 5/20/16 11:44 AM
  PASV
  227 Entering Passive Mode (205,153,119,8,40,159).
  Making data connection to 205.153.119.8 port 10399
  STOR 1960.jpg
  150 Ok to send data.
  226 Transfer complete.
  MDTM 20160519180336 1960.jpg
  213 File modification time set.
  STAT 1960.jpg
  213-Status follows:
  -rw-r--r-- 1 515 515 2505609 May 19 18:03 1960.jpg
  213 End of status
  Successful upload of 1960.jpg as binary data (2,505,609 bytes, 626,402 bytes/sec, 0:04 elapsed) completed at 5/20/16 11:44 AM
  PASV
  227 Entering Passive Mode (205,153,119,8,39,138).
  Making data connection to 205.153.119.8 port 10122
  STOR 1963.jpg
  150 Ok to send data.
  Unsuccessful upload of 1963.jpg as binary data (3,019,684/3,019,684 bytes, 46,456 bytes/sec, 1:05 elapsed) stopped at 5/20/16 11:45 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 1963.jpg stalled, retrying
  ABOR
  FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 638453 reply_received = 638452 TickCount() - reply_received = 1
  FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 638453 reply_received = 638452 TickCount() - reply_received = 1
  FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 639352 reply_received = 638452 TickCount() - reply_received = 900
  FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 639352 reply_received = 638452 TickCount() - reply_received = 900
  FTP::ftp_abort() FTP_ABOR_SENT_CMD TickCount() = 639353 reply_received = 638452 TickCount() - reply_received = 901
  ftp_abort: 2,-30014 (state == RETRY_CANCELING)
  Connecting to ftp.auneherbarium.org port 21 (Mac OS X firewall is allowing connections) (5/20/16 11:46 AM)
  Connected to 205.153.119.8 port 21 (5/20/16 11:46 AM)
  220 FTP server ready. All transfers are logged.
  USER userweb63727
  331 Please specify the password.
  PASS
  230 Login successful.
  SYST
  215 UNIX Type: L8
  PWD
  257 "/"
  CWD /html/images
  250 Directory successfully changed.
  TYPE I
  200 Switching to Binary mode.
  SIZE 1963.jpg
  213 3019684
  Successful upload of 1963.jpg (declared successful because all 3,019,684 bytes are present) at 5/20/16 11:46 AM

  Thanks for any help you can provide.

  Posted 7 years ago #

• Jim Matthews Administrator

  Hi,

  Thanks for posting the transcript. I'm not sure why Fetch switches to PASV, but it looks like both PORT and PASV usually work to this server. You can disable that switching by quitting Fetch, opening Terminal, and entering:

  defaults write com.fetchsoftworks.Fetch UseDataConnectionMagic -bool false

  Let me know if you still see a problem when Fetch sticks to PORT.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 7 years ago #

• John C Member

  Hi Jim,

  Unfortunately that doesn't work. It doesn't matter whether it is in PORT or PASV mode. It still aborts after 2 or 3 uploads.

  Thanks,

  John

  Posted 7 years ago #

• Jim Matthews Administrator

  Hi,

  It isn't clear why the server would stop responding at the end of some uploads, and not others. You might ask the web host if there have been recent changes that might explain this new behavior.

  On the Fetch side you could change the stall timeout so that Fetch does not wait as long before retrying. For example, to have Fetch wait 20 seconds instead of 60 you would give the following command in Terminal:

  defaults write com.fetchsoftworks.Fetch StallTimeout -int 20

  Unfortunately I can't think of a Fetch settings change that would be likely to reduce the chances of the stall happening in the first place.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 7 years ago #

• John C Member

  Okay. Thank you for your help.

  John

  Posted 7 years ago #

• Steve D Member

  Hi John and Jim.

  I just posted the same issue ("Uploads only 1 file at a time, sloooowly"). Missed this on my scroll-through-topics. Glad to see this is not just me having this issue. It sounds like I need to call my host provider and investigate if something changed on their end. I'll keep this group updated of what I find out. In the meantime, @Jim, if you have any new insights or that you agree with my course of action, I'd certainly appreciate it.

  Cheers guys,
  Steve

  Posted 6 years ago #

• Steve D Member

  @Jim,

  Okay, I just talked to my hosting provider (www.aplus.net) and they corroborate the same — that their Mac users who use Fetch are all experiencing the same problems uploading. Apparently they started seeing a lot of traffic on the issue last Summer (2015). Did Fetch make some upgrades about that time? According to aplus.net, something broke with how Fetch works with their platform. Is Fetch aware of similar experiences with other hosts?

  As a paying user of Fetch, I'd like to request that the engineer team look into this, please. It may require working with the team at aplus.net (and/or other host providers with similar experiences) to address this issue.

  As of today, I only see John and I with this topic. Are there others on this board who are familiar with this issue?

  Jim, I really appreciate any feedback, solutions, thoughts you can provide.

  Thanks so much,
  Steve

  Posted 6 years ago #

• Jim Matthews Administrator

  Hi Steve D,

  I'd definitely like to look into this. I'm not aware of this problem affecting other hosts, but I can only base that on what has been reported to us.

  It would be ideal if I could reproduce the problem on my computer, so I could look more closely at the network traffic and figure out what is going on. I will sign up for an aplus.net hosting account and see if the problem affects me as well.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 6 years ago #

• Jim Matthews Administrator

  Hi Steve D,

  I just now saw your email message with the transcript. The problem is that your hosting company's FTP server has a bug. Fetch sends the command

  MDTM 20160613230951 sitemap.xml

  in an attempt to set the modification date of the file sitemap.xml. The server should either 1) Carry out the command or 2) Return an error to indicate that it does not support that command. Instead it drops the connection entirely!

  Checking that box in Preferences will keep Fetch from sending the command in the first place, and so should avoid this bug.

  It would be great if you could contact aplus.net and let them know about this bug in their server. Feel free to put me in touch with them directly as well.

  Note: this is a different problem from the one that John C is dealing with; unfortunately I don't have an easy solution for him at this time.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 6 years ago #

• John C Member

  HI Jim,

  This issue has been resolved. It must have been a problem at the web host server that has been fixed because it is working fine now. I don't know what was changed, but after many weeks of problems, now uploads are going without a hitch.

  Thank you for your help.

  John C

  Posted 6 years ago #

• Jim Matthews Administrator

  Glad to hear it!

  Jim Matthews
  Fetch Softworks

  Posted 6 years ago #