Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.7.2 for Mac OS X

Product Release: January 17, 2017

Release Notes Updated: January 17, 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.



  • macOS 10.12 (Sierra) is now supported.
  • When using a local URI docroot or destination (such as file:////data), for example when server-side encryption-at-rest is enabled, temporary partial files can now be created during ascp transfers by configuring <partial_file_suffix> in aspera.conf. (CIM-85)
  • Connections can now be created with an ATS subscription in the GUI.
  • FASP transfers are more secure with upgraded OpenSSL (from 1.0.2i to 1.0.2j).
  • Special file permissions (setuid and setgid) are now supported in ascp and the Node API when the permissions are configured in aspera.conf. (CIM-201)
  • Users can now run asnodeadmin --db-update to migrate a non-local Redis db from Enterprise Server 3.5.6 and earlier versions. The local Redis db is automatically migrated and updated by the installer during upgrades.
  • A man page is now available for asconfigurator. The asconfigurator reference is included in the Enterprise Server, Connect Server, and Point-to-Point Client guides.


  • A new transfer scheme, faux://, enables testing a transfer without reading from disk and/or writing to disk, eliminating the need to generate large test sets.
  • Users can now specify multiple SSH private keys (both DSA and RSA keys) in the same ascp command.
  • SSH private key strings can now be used to authenticate ascp transfers by setting a new environment variable, ASPERA_SCP_KEY.
  • Two new ascp options extend support for base64 encoding: --dest64 can be used to indicate that the destination path is base64 encoded, and --source-prefix64=source_prefix can be used to indicate that the specified source prefix is base64 encoded.
  • The performance of the FASP protocol has been enhanced. Compared to prior releases, unencrypted CPU-bound transfers may see an increase of up to 100% in overall throughput; and encrypted CPU-bound transfers may see an increase in overall throughput of up to 20%.
  • Resume mode checks in ascp now use a SHA-2-based MD5 checksum algorithm by default; to configure alternative algorithms, there is a new aspera.conf option.
  • ascp now features new complete include and exclude filter options to support glob and regular expression matching, equivalent to include/exclude options of async.
  • A new FASP Manager API feature can be used to send an event when individual arguments, such as directories in persistent sessions, are completed.
  • ascp now includes a new asynchronous “in transfer” post-processing engine with Lua scripts. (This is the first version of this feature, and somewhat experimental.) A Lua interpreter engine is packaged with Enterprise Server, allowing for post-processing, validation, and authorization functions through embedded Lua scripts. Scripts execute asynchronously, and their progress is reported through a new validating state in the transfer session, without delaying completion of the file transfer or slowing the transfer pipeline.
  • Parallel (multi-session) transfers initiated from the command line can now use a URI for the filepath.
  • The <file_create_mode> option in the <file_system> section of aspera.conf is now respected when the docroot is a file URI.

Node API

  • A new Node API call returns usage data (bytes transferred in, transferred out, and total) listed by usage id.
  • The Node API now returns events for the creation, rename, and deletion of files using the Node API, in addition to file transfer events. (CIM-52)
  • A new Node API call returns verbatim the content of a file within the file size restriction set in aspera.conf.
  • The access key and token secret of a Node API user are now passed on to Aspera Central, such that ascp is run with the environment variables associated with that user.
  • SSH private key strings are now are now supported in the Node API through a new JSON element, ssh_private_key.
  • A new case-insensitive filter can return filename matches regardless of case to Aspera Files.
  • The /ops/transfers API has been improved, including new support for setting transfer rates, bandwidth priorities, and pausing/resuming/canceling active transfers.
  • Asperanoded includes improvements in the /info and / API response, such as support for content protection settings.
  • /ops token authorization now uses SHA-2 as the default checksum, rather than SHA-1.
  • The status of files and transfers can now be reported by iteration token from the Node API. For example, if the user specifies an iteration token to https://node:9092/ops/transfers?iteration_token=1234, file and transfer information since iteration_token=1234 are displayed.
  • File modification events, including delete and rename, are now logged to redis/scalekv.
  • Transfer and bandwidth statistics are self-cleaning for large numbers of sessions.
  • Default and allowed SSL ciphers have been updated to eliminate support for 3DES and to align the defaults with hardened versions.
  • Asperacentral has a new raw options capability that allows users to authorize the use of raw format ascp options by configuring aspera.conf.

Watchfolder and Aspera Watch Service

  • Watchfolder uses two new APIs:

    • asperarund: to start, stop, and manage asperawatchfolderd and asperawatchd under various user accounts.
    • access_control: to configure user access to specific instances of asperawatchfolderd and asperawatchd regardless of their system user account. See Breaking Changes for more information on this feature.
  • Support for force-send-after configuration for growing files, retrying failed drops, encryption at rest, and token authorization.
  • This release features many enhancements to the robustness of asperawatchfolderd:
    • The system ensures that a custom watchfolder aspera.conf is passed to ascp.
    • A valid and consistent docroot is verified upon startup.
    • --scan-period is now respected in creation.
    • aswatchadmin no longer hangs on removal of a watchpoint with a large number of files.
    • Archive directories are now respected.
    • Statistical counters persist after reboot.
    • asperawatchfolderd includes improved health status reporting.
    • Session cookie and tag fields are accepted and reported through management.
    • Timestamps are preserved when so configured.
  • asperawatchfolderd now initiates transfers with a destination root, allowing Watchfolder transfers to work using the Aspera upload option for Akamai storage (requires a minimum server software version on the Akamai side).
  • The API call getWatchFolderState now returns the state of asperawatchfolderd in addition to the state of the transport and state of the watch.
  • Users can now select an existing asperawatchfolderd service when creating a watchfolder.
  • The configuration of asperawatchfolderd can be updated without re-sending the remote host password.
  • Users can now authorize the use of raw format ascp options by Watchfolder transfers by enabling the new <raw_options> setting in the <watchfolderd> section of aspera.conf.
  • Watchfolders can now use token authentication for transfers.


  • Aspera introduces access key authentication for Async. Access keys provide an alternative to the security credentials of a node user or system user. Because an access key is restricted to its own storage (local or cloud), it allows access control and usage reporting to be segregated by storage. This offers significant benefits to multi-tenant service providers and enterprise installations with multiple departments. This also allows async to run on Aspera Files and for other Node v4 applications.
  • A new asyncadmin option displays file attributes (mtime, recursive mtime for directories, and checksum).
  • Pending file bytes are now reported correctly in Aspera Console during an async pull (fixed in Enterprise Server 3.6.2).
  • The new recursive mtime option enables the exclusion of directories and files older than a configured timestamp.
  • The new --delete-delay option allows the delete operations in a unidirectional sync to be delayed until the end of the synchronization.
  • Sync now preserves POSIX attributes in the event that file attributes change but file contents do not (times, UID, GID).
  • When using the --keep-dir-local or --keep-dir-remote options, locating the keep-dir under the same directory as the sync directory is no longer an error condition as long as the keep-dir has been added to the exclude list.
  • Sync has two new options for preserving timestamps: --preserve-access-time and --preserve-modification-time.
  • Sync has the following new options:
    • --scan-interval
      Run a periodic scan in async. This new option takes a time spec.

    • --local-mount-signature=signature_file
      Verify local/remote file system is mounted by the existence of this file. NOTE: Use of this feature will increase the time to synchronize deletes.

    • --pending-max=number_of_files
      The maximum number of pending files to allow. Default is 2000.

    • --compression=mode
      Specify method used to compress a file before transfer. mode can be zlib or none. The default value is none.

    • --transfer-threads=number[:size]
      Specify intervals for dedicated transfer threads. number corresponds to the number of threads used to process files smaller or equal to the specified size. If no size is specified, infinity is used as an upper bound.

    • --remove-after-transfer
      Remove source files after they are transferred correctly.

    • --scan-interval=duration
      Enable periodic scans. duration defines the interval between periodic scans. duration may be specified as DDd HH:MM:SS.mmm or NNw NNd NNh NNm NNs NNms NNus.

  • The Async library now takes a license as a parameter. If the library doesn't get a license on initialization, it can still search for one on the disk, as it does currently.

Cloud Support

  • Support for Azure storage Block Blobs with maximum file sizes up to 4.77 TB and maximum block sizes of 100 MB.
  • HDFS and Cleversafe object storage are now supported.

Other Changes

  • The pre/post variable TOKEN is no longer valid.
  • Activity bandwidth logging is no longer enabled by default.
  • The Aspera Watch Service is now automatically enabled and the <watchd>enabled</watchd> in aspera.conf is no longer necessary.


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

  • With the implementation of new inline validation options, existing users with inline validation enabled must set the validation provider to uri or lua_script. The external option has been replaced by uri and the lua option has been replaced by lua_script. To set the validation provider, run:
    asconfigurator -x "set_node_data;validation_threshold,uri"
  • When upgrading to 3.7.2, if asperawatchd or asperawatchfolderd services are being run by users other than root, the services must be stopped prior to upgrade and restarted manually following the upgrade. Services run by root are migrated automatically during installation.

    To restart the services, run the following commands for each user and service, as required:

    $ /Libary/Aspera/sbin/asperawatchd --user username
    $ /Libary/Aspera/sbin/asperawatchfolderd --user username
  • In Watchfolders, the Node API transfer account must have access control set to admin in order to create watchfolders. To update an existing Node API transfer account, run the following command:.
    $ /Libary/Aspera/bin/asnodeadmin -mu username --acl-set "admin,impersonation"

    To create a new Node API transfer account with the correct access control, run the following command:

    $ /Libary/Aspera/bin/asnodeadmin -a -u username -p passwd -x transfer_user --acl-set "admin,impersonation"
  • The way asperawatchfolderd uses docroots has changed in two ways:
    1. If no docroot and no restrictions are specified in aspera.conf, asperawatchfolderd will reject the creation of a watchfolder and return an error message similar to the following:
      ERR [Watch_folderd] Handle_create(): [err=28672, message=No docroot]

      Workaround: Specify a docroot or restrictions for the watchfolder.

    2. If the docroot of an existing instance of watchfolderd changes and asperawatchfolderd later restarts and tries to reload the watchfolderd, an error message similar to the following is returned:
      ERR [Watch_folder_pool] Synchronize(): [err=22, message=Change in docroot detected: /home/user/test/s != /home/user/home/user/test/s]

      The watchfolder must be recreated following a change in docroot.

  • Recursive counts are now disabled by default, but must be enabled in order for Aspera Files to use this feature. Workaround: Run the following command to edit the <server> section in aspera.conf such that <files_recursive_counts_workers> is set to 5:
    $ asconfigurator -x "set_server_data;files_recursive_counts_workers,5"
  • Multi-session (parallel) transfers from 3.5 clients are no longer compatible with 3.6 and newer servers. This is due to a change in how files are split and how the splitting of individual files is configured on both versions. Workaround: Upgrade the client side to 3.6 or newer.


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

ATT-207 - Transfers using AES-192 or AES-256 are incorrectly reported as using AES-128 in the GUI. (CIM-134)

ATT-109 - [Mac OS X] When a partial ascp transfer falls back to http, the transfer does not complete but the status of the transfer is shown as "completed" in Faspex.

ATT-95 (#23246) - Warnings are not generated about files skipped due to source base setting.

ATT-79 (#36276) - When the <ignore_skipped_files> setting is enabled (true) on the ES node, Console continues to show all skipped files for failed transfers on the Activity page.

ATT-76 (#36373) - In cases of a failed transfer, the files counter in session statistics is not updated with the data for skipped files.

ES-210 - Guides listed the default port for TCP as 33001. (CIM-303)

ES-161 (#35255) - When Japanese characters that include the voiced sound mark are used to name a directory in Connect Server, the following issues may occur:
  • The upload fails without an error message.
  • The download fails with the error code 43: The specified path cannot be found.

ES-62 - [Mac OS X] Connect Server displays a confusing time zone message at the top of the browser window.

WAT-286 (#30365) - On the Sync Job Detail page for pull operations, the size for pending files is reported as 0 Bytes. Transfer sizes are reported correctly after the transfer completes.

#31405 - async documentation regarding timestamp modification use is incorrect. If the checksum is "none" when a file is modified and the file size stays the same, async will not detect the change, even though the timestamp has changed.

#29474 - Pushing to S3 with the --scan-dir-rename option causes Sync to hang.

#28686 - File-splitting only works with S3.

#23888 - Sync does not trigger a transfer when only the permissions have changed (and no content has changed).


Mac: OS X 10.8, 10.9, 10.10, 10.11, macOS 10.12 (Sierra)
Browsers (for Connect Server): Safari 6-9, Firefox 27-48, Chrome 32-50


Enterprise Server 3.6.3 Release Notes (OS X)
Enterprise Server 3.5.5 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.5.4 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.5.2 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.5.1 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.4.5 Release Notes (OS X)
Enterprise Server 3.3.4 Release Notes (Windows, Linux, [OS X for Client only])


Enterprise/Connect Server

Mac OS X: AsperaEnterpriseServer-
md5: fc3388bb40ec3f4182484b2a61c99eff
sha1: f97cc8b3671dd970ff7efde2b4d79b4340c78055


Mac OS X: AsperaPointToPoint-
md5: b3758e4dc50f3011710c9a1305a4f8d5
sha1: 5efcd37a36d696b92b7efba65c72c7421f4c493f


Mac OS X: AsperaClient-
md5: 83b2670e21a45a32a07838abfa7820c7
sha1: 51cd5089ce77f63fcfbb62540c7c7bc668d2b9fe


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


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-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)

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

ES-212 - The filename is not shown in the Name or Source fields in the Transfer pane of the GUI if the transfer was initiated using the Connect Server web UI.

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 on the ES UI, it 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 installing Enterprise Server 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-57 - In the GUI after a fresh installation, initial values for Limit Download Bandwidth and Limit Upload Bandwidth are not set to system defaults.

ES-49 - [Mac OS X] the product manual doesn't open when the user clicks Help > Manual in the GUI if the Preview application is not already running. Workaround: The manual can be opened from the Finder, or by launching Preview before clicking Help > Manual.

ES-42 - When retrieving the entitlement status using alee-admin status, confusing error messages are returned even if the entitlement has been registered successfully.

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

#35952 - asunprotect cannot decrypt a re-protected file.

#34811 - The user is unable to download encrypted files with an incorrect decryption passphrase when using HTTP fallback.

#32934 - Some HTTP fallback transfers may appear to complete but then lose connection with the server and subsequently attempt to retransfer. This behavior has been observed only when the client system has an installation of the Internet accountability software Covenant Eyes, which captures the entire HTTP transmission before forwarding it to the server. If the file is large enough that this process takes longer than about 20 seconds, the server generates an inactivity timeout and cancels the session. Workaround: Reduce the probability of timeout by increasing the timeout length. This can be done by changing the Session Activity Timeout value in the HTTP Fallback tab in the server's configuration settings, or by using the asconfigurator settings, for example:
asconfigurator -x "http_server;session_activity_timeout,1200"

#32517 - Retransfer requests are unencrypted when transfers are encrypted. This can cause transfer failures in some scenarios, such as a network device dropping 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 the aspera.conf file on the server, and then copy aspera.conf to each source user.

#30690 - ascp fails with an inaccurate message—Error: failed to authenticate—when a server is configured to only accept ciphers that are no longer supported.

#28683 - docroot warning message: If global docroot is enabled, reports the root user as insecure.

#28679 - In some cases, the fallback server does not respond.

#27908 - When asperacentral has database errors, it continues to allow new transfers.

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

#27823 - The user's Faspex Server goes down with an "Transfer Server errors detected" error message. An error, "trying to read events from a parser that already reported an error before" appears. Workaround: move the central-store.db to allow re-creation.

#27056 - There is no ascmd support for server-side symlink configuration.

#27007 - When connecting to a forward proxy, Aspera clients on UNIX systems use the HTTP_PROXY and HTTPS_PROXY environment variables but these are not reported in the logs. These variables are not used in HTTP Fallback.

#25832 - Hot Folders: When creating or modifying Hot Folders, some controls in the File Handling tab do not work correctly: The option for resuming incomplete files does not work, but is still necessary to enable options for checking whether files at the source and files at the destination are the same. Selecting Compare File Attributes only checks whether the files are the same size. Selecting Compare Sparse File Checksums actually compares full checksums.

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

#24671 - DB logger logs each file twice when the transfer is between a source and destination that are on the same node.

#24390 - HTTP fallback upload operations fails with the message "Failed to create HTTP session on server!".

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

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

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

#22741 - When the --file-checksum feature is enabled, transferring ES 3.3.3 to ES 3.3.0, the file is corrupted at the destination with additional characters appended to the end.

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

#21604 - Extremely large socket buffer value causes overflow, resulting in an error when creating a UDP socket.

#20576 - Target Rate must be in the range 0 – 100 if TargetRateAsPercentage is yes; however, setting a target rate greater than 100 does not return an error. (Note that rate percentage is a deprecated feature.)

#16390 - Unicode filenames appear incorrectly in pre-processing and post-processing email notifications.


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

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

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

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

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

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

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

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

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

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

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

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

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

Node API

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 bytes transferred for the files_completed value is correct.

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

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

NODE-136 - ascp reports the wrong source paths for a Faspex direct upload from a local computer to an ATP cluster.

#35421 - Shares console becomes unresponsive during a deletion command that takes a long time to run.

#33374 - The 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. (Symbolic link capability is only available on local storage.)

#33229 - Users cannot browse a file on cloud storage 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 have completed.

#33202 - Node API allows the user to move a file in cloud storage into a directory with a /files/rename request.

#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 filename 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 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, the Node API does not return the correct file modification time.

#29078 - When an access key is created using the standard node user authorization, the access key inherits that node user and its associated system user. Afterwards, 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 - asperanoded fails to delete a directory name containing backslashes. Workaround:
  1. Stop node.
  2. At the command prompt, issue the command ulimit -S -n 2048.
  3. Restart node in the same command-line shell (the limit is shell-specific).
  4. Send in the same /files/delete request as you did before; the head and everything in it will be removed.
Note: Prior to the command in Step 2 above, you can find out the current limit by running the following command: ulimit -a | grep "open files".

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

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

#22619 - In the Node API, file searches follow symbolic links.

#20002 - Inconsistent behavior regarding symbolic link following: /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.

#18659 - Searching with very long pathnames (over 520 characters) results in an "insufficient buffer space" error.

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

Watchfolder and Aspera Watch Service

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

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

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

WAT-169 - When using top_level_dirs drop detection 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 will be 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 setting when running the license switch ascp -A.


ES-50 - When using 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-362 (#24812) - 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-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 syncing 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 describing the file name and path.

#27621 - Sync conflicts due to handling of hidden, temporary, or transient files (such as those created by Microsoft Office products).

#25913 - Aspera Drive attempts to sync a file that is still uploading to Shares, resulting in a file error.

#25631 - When transferring from Windows to Mac using preserve-acls=native and remote-preserve-acls=native, ACL data is saved as xattr. Workaround: Do not use the native setting when transferring or syncing across platforms.

#25467 - async cannot be used with cloud storage.

#24805 - For a synced directory, while all of the files and subdirectories under the source folder will have ACL preserved at destination, the ACL for the source folder itself will not be replicated to the remote destination folder.

#23954 - When the --preserve-acls or --preserve-xattrs option is used, async will 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 - Console does not draw a line between the involved nodes for an async transfer. This issue occurs when using two managed nodes with two interfaces on two different networks.

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

#22044 - asyncadmin reports all sessions 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 can't 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 is due to a bug in SQLite.

#18913 - Cancelled or stopped jobs are reported as completed in fasp_sessions.status.

#18780 - 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, therefore failing to trigger an error message. Any session options specified (such as -l or -a) after the string of characters not preceded by a "-" or "--" are also ignored. The session will still run, using the default values, without notifying the user that the new settings have not been applied.

#13761 - If filenames contain "\" or new line, async will try to transfer but fail, causing the internal transfer queue to become full and the synchronization to stall (or hang after all the other files have completed).

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

#9126 - Async logs events at a fast rate. The log destination must have room for large log files.

Cloud Support

TRAP-40 - Downloads of many (100+) large (100+GB) files from cloud storage fail with the message: OutOfMemoryError: GC overhead limit exceeded. Workaround: Increase the memory allowed to the JVM running trapd by increasing the value of MAX_JAVA_MEM in /opt/aspera/etc/init.d/ If the machine is large, also decrease the shared memory by an equivalent amount by uncommenting and setting the option system.buffer-pool.memory=value in /opt/aspera/etc/trapd/

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

#30324 - During an ascp upload to cloud storage, if a mid-file read failure occurs on the sending computer (which is very 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 cancelled with Ctrl+C or other means.

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

#29038 - 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. Using overwrite=always does not overwrite the file.

#26281 - At approximately 100 (or a similarly high number) of concurrent uploads to s3, intermittent transfer session failures 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.

#25636 - To use a larger chunk size to transfer big 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.

#23876 - On S3, when always overwrite is set, files are missing at the destination.

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

#22905 - On S3, when copying a file 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.

#22848 - On S3, uploading a file to a non-existent destination path, and without the -d option, creates the destination path anyway.

#17243 - An S3 download fails when a filename contains square brackets or a caret.


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.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk