Release Notes: IBM Aspera On Demand 3.6.1
Release Notes: IBM Aspera On Demand 3.6.1

Release Notes: IBM Aspera On Demand 3.6.1

  • Product Release: June 3, 2017
  • Release Notes Updated: June 3, 2017


This release of IBM Aspera On Demand provides the following new features:

  • Support for IBM Aspera Enterprise Server 3.6.1

IBM Aspera Enterprise Server 3.6.1

New Features

  • A new procedure removes the --master option from asperawatchd and introduces a procedure to elect a leader among the running daemons; this helps to overcome the situation where the master instance crashes or loses the connection to the other instances.
  • Instead of specifying the tool used by watchadmin using the --tool option, this release offers a new set of tools. For example, the first command is replaced by the second:
    aswatchadmin --db-spec redis:localhost:31415 --tool=daemon --create /mnt
    aswatchadmin create-watch /mnt --db-spec redis:locahost:31415
  • Reverse proxy support for async.
  • Support for an inclusion filter with Console smart transfers.
    Note: This feature is not available in Console 3.0.5 (the current release).
  • ascp transfer resume for -k2 (sparse checksum) or -k3 (full checksum) works with a FIPS-140-compatible cipher.
  • The option ascp --remove-empty-source-directory for the --remove-after-transfer feature can now be enabled in Aspera Central in the SOAP API; it removes the source directory itself.
  • Transfers to Amazon S3 storage now have the capacity to set cache-control request headers. For more information, see the API Reference in the AWS documentation at the following URL (subject to change):
  • Azure support now includes storage to blob pages.
  • When watchfolder transfers are initiated from Console or the watchfolder API, the Name field is not populating with data.
  • ascp now reads session_timeout_sec from aspera.conf.
  • Support for Amazon KMS when uploading to S3 (pushes data directly to S3 and supports KMS encryption).
  • Support for the multi-session threshold feature in node (file.json) transfers.
  • Node API /transfers and /opt/transfers take a multipart field to split a given transfer job between multiple ascp sessions, possibly over multiple nodes when using a cluster as an initiator. Functionality: this adds a default multipart aspera.conf configuration directive to use when one is not specified by the API call.
  • Amazon's new Infrequent Access storage option is now available as a storage class, through docroot configuration.
  • Support for full URIs in file lists and file-pair lists.
  • Added a client-side configuration option to define a per-user or global default of the SSH key (to help clients used to running ssh without specifying a key if $HOME/.ssh/id_rsa exists).
  • A new option in aspera.conf for client-side encryption setting frees users from having to specify a matching value at the command line (-T).
  • watchfolderd support for aspera proxy (dnat/dnats).
  • The default read/write block size is now set to 256 K (262144 KB) in ascp.
  • Support for cache-control metadata for S3.
  • Improved performance (by increasing the speed) when the system is deleting a large number of files in Azure.
  • watchadmin now allows specification of the escape character when using --format.
  • Console now reports the activity of the server node on the Activity Overview Page, in the Sync Jobs list, when async_activity_logging is set in aspera.conf.
  • Support for OpenSSL 1.0.1t

Fixed Issues

WAT-190 - Watchfolder does not retransfer changed files because it does not detect a change that happens after the cool-off of the file but before the completion of the drop.

WAT-170 - async stops mid-transfer when using watchd.

WAT-158 - The watchd existing watch report is impaired.

WAT-168 - Local post-processing "transfer_delete" is executed for failed files.

WAT-136 - On a watchfolder, timestamps are not preserved, even when they are specified in the configuration.

WAT-51 - Watchfolder status is stuck in Processing when files are skipped by ascp.

WAT-64 - watchd now supports namespaces in redis to distinguish the different watchd instances running on the same redis instance; this enables starting multiple watchd instances using different users.

WAT-86 - watchadmin now has a feature to test and set system values.

WAT-92 - In watchfolderd, there is now an ability to reenable remove post-processing.

WAT-119 - async noncontinuous mode does not sync files after a cancelled session.

#35378 - asperahttpd crashes when resuming an existing ascp transfer.

#35253 Alee logs show that alee reports 400 bad request when the redis database is empty or all the keys have 0.

#35002 - When the user attempts to transfer a file containing the character '&' in the name while using the AWS signature V4 (AWS4-HMAC-SHA256), the transfer fails. Users who use aws:kms server-side encryption will experience the issue since using KMS implies the use of signature V4. To get trapd to self -configure to use the signature V4, do one of the following:
  • Use the KMS server side encryption (sse:kms).
  • Use a server in a region where this is mandatory - like Frankfurt (eu-central-1).

#34419 - The user is unable to download encrypted files with an incorrect decryption passphrase. (This is stilll an issue when using HTTP fallback; see ticket #34811 in the Known Issues section).

#34166 - Memory leaks in asperanoded result in system crashes.

#34139 - Delete-before-transfer is not working for a SMB\CIFS path.

#34124 - When transfers are initiated from Watchfolder Transfers, the Name field does not populate with data.

#34045 - Connect Server for Linux cannot be browsed from the browser when the doc root is set using file:///.

#33978 - Ability to check for sshkey path in $HOME/.ssh not functioning properly.

#33975 - (Point-to-Point) A Console transfer with SSH keys is not working after an upgrade to Point-to-Point 3.6.0. The issue occurs when Console is set up to have smart transfers where the following is true:
  • The non-root user has a docroot set on aspera.conf.
  • The remote endpoint is associated with an SSH private key.
  • The remote host is a unmanaged node.

#33567 - When server-side encryption-at-rest (EAR) is configured for local storage using file:///<path> docroot, the aspera.conf chunk_size parameter must be set.

#33536 - When the database is configured on a remote machine, and db_host is set, ascp attempts to connect to the local database.

#33535 - asperawatchfolderd is not uninstalled on Linux.

#33233 - Basic tokens are stored and can be reused to make arbitrary transfers.

#33204 - A file name "\" causes a crash.

#33011 - asdelete fails to connect to the server.

IBM Aspera Shares On Demand (SHOD)

New Shares Features

  • Security: Upgrades to Ruby 2.0.0, Java 8, and OpenSSL 1.0.1r.

Fixed Issues

#33734 - Accessing https://shares_hostname/node_api/ping should not require authentication.

Known Issues

#29891 - Sometimes restoring Console's configuration file deletes the home folder of users in aspusers group, except aspadmin. Workaround: Before restoring your configuration file, follow the steps in this article:

#29858 - Sometimes Console's database is left empty after restoring a configuration file and users not allowed to log back into Console. Workaround: Before restoring your configuration file, follow the steps in this article:

#29649 - Restoring one SHOD Shares instance's database onto another SHOD Shares instance causes instance to not be browsable, with perpetual license error. Workaround: Use Rake task to disable and re-enable entitlement mode for the Shares application:


Shares On Demand (SHOD)
Region Registered AMI
us-west-2 ami-8f9b65ef
ap-northeast-1 ami-ea21c28b
ap-northeast-2 ami-46a46f28
ap-southeast-1 ami-26ab7a45
ap-southeast-2 ami-73ae8110
ap-south-1 ami-7894e817
eu-central-1 ami-c541adaa
eu-west-1 ami-baa83ec9
eu-west-2 ami-8c6671e8
sa-east-1 ami-ef26ae83
us-east-1 ami-537b8f3e
us-east-2 ami-f4af8891
us-west-1 ami-79304b19


Shares On Demand (SHOD)

  • IBM Aspera Shares 1.9.3
  • IBM Aspera Enterprise Server 3.6.1
  • IBM Aspera Console 3.0.5










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.