Release Notes: IBM Aspera Command-Line Interface 3.7.2
Release Notes: IBM Aspera Command-Line Interface 3.7.2

Release Notes: IBM Aspera Command-Line Interface 3.7.2

Product Release: January 24, 2017
Release Notes Updated: January 24, 2017

IBM Aspera Command-Line Interface (the Aspera CLI) is a collection of Aspera tools for performing high-speed, secure data transfers from the command line. The Aspera CLI is for users and organizations who want to automate their transfer workflows.

The Aspera CLI is comprised of three command-line programs:
  • aspera, a command-line client for performing transfers with Aspera Faspex and Aspera Shares transfer servers.
  • The ascp command-line FASP transfer program.
  • ascp4, or A4, a FASP transfer program similar to ascp that has been optimized for sending large sets of individual files and can support UDP multicast through Aspera FASPStream.
Note: This release of the Aspera CLI does not support the Shares Management API or the Faspex v4 API.

BREAKING CHANGES

If you are upgrading from a previous release, the following changes for this release may require you to adjust your workflow, configuration, or usage.

  • The Aspera CLI no longer creates a symlink to the aspera binary. Instead, add the Aspera CLI in your PATH:
    Linux:
    export PATH=~/.aspera/cli/bin:$PATH
    Mac OS X:
    export PATH=~/Applications/Aspera\ CLI/bin:$PATH
  • The man page for the aspera client is no longer automatically installed when you install the Aspera CLI. To install the man pages, run the following command:
    Linux:
    export MANPATH=~/.aspera/cli/share/man:$MANPATH
    Mac OS X:
    export MANPATH=~/Applications/Aspera\ CLI/share/man:$MANPATH

ISSUES FIXED IN THIS RELEASE

ACLI-5 - When you download from Shares, the system no longer reports incorrect exceptions about invalid cipher.

SYSTEM REQUIREMENTS

Linux 32- and 64 bit: The Aspera CLI is supported on all varieties of GNU Linux for Intel architectures, both 32- and 64-bit.

In the verification process, Aspera relies primarily these platforms:
  • Ubuntu 12-16
  • RedHat 6-7
  • CentOS 6-7
  • Fedora 16-20
  • Debian 6-7
  • SLES 11-12 Kernel 2.4 or higher

The Aspera CLI requires libc version GLIBC 2.5.

In order to install the Aspera CLI product package, your platform must include the tar utility.

Mac OS X: 10.7, 10.8, 10.9, 10.10, 10.11.

Windows: 2008r2, 2012, 7, 8, 10.

PACKAGE INFORMATION

Linux 32-bit (rpm): aspera-cli-3.7.2.354.010c3b8-linux-32-release.sh
md5: 00285827edcea61a36b6a455ec607328
sha1: dbba90d03332e15190815f5475bda042fd7ef5f8
Linux 64-bit (rpm): aspera-cli-3.7.2.354.010c3b8-linux-64-release.sh
md5: 02787ca46814fb9ae2de5c706461367e
sha1: 7fc50a3547490c0c2b3d779a41150ac77fed3007
Mac OS X: aspera-cli-3.7.2.354.010c3b8-mac-10.7-64-release.sh
md5: 7cd6d4133000c6f0b1f7a2ac04c1b006
sha1: ca1aef899e8d06ba62f4c2859f3ca67beebd4aa6
Windows: aspera-cli-3.7.2.354.010c3b8-win-v100-32-release.zip
md5: 7fa4f14b58bd1d1d528322d9c071e964
sha1: a70e464b17a1dff4786b1d0fd8ca4e41d4fbdc85

KNOWN ISSUES

Note: This release was developed using two different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.

aspera

ACLI-71 - [Mac OS X only] If you install the Aspera CLI to a location to which you lack permissions, the installation fails, but the installer nevertheless reports a successful installation.

ACLI-61 - [Windows only] When you specify a filepath using the %homepath% variable, the Aspera CLI action fails.

ACLI-48 - When you use the faspex list subcommand with the -x or --xml option for XML-formatted content, there is an issue with the formatting of the URLs that are returned. As a result, when you download the XML content with faspex get, the following error is returned:
Cannot parse an empty string
Workaround: Remove XML escape sequences (either manually or with an XML parser) from URLS before passing them as input to a faspex get subcommand.

ACLI-44 - When you specify the -b or --base-ca-path option with a filepath variable, the Aspera CLI fails to find the file or directory you specify.

ACLI-43 - When a Shares command is run on a share that the user does not have authorization for, the following error is returned:
JSON Exception: Error: Path not found
The error does not indicate that authorization is denied.
#35287 - Transfers from the local computer to the Azure default inbox fail with the following error:
Setting up FASP parameters... Invalid access: Cannot convert empty value.

#35520 - If your Faspex transfer specification includes a cipher (such as AES-128), the Aspera CLI ignores the cipher. Workaround: To avoid this issue, enable server-side encryption: specify the allowed_cipher parameter in the server-side aspera.conf file.

#35611 - The Faspex get command does not work with the --cipher= option. Workaround: To avoid this issue, enable server-side encryption.

ascp

ATT-205 - ascp transfer fails with an internal memory error if <network_rc><module> is set to air in the <bandwidth> section of aspera.conf.

ATT-185 - ascp does not reconnect to Redis db when asperanoded is restarted.

ATT-134 - [Windows, Linux]asdelete and ascp --delete-before-transfer commands initiated from Windows machines fail to delete files named with ASCII characters (< | ? * > : " \ ) on Linux machines.

ES-177 - The range_low value of a -@ argument is not respected.

ES-96 (#33091) - [Windows] Downloading files or folders that have names that end in a trailing space fail.

#35010 - If the source path in an ascp transfer is a file named \ , the file is not transferred and an error is generated, but the folder than contains the file and all other files in that folder are transferred.

#33094 - ascp delete-before-transfer does not support URI storage.

#32941 - Because pvcl does not support the --no-read --no-write option, ascp should fail transfers that use these options with pvcl. However, ascp ignores the options and continues the transfer.

#32890 - In a successful transfer from the client to the server, ascp fails to copy the metafile and thus it does not transfer with the data file.

#32680 - The option to create a directory (ascp -d) may create a directory at a destination before an expected session failure.

#32553 - When the FASP Session log source file list exceeds 500 bytes and contains multibyte UTF-8 characters, the output is truncated in a manner that creates an invalid UTF-8 sequence.

#31423 - It is possible for an ascp transfer of a file on a full disk to be reported as successful by both the sender and the receiver.

#30231 - [Windows] If a pre-post script includes a path that contains ".." and the client is running on Windows, ascp fails with the following message:
Cannot open -e pre-post command: Unknown error

#29043 - Under serious WAN impairment, Hot Folder push transfers with a prepost script intermittently report an asssh error approximately 10-15 seconds after Transfer Statistics are reported to the log. This delay in process shutdown can hold the handle to the file list such that subsequent ascp processes fail.

#28939 - If command line ascp neglects to specify a destination host, then the failed transfer (error: "no remote host specified") gets recorded in SQLite with client_node_id NULL, instead of being populated with the uuid of the node. This causes an issue with Console.

#25865 - Allowing symbolic links to be copied also allows access to locations outside the docroot.

A4

ES-151 - ascp4 does not recognize the UNC path docroot of a Console transfer user. (CIM-197)

ATT-238 - The log file does not rotate correctly if the log size is set to more than 2200 MB in aspera.conf.

ATT-208 - Symbolic links are copied when ascp4 is run with --symbolic-link=skip.

ATT-191 - [Linux] Symbolic links are not updated on the destination when the symbolic link option is follow (the default value if none is set) or copy.

ATT-181 - ascp4 returns the wrong error message if it fails because the specified remote logging directory is invalid.

ATT-44 - The timestamp of a parent directory transferred with ascp -p is not preserved, while the timestamps of the child files and directories are preserved.

ATT-37 - ascp4 hangs if a transfer exceeds the available space on the destination machine.

ATT-31 - ascp4 crashes following the transfer of a large (for example, 5 GB) file to S3 storage.

ATT-30 and ATT-46 - ascp4 transfer is slow when uploading many small files (for example, 1 million 4 byte files) to S3 storage.

ATT-29 - Files transferred to S3 storage using ascp4 retain a .partial extension when viewed in the GUI.

ATT-27 - Direct-to-cloud transfers using ascp4 are skipped unless the full destination path is specified.

ATT-2 (#32295) - The default minimum transfer rate is not picked up from aspera.conf.

#34322 - ascp fails to authenticate SHH with a large banner file size (approximately 2000 bytes) on CentOS 7.2.

#29613 (Windows) and ATT-44 (Linux) - Timestamps are not preserved on top-level directories.

#26484 - Proxy is not supported.

PRODUCT SUPPORT

For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.