FTP & SFTP

  • 27 Dec

    Uploading large files using FTP Multipart option

    Dear users,

    A while ago we received the folllowing support question:

    “I am having problem transfering a big file. The file is 959MB. We get the following error: Exception Error Control channel transfer error 114690.”

    We found out that error 11469 = No data is being transferred via control channel. We asked our FTP code supplier for advice. 

    “Looks like a timeout-related issue. Error 114690 (SB_FTPS_ERROR_CONTROL_CHANNEL_NO_DATA) is returned if no reply was received from the control channel where it was expected to come in.  According to the log, the server does not perform any activity after the file is being sent. I believe there may be a delay between the file is sent to the server and the actual response the server is sending back. This delay may originate, for example, from the server copying the uploaded file from a temporary location to its final destination. The solution is quite straightforward – instead of uploading the file as a whole, upload it in pieces. Please start with splitting the file into 100MB chunks and see how it goes.”

    And that is what we did in version ‘v2018.12.27.0’. The Multipart Upload option was added in the ‘File & Directory’ tab of the FTP destination.

    • Enabled this option using the ‘Use Multipart Upload’ checkbox.
    • Set the part size. Default is 102.400 KiByte (100 MiByte). The minimum is 5 MiByte.
    • Set the treshold size. Default is 512.000 KiByte (500 MiByte).

    So what does this mean. When a source filesize is 500 MiByte or higher then this file will be uploaded in parts (chunks) of 100 MiByte. So not as a whole but in parts. Each part will be appened at the FTP server side. We use the APPE (Append) FTP command to achieve this.

    A second option to achieve a multipart upload is using the COMB command (‘Use COMB’ checkbox). Important, not so many FTP servers support the COMB command (non RFC). The source file is send in segments and afterwards the FTP server will combine them when it receives the COMB command. We tested this using the trial version of Titan FTP server.

    Even better is when you combine this with the Retry option. So if one of the parts would fail during the FTP upload then it will retry to upload this part again (and not the whole file).

    Feedback would be much appreciated,

    Happy Holidays,

    Limagito Team

     

  • 03 Nov

    Domain Name System Security Extensions – DNSSEC

    Dear users,

    Regardins DNSSEC: https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions

    Since version 2018.11.2.0 we’ve added a DNS option tab to the SFTP Source and Destination Setup. This option let’s you override the system DNS. Reason that we’ve added this is security (suppose your system got hacked). This option let’s you firmly control the DNS requests. We’ve also added an option to use DNSSEC (“Use Security”). This is all new for us so feedback is more than welcome.

    Regards,

    Limagito Team

    By Limagito FTP & SFTP , ,
  • 04 Jun

    FTP Error Codes

    https://www.secureblackbox.com/kb/help/ref_err_ftperrorcodes.html

    Copyright www.secureblackbox.comValueDescription
    SB_FTPS_ERROR_CONTROL_CHANNEL_HANGUP114689 (0x1C001)Some servers hang up control channels if no information is sent or received within rather short time. Hence, on large file transfers, the code which reports successful operation completion (226/250) is not sent by the server. FTPS client returns SB_FTPS_ERROR_CONTROL_CHANNEL_HANGUP error code when the command channel hangs up, but when the session was gracefully closed by the server (i.e., file transfer was finished successfully).
    SB_FTPS_ERROR_CONTROL_CHANNEL_NO_DATA114690 (0x1C002)No data is being transferred via control channel.
    SB_FTPS_ERROR_UNACCEPTED_REPLY_CODE115713 (0x1C401)Unaccepted reply code. Such codes may be sent by servers when data connection closure was initiated on the client side.
    SB_FTPS_ERROR_INVALID_REPLY115714 (0x1C402)Invalid reply.
    SB_FTPS_ERROR_LOCAL_SOURCE_NOT_FILE116737 (0x1C801)Local source is not a file.
    SB_FTPS_ERROR_LOCAL_TARGET_NOT_FILE116738 (0x1C802)Local target is not a file.
    SB_FTPS_ERROR_RESUME_OFFSET_TOO_LARGE116739 (0x1C803)This error is fired when the it is impossible to resume data transfer (because resume offset is too large).
    SB_FTPS_ERROR_OPERATION_CRITERIA_NOT_MET116740 (0x1C804)The criteria for the requested operation is not met.
    SB_FTPS_ERROR_TIMES_NOT_SET116741 (0x1C805)The criteria for the requested operation is not met.
    By Limagito Error FTP & SFTP , ,
1 3 4 5 6 7 8 9