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.

NEW FEATURES

General

Data is now encrypted in transit (using AES-128) by default when a new connection is created in the GUI.

Transfers with Microsoft Azure Files are now supported, including using Azure Files access keys and the ability to create connections to Azure Files storage in the GUI.

The -u option can now be used with ascp4 to specify user strings to pre- and post-processing scripts.

Improved ascp4 transfer stability. (CIM-514)

Improved error handling including: 1) errors are reported to both the client and server, 2) if the destination does not have enough disk space to receive the transfer then the session now exits with an error message, and 3) if some files in a transfer session fail to transfer, the last failure is now reported in the A4 session status. (CIM-767)

Node API

The Node API /ops/transfers now supports ascp4 transfers. Specify that a transfer should use ascp4 rather than ascp by adding the following line to a JSON request:

"use_ascp4" : true

The Node API can now pass instructions on how FASP transfers handle symbolic links. If no method is specified, the default policy is now follow.

The logging thread to the kvstore database now times out after the FASP transfer session ends. The timeout period can be configured with a new setting,<activity_log_queue_timeout>, in aspera.conf.

Partial files reported by a /files/browse call can now be identified with the new "partial_file" : true attribute, allowing them to be processed separately from complete files. To enable this, the <partial_file_suffix> must be set in aspera.conf. Files with the resume suffix are still filtered out from the dictionary.

Watchfolder and Aspera Watch Service

Faster directory scanning by the Aspera Watch Service, particulary of directories that contain many (10,000s) subdirectories.

Watchfolders now supports IPv6 addresses. (CIM-531)

Watchfolder can delete files from the source as soon as the file is successfully transferred, rather than waiting for the session to complete, by editing the Watchfolder configuration JSON file or by enabling it in Console (In the Console GUI, go to File Handling > Source deletion and select Automatically delete a source file after transfer of this file). (CIM-493)

Sync

The Sync guide in now included in the Enterprise Server, Connect Server, and Point-to-Point Client guides. It includes new instructions for composing an asynccommand and an expanded troubleshooting section.

Improved handling of changing files by continuous Sync sessions when checksum is set to none; files that return a sharing violation error are now retried per --sharing-retry-max.

Access key authentication is now supported by using "Basic: token_string" as an argument for the -W option.

The --dedup option can now be used in async commands even if it is not specified in the first run; however, --dedup is rejected if the first run does not use -k(calculate file checksums). The dedup index is created if it does not already exist, and if the database is large then this process can take some time.

For AWS S3, Content Type is now automatically applied to uploaded objects from an updated list of content types. If you do not want to use content types or want to use your own list, instructions are provided in the guide.

The maximum open file limit of Trapd is now 20,000, improving the robustness of connections to the Redis database.

Trapd and custom Trapd plugins can now use different libraries. Each plugin has a definition file in which the class name of the plugin and its classpath can be set. The plugin can be given a simple name and set in the docroot by using the simple name, as ?plugin=simple_name.

Simplified s3.properties configuration due to AWS S3 infrastructure enhancements that no longer require host caching and selection to optimize transfer performance. The following settings are deprecated, and have no effect if present: aspera.httpclient.connections-per-host-hint,aspera.s3session.hostcache.enabled, aspera.s3session.hostcache.directory, aspera.s3session.hostcache.aliases.enabled, aspera.s3session.hostcache.ns-lookup.main, and aspera.s3session.dnsResolvePolicy.

BREAKING CHANGES

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

Activity event reporting can now be configured with a new aspera.conf setting, activity_event_logging. Prior to 3.7.4, activity event reporting was always enabled. As of 3.7.4, activity event reporting is disabled by default to improve server performance, and it must be enabled in order to query the Node API /events endpoint. Nodes that are added to Aspera Files must have activity event reporting enabled. To enable it, run the following command:

asconfigurator -x "set_server_data;activity_event_logging,true"

ISSUES FIXED IN THIS RELEASE

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-427 - ascp transfers fail when the destination is in S3 and is archived to S3 Glacier because the file types no longer match.

ATT-421 - FASP manager does not return an ARGSTOP message when a file is not transferred, such as when a file is skipped because the file exists at the destination and overwrite is set to never.

ATT-398 - A4 transfers fail with the error "Failed to create provider" when the docroot contains a query part, such as s3://s3.amazonaws.com/my_bucket/?storage-class=REDUCED_REDUNDANCY.

ATT-389 - When transferring multiple files as part of an Aspera Orchestrator workflow that includes inline file validation, ascp returns the wrong error message if one file fails validation and continues to attempt to transfer the remaining files.

ATT-379 - ascp transfers do not fail when the target rate is set with only a unit, such as k, m, or g. In this case the transfer session uses the target rate set on the server or the default rate if no rate is set.

ATT-376 - An ascp transfer that uses a file pair list which contains only one file fails if the parent directory of the destination path does not exist.

ATT-375 - HTTP fallback sessions cannot complete when they use a single socket connection instead of a new connection for each file. (CIM-571)

ATT-370 - When a client-side ascp transfer errors when connecting to the Redis database, server-side transfers with cloud storage can continue running.

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. (CIM-679)

ATT-363 - An upload to object storage over an HTTP fallback connection fails to resume.

ATT-358 - 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 in aspera.conf is not respected.

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

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

ATT-37 - ascp4 does not terminate if a transfer exceeds the available space on the destination machine.

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

ES-402 - Inconsistent error reporting by ascp4 to the source and destination can cause discrepancies in the transfer session logs. (CIM-767)

ES-396 - The Aspera Noded service can run out of memory and crash when the <capacity> setting in aspera.conf contains <value>total_vlink_capacity</value>instead of <schedule format="ranges">total_vlink_capacity</schedule>.

ES-380 - [Linux RedHat] After updating yum on an Aspera server to kernel 2.6.32-696.3.2 or newer, Java-based Aspera services such as Stats Collector, ALEE, and Trapd fail to start. (CIM-690)

ES-369 - If another application uses port 31415, ascp might not start and cause Connect to report an error. (CIM-619)

ES-354 - Transfers fail and the Aspera Central service crashes after registering a subscription to the Aspera Central service using the SOAP API call FASPSessionNET. Note: this is a deprecated feature. (CIM-650)

ES-333 - If more than one group is configured in aspera.conf, users can be assigned configuration settings from a group to which they do not belong. (CIM-588)

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/createendpoint have the primary group ID of the user rather than the group ID of the parent directory. (CIM-541) Workaround: To configure the server to allow a Node API call to set the owner, set the value for <group_ownership> in aspera.conf to "-" by running the following command:

$> asconfigurator -x "set_node_data;group_ownership,-"

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

NODE-416 - When server side encryption-at-rest is enabled, the Node API includes the .asp-meta files in lists of transferred files. (CIM-737)

NODE-410 - When a Node API query to /ops/transfers includes the after_time parameter, the "files" object in the output is empty. (CIM-661)

NODE-406 - The asperanoded service can crash if an invalid header value is specified in a curl command. (CIM-672)

TRAP-85 - Trapd uses a large number of file descriptors and does not close expired connections.

TRAP-78 - [Swift] When a file is uploaded to Swift storage by using a multi-session ascp transfer, multiple copies of the manifest file are created. As a result, if the file is deleted at the destination, a copy of the manifest file can remain and it appears to the user that the file is still present but much smaller.

TRAP-75 - When copying many millions of files to object storage with ascp4, Trapd might run out of memory and report an error.

WAT-574 - Sync can run indefinitely if the queue becomes full.

WAT-565 - Sync might store incorrect counter data in the database if it is stopped abruptly.

WAT-542 - When the async logging level is set to log, the file list is included in the log.

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-409 - Permissions assigned to IBM Aspera Shares users are not inherited by the Enterprise Server that hosts the share. For example, if a user is created in Shares and does not have delete permissions to a share, if the Shares user runs an ascp download directly from the server (from the command line, through the GUI, or using Hot Folders) and uses --remove-after-transfer in the command line or the "Automatically delete source files after transfer" option in the GUI, the files are deleted from the source. (CIM-788)

ES-357 - If the user language is set to Spanish (user.language=es in aspera.prop) and global configuration settings are changed in the GUI (Configuration > Global), the GUI displays the default values after it is restarted even though the updated settings are saved in aspera.conf. (CIM-638)

ES-323 - When doing a dry run of an asdelete (by using the -d option), the log shows all the files that were scanned, not the files that would be deleted by the asdelete command. (CIM-558)

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-206, ES-102 (#35857) - [Linux] When you attempt to launch the GUI after a system reboot, you might get the error message, "Application ascpmgr.Main - failed to launch: Failed to retrieve atom name." This indicates that the clipboard is locked. Workaround: Copy something to the clipboard to release the clipboard lock and the GUI launches normally. (CIM-302)

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-139 - [Debian Linux] Update patches introduced in Perl version 5.14.2 and included in later versions cause the Connect Server web UI to return a 500 error.

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-98 (#34674) - When Japanese language is set in the GUI, the application doesn't respect aspera.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:

#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 on S3 with the same name as the transfer file is still overwritten.

ES-349 - When ascp is run with resume enabled (-k {1|2|3}), --preserve-file-owner-uid and --preserve-file-owner-gid are ignored.

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.

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

A4

ATT-438 - A4 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 in receive mode, 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-426 - To use SSH key authentication in A4, the full path to the private key must be specified as the argument for -i because A4 does not automatically look in the transfer user's home folder. This prevents Aspera Console from being able to use SSH keys if it is configured to use A4 instead of ascp because the full path cannot be specified in the Console UI.

ATT-366 - An ascp4 transfer to object storage does not fail immediately if chunk size is configured incorrectly. Workaround: On the client command line, set the chunk size equal to the size of the shared memory buffers used by Trapd with the --chunk-size option. By default, shared memory buffers are 1 MB, in which case --chunk-size=1048576 should be used.

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 ascp4 command exceeds the number of jobs that are allowed to run by Trapd. Workaround: Open /opt/aspera/etc/trapd/trap.properties 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
aspera.session.upload.max-jobs=50

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

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-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-2 (#32295) - The default minimum transfer rate is not picked up from aspera.conf.

ES-416 - A4 transfers with object storage can hang if the Aspera Trapd service loses connection or otherwise errors.

ES-367 - If a user's docroot contains a string variable, such as /home/$(name), ascp4 returns the error "No such file or directory (e=104)". (CIM-586)

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)

Node API

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-437 - Transfers with object storage, particularly with buckets that contain a lot of data, become slow when <files_filelock_enabled> in aspera.conf is set to true (in order to enable the filelock feature in the Node API /files endpoint). The default setting is false.

NODE-405 - The max_rate_kbps in the output of a /events call is incorrectly reported as zero.

NODE-345 - A RESTful Node API POST to /ops/transfers can trigger two transfer sessions for the same file and result in a corrupted file at the destination and a slower final transfer rate.

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:

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

#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 in aspera.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):

Stop asperanoded.

Determine the current limit by running:

$ ulimit -a | grep "open files"

Change the limit. For example, to set a value of 2048, run the following:

$ ulimit -S -n 2048

Restart asperanoded.

Resend the /files/delete request; the directory and all subdirectories are removed.

#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/info reports symbolic links as files or directories.

#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-567 - A Watch Folder configured for growing files reports a "Healthy" state and shows bytes are written at the destination despite having an invalid password and no transfer occurring.

WAT-559 - Watchd allows users to create a watch on the root folder, which can overload the Redis database and cause Watchd to coredump. (CIM-662)

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-594 - During a Sync session, if ascp fails to transfer a file, Sync keeps the file as pending rather than as errored and the session does not stop. (CIM-814)

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

WAT-571 - Sync deletes files from the destination if the files become inaccessible on the source, such as when permissions change. (CIM-729)

WAT-557 - A continuous Sync push that is run with the --scan-dir-rename option does not synchronize files if the directory is created and then renamed after the Sync session has started.

WAT-550 (#29686) - A continuous Sync push to S3 storage does not update the object in S3 when the source file is renamed or deleted while it is transferred.

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-377 (#27391) - [Linux] A continuous async session that is configured to follow symlinks does not sync a symlink file after it is modified.

WAT-362 (#24812) - [Windows, Linux] If a file's size decreases during a continuous Sync push, the file remains pending and is never synced.

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-287 (#32064,#32883) - [Windows, Linux] When syncing a directory in continuous, bidi mode, Sync keeps running with one pending file rather than complete and go idle.

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.

#25915 - [Linux] If a source file is overwritten during a continuous Sync in push mode, the corresponding file on the destination might be deleted. Workaround: Run a one-time push Sync of the overwritten file to restore it on the destination.

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

#23400 - [Linux] As of Sync version 1.5+ the user is permitted to sync to the root directory.

#23004 - Aspera Console does not draw a line between the involved nodes for an async transfer. 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.

#20767 - If you use the -R log dir from Linux to Windows and there are spaces in the directory path, the path is truncated at the first space in the path.

#20347 - Async reports errors and conflicts for deep directory depth when the sync is from Linux to Windows.

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

#18780 - [Linux] An async push conflict occurs when a new file is renamed quickly.

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

Object Storage Support

TRAP-83 - Using the default configuration of the Java Heap size, Trapd might be unable to recover enough memory after a full garbage collection, resulting in an out-of-memory error. Workaround: Edit the configuration by opening /opt/aspera/etc/init.d/asperatrapd_init.sh and locating the following section:

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/trap.properties 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:

aspera.session.max-start-threads=1280

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,asperatrapd_init.sh. If you do so, be sure to preserve the script manually during upgrades to prevent it from being overwritten.

PRODUCT SUPPORT

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.