Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.7.3 for Mac OSX

Product Release: June 5, 2017
Release Notes Updated: June 6, 2017

This release of IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client provides the new features, fixes, and other changes listed below. In particular, the Breaking Changes section provides important information about modifications to the product that may require you to adjust your workflow, configuration, or usage. Additional sections cover system requirements and known problems.

Desktop Client users: Features and issues that are related to configuration, the Node API, and Watchfolder are not applicable to your product.



  • File checksums SHA-256, SHA-384, and SHA-512 can now be set in aspera.conf. (CIM-269)
  • Improved detection of potential Distributed Denial of Service attempts involving missing or slow SSL negotiation requests. The HTTP fallback daemon now automatically times out (after 20 seconds) connections that do not send a request or are too slow.


  • Persistent ascp sessions (run with the --keepalive option) can now accept management control messages sent from a server to the remote machine.
  • The ascp management fields "User" and "ClientUser" now reflect the authorization and authentication methods.


  • A4 is now supported on macOS. Aspera A4 is an optimized transfer engine based on FASP technology. A4 is designed for sending extremely large sets of individual files efficiently. The executable, ascp4, is similar to ascp and shares many of the same options and capabilities, as well as options that enable multi-threaded FASP transfer, TCP and UDP stream I/O, memory usage control, and filtering by when a file was last modified.

Node API

  • RESTful /files calls now return full filepaths for admin users.
  • Specific events can now be requested by ID by using the new /events/{event_id} call.
  • The Node API now supports file locking. ascp transfers respect the lock status while the file is checked out. File locking can be enabled on the server by setting the<files_filelock_enabled> option in the <server> section of aspera.conf to true.
  • The Node API now supports access keys for IBM Bluemix S3 storage and Google Cloud Storage.
  • A new Node API call returns usage data (bytes transferred in, transferred out, and total) listed by access key.

Watchfolder and Aspera Watch Service

  • Users can now update the password of a service without deleting and re-creating the service.
  • Improved behavior of Watchfolders when a transfer session fails to start within a specified timeout.
  • Improved error messages when watchd encounters invalid paths or is blocked by permission settings.
  • When a watchd service is deleted, the Aspera Rund service now deletes all data in the Redis database unless the user specifies that Redis should not be cleaned in the deletion request.


  • On Windows machines, synced files inherit the ACLs of the destination folder.
  • Sync now has a two-minute timeout, enabling it to exit gracefully in the rare cases when under high network impairment conditions Sync does not receive a proper shutdown sequence.
  • The asyncadmin tool can now output file and session status when Sync is using a database with LMS (<async_db_spec> is set to sqlite::lms). When reporting data on a specific source-destination pair by name (using the -N pair_name option), if Sync is running then the output reflects the final state of the last async run and does not reflect any changes in the active sync.
  • Sync run in bidirectional mode with modification times preserved no longer reports conflicts due to directory modification times. However, when the source and destination directory times are both modified between sync sessions, directory modification times might not be preserved.
  • On machines with Unix-based operating systems, a new value, inode, is available for the --dedup option. In this mode, when two or more source files have matching inodes, a hardlink is created between them on the target and the target files have matching inodes.
  • Faster Snap database loading on subsequent syncs when many (100s) of filters are specified.
  • Sync with S3 is now fully supported.
  • Improved Sync shutdown process when a Sync session is stopped.
  • Bidirectional syncs between S3 buckets are now supported.
  • A new option, --cooloff-max=time, can be specified so that a one-time Sync waits for a file to stop changing within the cooloff interval before it synchronizes the file. With this option, the file is skipped after the cooloff-max time.
  • Sync sessions can now be filtered by setting the <filter> configuration in aspera.conf. Command-line filters are applied after aspera.conf settings. If filtering is not always wanted, then configure filters for one user. Sync sessions that are run by that user are filtered while sync sessions run by other users are not.

Cloud, Object, and HDFS Storage Support

  • New fields are available in the AWS access keys to support AWS KMS server-side encryption and the INFREQUENT_ACCESS storage class.
  • Connections to Azure PAGE blob storage can now be created in the GUI.
  • Improved search results for Trapd logs, which now include the ascp session ID.
  • IBM Bluemix Swift and S3 storage are now supported and can be specified from the GUI for ATS connections.
  • Faster file deletion in OpenStack Swift storage. Users can still configure Trap to use the bulk-delete feature, but this option is now disabled by default.
  • S3 versioning is now supported. Versioned object overwrite options can be configured in/opt/aspera/etc/trapd/
  • Aspera now supports Kerberos for Hadoop Distributed File System (HDFS) transfers. (CIM-277)


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 RESTful operations (such as the Node API /files call and ascp run with file IDs), file events as returned by the Node API /events call, no longer show file paths. Instead, they return values for parent_file_id, file_id, and the file name. File events for RPC-style calls to /files and non-file-ID ascp transfers remain unchanged (reporting file_id and file path).


Note: This release contains tickets that were created from different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.

ATT-354 - If the target rate of an ascp transfer is given as a percentage of available bandwidth (ascp -80% -wf), the target rate cap set on the server is not respected and the transfer is allowed to exceed the rate cap. (CIM-546)

ATT-349 - The ascp bandwidth test option -wf is invalid in v3.7.2+. (CIM-516)

ATT-330 - If a user's docroot is configured as a URL (for example, file:////), ascp transfers do not preserve group permissions.

ATT-309 - Content may be mistransferred from a source that is specified with the stdio://URL if the session is delayed, which causes illegal, non-sequential reads from the stdin source.

ATT-293/292 - Vlink settings are not respected when the server receives several (>10) concurrent transfers, and the bandwidth usage exceeds the setting in aspera.conf.

ES-257 - The Node API does not support Basic tokens without access keys and tags, and transfers attempting to use them fail with the error "Error parsing tag, node-user impersonation failed."

ES-250 - When many (500) external authorizations are requested simulaneously from Aspera Central, one of them can randomly fail.

ES-238, WAT-520 - When a client-side asyncsession is forced to quit, in rare cases the server-side async process may not stop. (CIM-364)

ES-183 - The pre/post variable FILE_CSUM is listed as a session variable rather than a file variable in the Enterprise Server, Connect Server, and Point to Point Client guides. (CIM-262)

ES-1 - Pre/post processing notification email fails if the version of Perl is 5.22 or later. (CIM-26)

NODE-213 - The package summary reports greater numbers of files and package size, often double the actual values, when a transfer has been paused and resumed. The value reported for bytes transferred by files_completed is correct.

NODE-188 - alee-admin times out if a node has more registered access-key entitlements than it can process in 30 seconds.

NODE-167 - Newly created access key entitlements on cluster machines are not updated immediately and it may be more than 5 minutes before the access key is valid.

NODE-159 - The save option is not set by asperanoded when the Redis database is restarted if the Redis database is so large that it is still loading and unavailable during restart.

TRAP-64 - An illegal state is reported when scheduling the stream monitoring timer. Though this does not affect transfers, the error causes stream monitoring to stop.

TRAP-58 - Objects cannot be uploaded to AWS if the file name ends with one or more spaces.

TRAP-53 - Resuming uploads to OpenStack Swift storage can fail if the .partial file contains invalid content.

TRAP-51 - During transfer finalization of a multipart upload, .partial files in OpenStack Swift Storage may be deleted. When this happens and the user tries to download the file, HTTP error code 409 is returned.

TRAP-45 - When a 0 bytes file is transferred to HDFS, the transfer is successful but a .partialfile is retained.

TRAP-40 - Downloads of many (100+) large (100+GB) files from cloud storage fail with the message: OutOfMemoryError: GC overhead limit exceeded.

TRAP-39 - Trap fails if the target AWS endpoint is missing from its list of recognized regions, rather than correcting itself.

WAT-512 (#29038) - The --overwrite older option of Sync does not recognize modified files if the size has not changed and they are in storage that does not support sparse checksums, such as Azure cloud storage, or when async is run with the --checksum none option.

WAT-511 - The Rund service becomes inaccessible following an invalid update, and is only restored by restarting.

WAT-500 - Watchfolder may report a HEALTHY state even if the FASP transfer reports an error.

WAT-473 - The Node API service crashes when a request specifies a watch or watchfolder service ID that contains a percent and the ID is not known by the server, rather than returning an error.

WAT-468 - A watch service instance cannot be deleted, updated, or queried if the ID contains URL encoded characters.

WAT-454 - If the docroot is set with a URI, Watchfolder returns the error "No docroot defined," rather than the correct error "URI for a docroot is not supported."

WAT-452 - Watchfolders disappear after restarting the asperarund service if the Watchfolder IDs include backslashes. (CIM-354)

WAT-449 - Sync does not respect the cooloff option.

WAT-445 - A file name hash function collision may occur when creating a watchfolder, which can cause files to be missed in the drop because the same hash is used for different file names.

WAT-442 - Sync does not stop if filters have been configured in aspera.conf and one or more files in the sync session match a filter.

WAT-430 - When async is run with the option --symbolic-links=skip, errors are logged for each symbolic link encountered.

#32941 - Because pvcl does not support the --no-read --no-write option, ascp should fail transfers that use these options with pvcl (transfers to cloud storage). However, ascp ignores the options and continues the transfer. Resolution: --no-read --no-write were replaced with faux://, which is compatible with cloud storage.



  • Mac: OS X 10.8, 10.9, 10.10, 10.11, macOS 10.12 (Sierra)

Client Browsers for Connect Server Web UI

  • Windows: Microsoft Edge, Internet Explorer 8-11, Firefox 27-53, Chrome 32-56
  • Mac OS X: Safari 6-9, Firefox 27-53, Chrome 32-56
  • Linux: Firefox 27-53, Google Chrome 32-56


Enterprise/Connect Server

Mac OS X: AsperaEnterpriseServer-
md5: 7fc99d42db1508a5907def5fe127b395
sha1: 9e465a2048e36e31b74849da9f71fbc252221c0b


Mac OS X: AsperaPointToPoint-
md5: d6831240531b244d235e70ad46063dec
sha1: f26b67d94d3178d16ecdf6959639ce059069a701


Mac OS X: AsperaClient-
md5: 78505d9f2fd3c9bed98847d4f9f537c1
sha1: b15f69542eeeaaaf374acccebf4bac1cb8a32ee1


Note: This release contains tickets that were created from different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.


ATT-245 (#22726) - Successful transfers might log the error, Failure Event: -34 - libssh2_channel_wait_closed() invoked when channel is not in EOF state, particularly downloads in FIPS mode. The error can be safely ignored. (CIM-329)

ATT-107 - The file count that is reported in the GUI under session statistics is incorrect when the user has an exclude filter.

ATT-98 - If inline validation is configured on the server side, the server does not honor a session timeout if a transfer includes a skipped file.

ES-312 - In the GUI, if the Default Target Rate under Preferences or Global Preferences is set to an alphanumeric value, such as "10 Gbps," then only the numeric values are retained. If an alphanumeric value is entered that starts with a letter, then the transfer rate resets to the last valid numeric value.

ES-281 - When several different users access a transfer server remotely, passwords may disappear from the GUI if the GUI is opened while simultaneously querying the SQLite database or the GUI is stopped abruptly and the database does not close gracefully. (CIM-487)

ES-280 - In the GUI, the upload and download rates that are configured for a connection (Connection > Transfer > Speed) cannot have different units.

ES-249 - The aggressiveness setting is being applied to Vlinks, rather than only the network rate controller. (CIM-399)

ES-216 - If the Aspera Connect Plug-in is unable to connect to the server by SSH, a misleading error message, "Failed to authenticate," is reported rather than indicating that it is a connection problem. (CIM-72)

ES-215 - If the Aspera Connect Plug-in is unable to connect to the server by SSH, no fallback is attempted. (CIM-320)

ES-212 - The file name is not shown in the Name or Source fields in the Transfer pane of the GUI in version 3.7.1+ servers if the clients are using versions older than 3.7. Workaround:Upgrade clients to version 3.7.0 or later for the server to display the correct source path.

ES-188 - Transfers through Aspera Forward Proxy are rejected if the node user password contains an @ symbol. (CIM-290)

ES-166 - To set a combination of symbolic links actions besides the default, aspera.conf must be manually edited. Selecting any combination of the above delimited by commas in the GUI sets that invalid text string as the value.

ES-157 - On the Security tab of the Connections Manager, users must enter the decryption password twice.

ES-124 - When email notifications are configured through the GUI, transfer start and stop notifications list the source as the local/LAN IP address, rather than the external/WAN IP address. (CIM-30)

ES-118 (#21517) - Folders that are created in the Connect Server web GUI can have permissions different from the permissions that are specified in aspera.conf.

ES-109 (#35911) - Changing the transfer rate by moving the sliders in the Transfer Monitor UI does not change the transfer rate unless the transfer is stopped and resumed.

ES-98 (#34674) - When Japanese language is set in the GUI, the application doesn't respectaspera.conf settings; all docroot settings are set to false, and the other settings fail with attached Japanese errors.

ES-94 (#31136) - When you install the application on an operating system with the language set to Japanese, clicking the English button in the License Agreement window does not translate the license into English.

ES-86 - After you reopen the GUI, Aspera cannot connect to a Microsoft SAS URL.Workaround: Add and remove a space or letter to the SAS URL to remove the error. You must do this fix each time the GUI is restarted. (CIM-120)

ES-57 - After a fresh installation, initial values for Limit Download Bandwidth and Limit Upload Bandwidth in the GUI are not set to system defaults.

ES-42 - When you retrieve the entitlement status by using alee-admin status, confusing error messages are returned even if the entitlement was registered successfully.

#35952 - asunprotect cannot decrypt a reprotected file.

#34811 - You are unable to download encrypted files with an incorrect decryption passphrase when you are using HTTP fallback.

#32934 - If the Internet accountability software Covenant Eyes is installed, some HTTP fallback transfers appear to complete but then lose connection with the server and then attempt to retransfer. Covenant Eyes captures the entire HTTP transmission before forwarding it to the server. If the file is so large that this process takes longer than about 20 seconds, the server times out and cancels the session. Workaround: Reduce the probability of timeout by increasing the server timeout length. Set Session Activity Timeout in aspera.conf by running the following command:
$> asconfigurator -x "http_server;session_activity_timeout,time_in_seconds"

#32517 - Retransfer requests are unencrypted when transfers are encrypted. This change in encryption can cause transfer failures in some scenarios, such as when a network device drops the retransfer request because it detects a bit sequence it considers malicious.

#31791 - Files with the file extension .aspx are not transferred. Workaround: Edit the resume_suffix setting in aspera.conf on the client.

#30690 - ascp fails with an inaccurate message—Error: failed to authenticate—when the server is configured to accept only unsupported ciphers.

#28679 - In some cases, the fallback server cannot accept additional connections, possibly due to too many 'incomplete' requests.

#27879 - [Mac] In Connect Server, always_set_home does not work if the user's home directory does not exist.

#27056 - ascmd does not respect server-side symlink configuration.

#24918 - When shares are added to or removed from a user while the user is connected to Shares in the Enterprise Server GUI, the remote file browser is not updated. The list of shares that is displayed in the remote file browser bar is not refreshed until you disconnect from Shares and reconnect to it. If a share was removed, the user is unable to perform certain actions and it is not clear to the user that this occurring because the user is no longer authorized for the share.

#23246 - Warnings are not generated about files skipped due to the source base setting.

#23070 - If a transfer of several files is interrupted, the retries generate a no such file error for files that transferred.

#22998 - If the overwrite setting in the server's aspera.conf is deny, a destination file with the same name as the transfer file is still overwritten.

#21629 - Connect Server does not accurately reflect file permissions for user actions.


ATT-366 - An ascp transfer to object storage does not fail immediately if chunk size is configured incorrectly.

ATT-365 - An ascp transfer that is initiated with persistent session (from one of the FaspManager SDKs) might crash while freeing memory for argument stop management messages.

ATT-361 - ascp transfers to S3 fail when the --symbolic-link=copy or --symbolic-link=copy+force option is used.

ATT-226 - If a URL docroot is configured, ascp reports incorrect bytes for the sessions that are involved in a multi-session transfer.

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-189 - In rare cases, ascp keeps running after it encounters a disk read error. (CIM-233)

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

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 respected.

#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.

#33094 - The ascp option delete-before-transfer is not supported for URI storage.

#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.

#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.

#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.

#29255 - Download from SoftLayer of a file larger than 62 GB is unsuccessful. Workaround: Do not use time-stamp preservation with SoftLayer.

#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.

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

#23503 - Uploads of zero-byte files to Akamai appear to be successful, but no file is present at the destination.

#22905 - When you copy a file in S3 storage with ascp, if a slash is appended to the destination -- for example, /path/ -- the file is renamed path/. Because of the trailing slash, it appears to be a directory, but is actually a file.


ATT-357 - Transfer errors might not be reported to the client and only logged in the remote log.

ATT-338 - Parallel uploads of several large (>1 GB) files to object or HDFS storage may fail with the error "Peer aborted session" if the number of threads that are specified in the ascp4command exceeds the number of jobs that are allowed to run by Trapd. Workaround: Open /opt/aspera/etc/trapd/ and set the value for aspera.session.upload.max-jobs to one larger than the number of ascp4 threads. For example,
# Number of jobs allowed to run in parallel for uploads.
# Default is 15

ATT-321 - To use ascp4 to transfer with object storage, you must set the chunk size on the server to 64 kb for transfers that include primarily small files, and set it to 1 Mb for transfers that include primarily large files. If the chunk size is not set on the server, then the transfer fails.

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 that is transferred with ascp -p is not preserved, while the timestamps of the child files and directories are preserved.

ATT-39 - When ascp4 is run with the --no-write option, a 0-byte file and an .aspx (partial) file are created at the destination.

ATT-37 - ascp4 does not terminate 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 you upload many small files (for example, 1 million 4-byte files) to S3 storage.

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

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

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

ES-247 - Console-initiated ascp4 transfers fail if the docroot on the source is a UNC path (for example, \\localhost\SHARE), returning the error ERR Source base/path is not a valid directory/file (doesn't match any source path). (CIM-397)

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

#26484 - A4 through Aspera Proxy is not supported.

Node API

ES-309 - [Unix-based OS] When a group ID (setgid) is set on a parent directory (chmod g+s parent_dir), subdirectories that are created by a call to the /files/create endpoint have the primary group ID of the user rather than the group ID of the parent directory. (CIM-541)

ES-248 - While a transfer of many files is in process, Node API reports skipped files as complete. The counters are correct once the transfer is complete. (CIM-398)

NODE-257 - Reports sometimes fail if the Node API temporarily reports an impossibly large value for bytes_transferred.

NODE-244 - A POST request that contains an invalid value for "storage_class" returns the wrong error message, "Invalid value for server_side_encryption".

NODE-236 - Transfers with a status of "waiting" cannot be canceled.

NODE-177 - [Unix-based OS] ascp transfers and asperanoded may fail when trying to transfer many (millions) of small files because the Redis db exceeds available number of file descriptors.Workaround: Increase the maximum number of file descriptors from the default of 1024 to a larger value, such as 1,000,000, by running the following command:

$ ulimit -Sn 10000000

NODE-139 - The --token-key-length option in asnodeadmin allows invalid token key lengths.

NODE-137 - A Node API /ops/transfers call reports the incorrect values for files_completed and files_failed.

#33374 - Symbolic link capability is only available on local storage but an unimplemented function error does not appear when the user attempts to create a symbolic link to a file on cloud storage (S3) from the Node API.

#33229 - Users cannot browse a file on cloud storage by using a /files/browse API request.

#33206 - /ops/transfers erroneously shows some queued transfers (which are farther down in the queue) as failed before they complete.

#32669 - When a directory is linked from a subdirectory, it does not appear in the search result for a /files/search request in the Node API.

#32627 - When a file name is just a dot and an extension, (for example, .pdf), then it is reported as a file with "content_type"=>"application/pdf" or a hidden file named PDF; for example:
{"id"=>"27", "name"=>".pdf", "size"=>12, "content_type"=>"application/pdf", "type"=>"file", "modified_time"=>"2015-09-10T15:24:01Z", "access_level"=>"edit", "permission_count"=>0}

#31712 - For both S3 on AWS and SoftLayer Swift storage, /files returns modified_time for files but not for folders.

#30542 -/files PUT (file rename) should be fixed to involve only one PVCL operation but still return the proper 409 code when there is a destination conflict, and PVCL needs to return proper error codes stating that the move operation failed because of a destination conflict.

#29848 - When <write_allowed>, <read_allowed>, and <dir_allowed> are all set to false inaspera.conf, Node API calls to URLs such as /files/browse are returning response code 500 Internal Server Error: instead of another code that better indicates that access to the resource is denied.

#29787 - When the docroot is not configured, the HTTP error code 500 ("Internal Server Error") is returned.

#29187 - For content in cloud storage, the Node API does not display all the files in the docroot directory. Workaround: Use the /files/info request to browse the docroot directory when content is in cloud-based storage.

#29138 - For files in S3 storage, the Node API does not return the correct file modification time.

#29078 - When an access key is created with the standard node user authorization, the access key inherits that node user and its associated system user. Afterward, asnodeadmin can be used to associate a new system user to the node user, but the new system user is not updated for the access key.

#28219 - [Unix-based OS] asperanoded fails to delete a directory name containing backslashes. Workaround: Increase the number of system processes that are allowed by the operating system to run concurrently. In a Terminal window, take the following steps (note that the limit is shell-specific, so all commands must be run in the same Terminal):
  1. Stop asperanoded.
  2. Determine the current limit by running:
    $ ulimit -a | grep "open files"
  3. Change the limit. For example, to set a value of 2048, run the following:
    $ ulimit -S -n 2048
  4. Restart asperanoded.
  5. Resend the /files/delete request; the directory and all subdirectories are removed.

#25127 - HTTP fallback temporary files (*.haspx) are not excluded by the Node API.

#23434 - Files that start with "._" are not returned by the Node API browse action.

#22619 - In the Node API, /files/search follows symbolic links.

#20002 - The Node API is inconsistent in how it handles ymbolic links. /files/browse doesn't follow the links and reports links and their target (final type and next name), while /files/inforeports symbolic links as files or directories.

#18659 - Searches with very long path names (over 520 characters) report an "insufficient buffer space" error.

#18368 - Files with a backslash in the file name are not displayed in the list when the user browses the remote source on the new package page.

Watchfolder and Aspera Watch Service

WAT-501 - Some ascp sessions started by a Watchfolder may not stop running after synchronization is complete when many (50) large (1000 files of 2 KB to 1 MB) Watchfolders are started at the same time.

WAT-314 - asperawatchfolderd must be running in order to delete a Watchfolder.

WAT-246 - [Mac OS X] Watches cannot be created on symlinked directories.

WAT-200 - Recently finished Watchfolder drops are not stored and are lost if asrund is restarted.

WAT-174 - Watchfolder uses excessive memory when it watches 10 million files.

WAT-169 - If top_level_dirs drop detection is used with x top-level directories in Watchfolder, 7(x)+ drops are created. The drop count continually increases.

WAT-159 - If one file in a Watchfolder transfer fails or a drop is aborted, the other files in the package are reported as aborted but ascp is not stopped and the transfer continues.

#33877 - Aspera Enterprise licenses that are watchfolder-enabled don't display watchfolders as an enabled component.


Async on Mac OS X does not support continuous PUSH or BIDI modes.

ES-92 - Sync reports incorrect counts for 'deleted_paths', 'deleted_bytes', and 'cumulative_deleted_bytes'.

ES-50 - When you use local storage for Sync with Files on Unix-based systems, Sync fails if the access key storage does not start with "/". For example, data/storage fails but /data/storage is successful.

WAT-523 - Meta-attributes are not preserved in sync sessions that use the --dedup=copy option.

WAT-465 - Sync hangs following a TCP impairment that produces a libssh2 timeout or error.

WAT-288 (#27311) - An --apply-local-docroot pull copies the local docroot path into the same path. For example, /home/user1/sync is copied into /home/user1/sync.

WAT-9 - When the scan-file-rename option is used with asperawatchd, moved files should be detected and renamed at the destination, not deleted and replaced by a transferred, renamed file.

#29038 - Using overwrite=always when you sync with cloud storage does not overwrite the file. The default checksum behavior with S3 (as with any cloud storage) is "none". An existing file on S3 is considered identical to the local file when their sizes are equal. Therefore, the file on S3 is not overwritten even when the content of S3 differs from the content of the local file.

#28817 - The Sync log entry for SYNCERROR_DELAY does not include information that describes the file name and path.

#27621 - Hidden, temporary, or transient files, such as temporary files created by Microsoft Office products, can cause Sync to report conflicts.

#25631 - When you transfer from Windows to Mac and use preserve-acls=native and remote-preserve-acls=native, ACL data are saved as xattr. Workaround: Do not use the nativesetting when you transfer or sync across platforms.

#24805 - ACL data are preserved at the destination for all files and subdirectories in the source folder, but ACL data for the source folder itself are preserved at the destination.

#23954 - When the --preserve-acls or --preserve-xattrs option is used, async does not preserve the acl or xattr when either file acl or xattr is modified and (a) file content is unmodified or (b) file content is unmodified and the file is renamed.

#23004 - Aspera Console does not draw a line between the involved nodes for an asynctransfer. This issue occurs when two managed nodes are used with two interfaces on two different networks.

#22633 - Sync does not support large xattr/ResourceForks.

#22044 - asyncadmin reports all sessions are locked after the last actual running session.

#21014 - When creating a file with vi during a sync, the swap file is in conflict.

#20906 - async cannot create a watch on an unreadable directory; therefore, it does not get notified when permissions change. In addition, async treats an unreadable directory as "skip" rather than reporting an error or conflict.

#19945 - asyncadmin creates SHM and WAL files for read-only operations. Once asyncadmin is run as the root, async run by the user does not have permission to access the existing SHM and WAL files and thus async fails. This issue is due to a bug in SQLite.

#16911 - Characters in the async session option that are not preceded by a "-" or "--" are ignored and no error message is reported. Any session options that are specified (such as -l or -a) after the string of characters that are not preceded by a "-" or "--" are also ignored. The session runs using the default values, and does not notify you that the command line settings were ignored.

#13761 - If file names contain "\" or new line, async transfer fails, causing the internal transfer queue to become full and the synchronization to stall.

#13645 - When a directory is renamed during transfer, Sync continues running and never completes.

Object Storage Support

TRAP-71 - Multi-session transfers to object storage can stall if the number of files open for write in multi-session mode exceeds the default number of starting threads (64). Workaround: Open /opt/aspera/etc/trapd/ and set aspera.session.max-starter-threads to a larger value. If this setting is not in the file, add the following line with an appropriate value:

TRAP-59 - If an incorrect DNS nameserver is set in /etc/resolve.conf and then corrected, TrapD must be restarted for the correct nameserver to be used by TrapD. If TrapD is not restarted, TrapD fails to connect and retries indefinitely. (CIM-469)

TRAP-57 - If a very large file (several TB) upload to AWS S3 is interrupted after more than 1 TB is transferred, resuming the transfer may take hours and the session may close before any data is transferred. (CIM-476)

TRAP-28 - When downloading from cloud or object storage, ascp always takes the equivalent of 1 GB of buffers from Trapd. This can lock buffers in ascp queues for hours and may prevent other ascp transfers from transferring normally.

TRAP-27 - In some cases, stopping Trapd while an ascp transfer is still running may cause a restart of Trapd to fail.

TRAP-26 - Sometimes when Trapd is being heavily loaded by many ascp transfers, Trap may return a 'No such file or directory' error.

#36067 - Deleting folders from a Limelight directory is slow.

#33214 - Transfers to and from cloud storage using authorization tokens with URIs that do not have a docroot specified are not supported.

#25636 - To use a larger chunk size to transfer large files to AWS S3 storage, some users modify the memory settings in the Trapd initialization script, If you do so, be sure to preserve the script manually during upgrades to prevent it from being overwritten.


For online 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.

Powered by Zendesk