Your best friend for file transfer.

Fetch application logoFetch

Errors on large file upload (6 posts)

  • Started 8 years ago by Sensei
  • Latest reply 8 years ago from Jim Matthews
  • Sensei Member

    When uploading a 166MB zip archive to a Rumpus server, I get the following errors at the very end of the upload:

    (error: -30000)
    ftp_store_close: -30000 (state == RPUT_CLOSING)

    What does that mean? Here's the full transcript:

    Connecting to ftp.myserver.com port 21 (OS X firewall is off) (11/16/06 12:32:11 PM)
    Connected to 72.37.###.## port 21 (11/16/06 12:32:12 PM)
    220-Your login to the ftp server was successful.
    220 Service ready for new user
    USER myUsername
    331 Password required
    PASS
    230 User logged in
    SYST
    215 MACOS Peter's Server
    PWD
    257 "/" is current directory.
    MACB ENABLE
    200 MacBinary enabled
    CWD Admin_Test_Folder
    250 CWD command successful
    PWD
    257 "/Admin_Test_Folder/" is current directory.
    TYPE A
    200 Type set to A (ASCII)
    PASV
    227 Entering Passive Mode (72,##,###,##,11,185)
    LIST
    150 Opening connection
    drwxr-xr-x folder 0 Nov 13 18:10 Files_for_website
    226 Transfer complete
    PWD
    257 "/Admin_Test_Folder/" is current directory.
    PWD
    257 "/Admin_Test_Folder/" is current directory.
    TYPE I
    200 Type set to I (Image) [MACBINARY ENABLED]
    MACB DISABLE
    200 MacBinary Disabled
    PASV
    227 Entering Passive Mode (72,##,###,##,11,185)
    STOR myLargeFile.zip
    150 Opening connection
    PWD
    PWD
    PWD
    PWD
    500 Command not understood
    Unsuccessful transfer of Allstate Superdome orch.zip (174,552,507 bytes, 53,642 bytes/sec, 54:14 elapsed) stopped at 11/16/06 12:19:16 PM (error: -30000)
    ftp_store_close: -30000 (state == RPUT_CLOSING)
    ABOR
    426 Transfer aborted

    Thanks for your help.

    Posted 8 years ago #

  • Scott McGuire Administrator

    Hi,

    Could you check the following?

    * Open the Fetch Preferences
    * Click the Obscure tab
    * Make sure "Contact servers during long transfers" is unchecked.

    If it was checked, uncheck it, and try again. (That setting is known to cause this sort of problem with Rumpus. We are working on an update to fix this problem.)

    While Fetch does have a resume upload feature, you need to set the upload format to be Binary to use it with Rumpus servers. (You can set the upload format using the Remote > Format menu.) But since you did not have it set to that initially, you won't be able to use it to resume this particular upload - you'll have to start again, sorry. But you may want to switch to Binary for the retry, and then if it fails again, try resuming the upload. (Instructions can be found here.)

    Let us know if either of these helps solve the problem, or if you have further questions.

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 11-16-2006).]

    Posted 8 years ago #

  • Sensei Member

    Thanks for your reply. I unchecked "Contact servers..." and uploaded it again. Again the upload gets about 99.99% complete (0:00 remaining) and then it stops. The 0:00 changes to "stalled", and the upload never fully completes. When I refresh the listing, I can see the file on the server, but without a clean 'upload complete' resolution, will there be bits missing in the uploaded file or something?
    Fetch is behind a NAT router, so I'm using PASV. Rumpus is also behind a NAT router, but the same problem happened when Rumpus was in the DMZ last month. Rumpus tech support swears there's nothing on the server side that would cause this hang. Do you have any other suggestions?

    Posted 8 years ago #

  • Jim Matthews Administrator

    You might compare the exact length of the original file on your Mac (e.g. with the Get Info command in the Finder) to the length of the file on the server (with Get Info in Fetch). If they match then the file is all there.

    I would recommend unchecking "Contact server during long transfers" in the Obscure section of Fetch Preferences.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 8 years ago #

  • Sensei Member

    Something odd I noticed in the Fetch transcript: Even though I have definitely set Fetch to upload using "BINARY (RAW DATA)" mode, in the transcript it says ASCII and MACBINARY:

    TYPE A
    200 Type set to A (ASCII)

    200 Type set to I (Image) [MACBINARY ENABLED]
    MACB DISABLE
    200 MacBinary Disabled
    PASV
    227 Entering Passive Mode (67,38,###,###,11,185)
    STOR TestUpload.zip

    It's my understanding that Binary transfers result in exact byte-for-byte copies, but ASCII transfers may alter files (change line endings, e.g.) Therefore I want to upload these large .zip files specifically in BINARY mode (not Mac Binary, not ASCII). Do you need the full transcript to troubleshoot this? Thanks for your help

    Posted 8 years ago #

  • Jim Matthews Administrator

    The .zip files are being uploaded in Binary format. The mention of TYPE A (ASCII) you see is because Fetch uses ASCII mode to download the file list; it later switches to TYPE I (i.e. binary) for the actual file transfer. The MACB DISABLE command you see disables MacBinary mode, so the transfer is not in MacBinary mode.

    Thanks,

    Jim Matthews
    Fetch Softworks

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