Fetch Softworks

FTP server disconnects me after exactly 1:00:59 (4 posts)

• Started 11 years ago by sheckylovejoy
• Latest reply 11 years ago from Jim Matthews

• sheckylovejoy Member

  I'm trying to locate the source of this problem, whether it's on my end or on the server-side. FWIW, this problem exists with all FTP clients, not just Fetch (v 5.7.1).

  I am uploading very large video files (~10GB) to the server for the cable network that is carrying the show. Every 1:00:59 EXACTLY, Fetch is forced to resume the upload. Here's the excerpted log

  200 Transfer mode set to BINARY
  PASV
  227 Entering Passive Mode (159,26,220,45,7,66).
  Making data connection to 159.26.220.45 port 1858
  STOR those_magnificent_mules_Ep3_HTTM003.MXF
  125 Uploading in BINARY file those_magnificent_mules_Ep3_HTTM003.MXF
  Upload of those_magnificent_mules_Ep3_HTTM003.MXF stalled with 708945752 bytes transferred, tw->ftp_store_high_water_mark == 0 (state == RPUT_SENDING)
  Unsuccessful upload of those_magnificent_mules_Ep3_HTTM003.MXF as binary data (708,945,752/9,969,577,820 bytes, 193,753 bytes/sec, 1:00:59 elapsed) stopped at 3/30/12 10:19 PM (error: 2,-30036)
  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 = 1, tw->retry_count = 0
  Upload of those_magnificent_mules_Ep3_HTTM003.MXF stalled, retrying
  ABOR
  send_cmd():con_conn->Putline() returns 2,-50
  ftp_abort: 2,-30014 (state == RETRY_CANCELING)
  Connecting to filetransfer.northstarstudios.tv port 21 (Mac OS X firewall is allowing connections) (3/30/12 10:19 PM)
  Connected to 159.26.220.45 port 21 (3/30/12 10:19 PM)
  220 nvnssftp1 X2 WS_FTP Server 7.5(00843750)
  USER rfd
  331 Enter password
  PASS
  230-User logged in
  Use of this system constitutes consent to security monitoring and testing. All activity is logged with your host name and IP address. Unathorized access to this system is a violation of federal law (18 u.s.c sec. 1030) and state law (Tennessee code section 39-14-602).
  230 User logged in
  SYST
  215 UNIX
  PWD
  257 "/users/MC/RFD" is current directory
  CWD /users/MC/RFD/Programs/Those Magnificent Mules/HTTM003 - Those Magnificent Mules
  250 Command CWD succeed
  TYPE I
  200 Transfer mode set to BINARY
  SIZE those_magnificent_mules_Ep3_HTTM003.MXF
  213 708876248
  PASV
  227 Entering Passive Mode (159,26,220,45,7,221).
  Making data connection to 159.26.220.45 port 2013
  REST 708876248
  350 Restart from 708876248
  STOR those_magnificent_mules_Ep3_HTTM003.MXF
  125 Uploading in BINARY file those_magnificent_mules_Ep3_HTTM003.MXF
  Upload of those_magnificent_mules_Ep3_HTTM003.MXF stalled with 1439139368 bytes transferred, tw->ftp_store_high_water_mark == 708945752 (state == RPUT_SENDING)
  Unsuccessful upload of those_magnificent_mules_Ep3_HTTM003.MXF as binary data (730,263,120/9,969,577,820 bytes, 199,579 bytes/sec, 1:00:59 elapsed) stopped at 3/30/12 11:20 PM (error: 2,-30036)
  retry_failed_operation derr = 2, -30036 retry_state = RPUT_SETTING_UP cancel_cur_cmd = 1 force_reconnect = 0 tw->retry_reconnect_count = 1 making_progress = 1, tw->retry_count = 0
  Upload of those_magnificent_mules_Ep3_HTTM003.MXF stalled, retrying
  ABOR
  send_cmd():con_conn->Putline() returns 2,-50
  ftp_abort: 2,-30014 (state == RETRY_CANCELING)
  Connecting to filetransfer.northstarstudios.tv port 21 (Mac OS X firewall is allowing connections) (3/30/12 11:20 PM)
  Connected to 159.26.220.45 port 21 (3/30/12 11:20 PM)
  220 nvnssftp1 X2 WS_FTP Server 7.5(71625000)
  USER rfd
  331 Enter password
  PASS
  230-User logged in
  Use of this system constitutes consent to security monitoring and testing. All activity is logged with your host name and IP address. Unathorized access to this system is a violation of federal law (18 u.s.c sec. 1030) and state law (Tennessee code section 39-14-602).
  230 User logged in
  SYST
  215 UNIX
  PWD
  257 "/users/MC/RFD" is current directory
  CWD /users/MC/RFD/Programs/Those Magnificent Mules/HTTM003 - Those Magnificent Mules
  250 Command CWD succeed
  TYPE I
  200 Transfer mode set to BINARY
  SIZE those_magnificent_mules_Ep3_HTTM003.MXF
  213 1439072760
  PASV
  227 Entering Passive Mode (159,26,220,45,8,98).
  Making data connection to 159.26.220.45 port 2146
  REST 1439072760
  350 Restart from 1439072760
  STOR those_magnificent_mules_Ep3_HTTM003.MXF
  125 Uploading in BINARY file those_magnificent_mules_Ep3_HTTM003.MXF
  Upload of those_magnificent_mules_Ep3_HTTM003.MXF stalled with 2290589568 bytes transferred, tw->ftp_store_high_water_mark == 1439139368 (state == RPUT_SENDING)
  Unsuccessful upload of those_magnificent_mules_Ep3_HTTM003.MXF as binary data (851,516,808/9,969,577,820 bytes, 232,718 bytes/sec, 1:00:59 elapsed) stopped at 3/31/12 12:21 AM (error: 2,-30036)
  retry_failed_operation derr = 2, -30036 retry_state = RPUT_SETTING_UP cancel_cur_cmd = 1 force_reconnect = 0 tw->retry_reconnect_count = 2 making_progress = 1, tw->retry_count = 0
  Upload of those_magnificent_mules_Ep3_HTTM003.MXF stalled, retrying
  ABOR
  send_cmd():con_conn->Putline() returns 2,-50
  ftp_abort: 2,-30014 (state == RETRY_CANCELING)

  etc

  Posted 11 years ago #

• Jim Matthews Administrator

  Hi,

  It looks like either the server or a router is dropping your connection to the server when there's been an hour go by without a new command (in this case because Fetch is transferring a file that takes more than one hour to transfer). You might try one of these transfers from a different location (if you have a laptop) to see if it's an issue with your router.

  The good news is that Fetch will notice the problem and automatically restart the transfer where it left off, so you should eventually get the whole file across.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 11 years ago #

• sheckylovejoy Member

  Is there any way to send a dummy command every 30 min or something?

  Posted 11 years ago #

• Jim Matthews Administrator

  The FTP protocol does not specify what should happen if a client (like Fetch) sends a command while a previous command is still being handled. And even doing that might not fix the problem; some servers drop connections after a certain period of time elapses without the client starting a new file transfer.

  The real fix is for the server and/or router to realize that data is still moving, and to not drop the connection. The next best thing is for the client to automatically restart, as Fetch does.

  Thanks,

  Jim Matthews
  Fetch Softworks

  Posted 11 years ago #