Release Notes: IBM Aspera Command-Line Interface 3.9.1
Product Release: December 7, 2018
Release Notes Updated: December 6, 2018
This release of the IBM Aspera Command-Line Interface (the Aspera CLI) provides the new features, fixes, and other changes listed below.
- You can now use the Aspera CLI to send AoC package invitations to external users (users who are not in your workspace or who do not have an AoC account). To use this feature, specify the --public-link argument in your command sequence. For detailed information about sending to an outside user in Aspera on Cloud, see the AoC Help Center topic Sending to an Outside User.
- The Aspera CLI now supports a global client for use with Aspera on Cloud. The global client lets you perform transfers to and from AoC without having to register a custom API integration. For more information, see the IBM Aspera CLI User Guide.
- The Aspera CLI now supports the following additional encryption ciphers:
If you are upgrading from a previous release, the following changes in this release may require you to adjust your workflow, configuration, or usage.
- For the aoc upload command, the --filelist argument is no longer an ascp argument; it is now a CLI argument. Examine any Aspera CLI sequences you may have saved or automated, and adjust them accordingly.
ISSUES FIXED IN THIS RELEASE
ACLI-453 - The aoc download command did not process the ascp option --file-crypt correctly.
ACLI-448 - The aoc send command did not process the ascp option --file-crypt correctly.
ACLI-439 - Aspera CLI commands failed if the source-prefix argument was set to a path other than the current folder path.
ACLI-438 - The aoc send and aoc upload commands did not process the ascp option --file-list correctly.
ACLI-38 - An issue was fixed so that the shares download and shares upload commands can transfer files from within a directory, without transferring the directory itself. This corresponds to the ascp option --src-base. (CIM-198)
- This release of the Aspera CLI does not support the Shares Management API.
- This release of the Aspera CLI does not support the Faspex v4 API.
- OS versions (glibc 2.9 and higher): RHEL 6.7,7.3, 7.4, CentOS 6-7, Debian 7-9, Fedora 26-27, SLES 11-12, OpenSUSE 42.3, Ubuntu 14.04 LTS, 16.04 LTS, 17.10
- Required Libraries: OpenSSL 1.0.2g or higher, glib2 2.28 or higher
Mac: OS X 10.10, 10.11, macOS 10.12, 10.13.
Windows: Windows 7, 8, 10, or Windows Server 2008 R2, 2012 R2, 2016.
PREVIOUS RELEASE NOTES
Release Notes: IBM Aspera Command-Line Interface 3.9.0
Release Notes: IBM Aspera Command-Line Interface 3.7.7
Release Notes: IBM Aspera Command-Line Interface 3.7.6
Release Notes: IBM Aspera Command-Line Interface 3.7.5
Release Notes: IBM Aspera Command-Line Interface 3.7.2
md5: 743da65c7adbe48558a6890bb1bcb007 sha1: edeaa6d70e5b25e5d092b047c8429fa0c5ae9bda
md5: e22efbc6f77af782b3b8cc7d7fe73b5a sha1: a5caf3f9e04bfaf765608fb79ae96e6fa331ec12
md5: c6bc18bf62b9ef19fbf988da0cc3d127 sha1: 3a8989b4f37dc4fecbda680d61de33d0d9b016ed
ACLI-455 - When you use the Aspera CLI to make transfers into and and out of Aspera on Cloud, these transfers are not included in the AoC Analytics app.
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.
Workaround: Remove XML escape sequences (either manually or with an XML parser) from URLS before passing them as input to a faspex get subcommand.
Cannot parse an empty string
The error does not indicate that authorization is denied.
JSON Exception: Error: Path not found
Setting up FASP parameters... Invalid access: Cannot convert empty value.
ATT-657 - Multi-session transfers that use
-k1, or multi-session
transfers from cloud storage to local storage, can result in files on the destination that
are missing bytes. This occurs when a file is split between sessions; the first session
creates matching attributes for the source and destination (partial) file, and the other
sessions do not recognize that there are more bytes for transfer. Workaround: For
multi-session downloads from cloud storage, use
prevent resuming file transfers) or
prevent file-splitting across sessions).
ATT-613 - When uploading files to a HST Server on a Windows computer, if the file name contains a carriage return character ("\r"), then the transfer fails. (CIM-1205)
ATT-537 - Downloads that use ascp --overwrite=always fail when they are authenticated using ASPERA_LOCAL_TOKEN that specifies a local storage path.
save-before-overwrite is not supported for URI
ATT-395 - When running a persistent ascp session, a FaspManager FILEERROR message truncates a filename that is longer than 128 characters to only the first 128 characters.
ATT-361 - ascp transfers to S3 fail when the
option is used.
ATT-360 and NODE-545 - Directory timestamps are not always
preserved on the destination during an ascp transfer that uses
ATT-226 - If the docroot is a URL path, ascp reports incorrect bytes for the sessions that are involved in a multi-session transfer.
ATT-185 - ascp does not reconnect to Redis database when
asperanoded is restarted.
ES-645 - The
ascp -@ option is not supported when the destination is
ES-626 - As of 3.8.0, ascp truncates JSON tags if the tags exceed 4 Kb. With this fix, tag length is checked before the transfer is started and an error is returned if the tags exceed 4 Kb.
ES-624 - [Windows] No files are transferred if the argument for
--src-base includes a semicolon (";") but the transfer is reported as
ES-359 - ascp downloads from SoftLayer do not support
ES-267 - Under rare conditions, ascp transfers to cloud object storage may be reported as successful even though Trapd reports an error and the content is not in the storage. (CIM-475)
ES-177 - The
range_low value of a
-@ argument is not
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 that is named \ (which is not supported by Aspera), the file is not transferred and an error is generated, but the folder then contains the file and all other files in that folder are transferred.
#34322 - [Linux CentOS 7.2] ascp fails to authenticate SSH with a large banner file size (approximately 2000 bytes).
#32890 - During an ascp transfer that uses the --preserve-xattrs= metafile --remote-preserve-xattrs=metafile options, the metafile is not transferred.
#32680 - The option to create a directory (ascp -d) may create a directory at a destination before an expected session failure.
#30324 - During an ascp upload to cloud storage, if a mid-file read failure occurs on the sending computer (which is rare) it can cause the server-side ascp to crash and possibly fail to report transfer completion. This read failure can be caused when a source file is truncated during transfer, a drive or file system fails, or a transfer is canceled with Ctrl+C or other means.
Cannot open -e pre-post command: Unknown error
#29043 - [Windows] 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 database error causes an issue with Console.
#26281 - If you run approximately 100 (or a similarly high number) concurrent uploads to S3, intermittent transfer session failures can occur.
#26185 - During an upload to S3 storage, an error may result if ascp reports a successful file transfer before the transfer to S3 completes.
ATT-717 - Persistent Ascp4 sessions do not report SSH errors (such as an invalid hostname, username, password, port, or file list) to management.
ATT-637 - As of 3.7.4, an empty folder is created on the destination even when the source
folder is excluded from the transfer (by using
ATT-621 - As of 3.8.0, Ascp 4 is not backward compatible.
ATT-583 - Ascp 4 does not automatically create a destination folder when the source is a file list and the destination does not exist. Instead, it writes all the files in the file list into one file. (CIM-1198)
ATT-582 - Ascp 4 sessions run with -d and a file list do not report an error if the destination already exists and is not a folder. (CIM-1199)
ATT-545 - Ascp 4 downloads all content from an AWS S3 docroot, rather than the specified
content, if the docroot contains
ATT-515 - When ascp4 is used by the GUI and transfers are encrypted with AES-128, the GUI incorrectly shows that encryption is "none". (CIM-953)
ATT-485 - Persistent session Ascp 4 downloads from object storage do not report a STOP message to management after the transfer completes.
ATT-477 - When files are transferred to a server with an S3 docroot and quickly
retransferred with the
--delete-before-transfer enabled, some files are
deleted from the destination.
ATT-473 - Ascp 4 uploads to object storage that specify
-k 1 (resume if
file sizes match) are also sensitive to checksum, such that if a file transfer is resumed
and the file has the same size but a different checksum then the entire file is
retransferred, rather than resumed from the last successful chunk.
ATT-451 - Ascp 4 does not respect exclude filters if the file path is part of the command line.
ATT-438 - Ascp 4 downloads from object storage fail if the source filename contains special Unicode characters, such as Japanese font.
ATT-432 - [Linux Ubuntu] When downloading files from a server by using ascp4, if a docroot is configured for the transfer user and multiple source files are specified on the command line then only the first file is downloaded.
ATT-428 - During a persistent ascp4 session, when it a file transferred to a non-existant path and -d is used, the file transfers successfully and the destination path is created but the file is renamed to the last element of the destination path instead of being placed inside.
ATT-409 - If a file list contains an invalid path, no error is reported or logged.
aspera.session.upload.max-jobsto one larger than the number of ascp4 threads. For example,
# Number of jobs allowed to run in parallel for uploads. # Default is 15 aspera.session.upload.max-jobs=50
ATT-298 - [Windows] When the destination has several million files, the source has few
<worker_threads> is set to 64 in
aspera.conf, a download run with the
--delete-after option can take
several hours to delete files and might time out before finishing the deletion.
ATT-191 - [Linux] Symbolic links are not updated on the destination when the symbolic
link option is
follow (the default value when none is set) or
ATT-186 - An ascp4 multicast session does not fail if the multicast IP address and port is already in use on the receiver.
ATT-29 - Files that are transferred to S3 storage with ascp4 retain a .partial extension when viewed in the GUI.
ATT-2 (#32295) - The default minimum transfer rate set in aspera.conf is not respected.
ES-247 - Console-initiated ascp4 transfers fail if the docroot on the
source is a UNC path (for example, \\localhost\SHARE), returning the
ERR Source base/path is not a valid directory/file (doesn't match any source
ES-151 - ascp4 does not recognize the UNC-path docroot of a Console transfer user. (CIM-197)
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.