Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.7.2 for Linux and Windows

Product Release: January 12, 2017

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

NEW FEATURES

General

  • 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)
  • A new option for Hot Folders in pull mode, Transfer source directory contents only, downloads only the contents of a directory and not the directory itself, stripping the prefix from the filepath of each source file.
  • 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.

ascp

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

A4

  • Log size can now be configured in aspera.conf so that logs of long ascp4 transfers of many files (millions) are not overwritten before the session completes.
  • ascp4 can now transfer to destinations with a UNC path set for the docroot.
  • The path of a docroot in cloud storage is not required for ascp4 transfers.
  • Exclude patterns are now supported in ascp4 transfers, including those with cloud storage.
  • A4 documentation is now included in the Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client guides.
  • New options --delete-before and --delete-after are available in beta version.

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.

Watchfolder and Aspera Watch Service

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

Cloud Support

  • Support for Azure storage Block Blobs with maximum file sizes up to 4.77 TB and maximum block sizes of 100 MB.

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.

BREAKING CHANGES

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"

ISSUES FIXED IN THIS RELEASE

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-180 - The source and destination reported by ascp is not consistent between the server and the client. When sending files with ascp using a file-pair list, the reported "sources" are the destinations instead, and only "sources" in odd lines (1, 3, 5, etc.) are reported. When receiving files from a server with a docroot, the server reports the source including the docroot, whereas the client reports the relative path.

ATT-174 - ascp fails to download and decrypt files that were uploaded and encrypted using HTTP fallback.

ATT-171 - ascp may hang on the server (cloud storage) when the client reports an error. (CIM-150)

ATT-169 - ascp may hang if one of several threads accessing the queue NEW_Q is missing a mutex.

ATT-168 - The Connect Server web UI displays a text error if the browser language is set to Korean, Japanese, or Chinese.

ATT-162 - Encryption at Rest aborts the process if FIPS is enabled.

ATT-158 - ascp logs SINK_POST_COMPLETE_Q if the logging level is set to log.

ATT-148 - aes-256 is not a valid entry for transfer_encryption_allowed_cipher in aspera.conf. (CIM-131)

ATT-137 - A4 does not support more than one exclude (-E) option.

ATT-136 - [Windows] ascp4 hangs when a large (>1 million small files) transfer session is stopped and restarted from the GUI.

ATT-132 - ascp crashes when a cloud storage transfer is canceled from the Connect Server GUI while asynchronous functions are pending. (CIM-232)

ATT-110 - Partial files are not resumed after an HTTPS fallback transfer is interrupted if server-side encryption at rest is enabled. (CIM-103)

ATT-96 - Downloading Faspex packages may fail when server-side encryption is enabled and the client is using encryption-at-rest.

ATT-87 - If a single file fails due to permissions during an A4 transfer session, the entire session fails.

ATT-84 (#26517) - [Linux] ascp4 does not support values besides skip for the --symbolic-links option.

ATT-71 - ascp4 fails when the destination docroot is set to a UNC path.

ATT-47 - ascp4 fails if a negative mtime is specified for --exclude-older-than and --exclude-newer-than.

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

ES-197 - The File Filter Pattern List dialog in the File Handling tab of the GUI does not set a filter list correctly.

ES-184 - When the user selects a file or folder in the left pane, then clicks File >New, the Hot Folder menu option is disabled (grayed-out).

ES-165 - The Redis DB version is not updated when the application is uninstalled and reinstalled without deleting the installation folder. (CIM-199)

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-150 - asperacentral reports the cipher as AES-128, even if AES-192 or AES-256 is being used. (CIM-135).

ES-43 - A Node API /ops/transfers query does not return Faspex transfers from an ATP cluster to Faspex On Demand.

ES-18 (#33673) - Transferring symbolic links on Windows results in the creation of a zero-byte file at the destination instead of the expected copying of the target of the symlink. Documentation now clarifies that symbolic links are skipped on Windows.

NODE-156 - Node users are not retained after ATC clusters are upgraded from version 3.6.2 to 3.7.1 and --db update is run before ScaleKV has stabilized.

NODE-155 - Retries may timeout before the default number of retries can be run, depending on the transfers_retry_duration set in aspera.conf.

NODE-130 - asperanoded sometimes crashes when shared folders are deleted using Files or Drive.

WAT-435 - [Windows] Hotfolder filepaths are limited to 260 characters. Files with longer filepaths are skipped.

WAT-434 - A Watchfolder can't be created if the docroot contains a UNC path. (CIM-300)

WAT-433 - [Windows] Watchd is unable to monitor a UNC path. (CIM-300)

WAT-410 - For large syncpair files which are slow to load, the Point-to-Point UI sometimes displays the error message, "Error writing hot folder configuration file file_path: destination 'file_path' already exists."

WAT-400 - A Watchfolder may not restart after the docroot is added or changed if the absolute_source_dir is not compatible with the docroot or if raw_options are set in the configuration but not enabled in aspera.conf. The Watchfolder is shown in an error state but cannot be updated or deleted.

WAT-380 - [Windows] Slow storage devices can result in long scan times for Hot Folders in push mode, which eventually causes FASP transfers to fail.

WAT-374 - When <write_allowed> is set to false on a Console managed node without Watchfolders, Console returns a node error and simple/smart transfers from the node fail.

WAT-356 - [Windows] Hot Folders stop working if there is a system clock error (clock is running backwards or is not synchronized in a multi-core system). For a solution, see the Aspera knowledgebase article https://support.asperasoft.com/hc/en-us/articles/216128758. (CIM-128)

WAT-349 - aswatchfolderadmin is unable to query created watchfolders.

WAT-333 - [Windows] async sessions started with the Windows Task Scheduler are not stopped if asyncadmin -T is run by a user other than the user running the current sessions.

#33742 - Node API /files/browse cannot retrieve the preserved modification times for ascp uploads. (fixed as of 3.6.1)

#32080 - An error message spams the log file used by asperanoded each time Console to check the node for the status. A second error can occur when the end user fills in a docroot but doesn't have a valid system user; this results in an error that also spams the log file used by asperanoded.

#33298 - [Windows] The Enterprise Server installer fails to install with the /quiet option. Workaround: For instructions, see https://support.asperasoft.com/hc/en-us/articles/216127388.

#28820 - The following operations attempted in a Limelight directory fail or are unacceptably slow: copy/paste file and rename file.

#26477 - ascp4 does not support exclude patterns (-E).

#24549 - [Linux] Drag-and-drop transfers in the desktop client are not supported.

SYSTEM REQUIREMENTS

Windows:  2008 R2, 2012 R2, 7, 8, 10
Browsers (for Connect Server clients): Microsoft Edge, Firefox 27-48, Chrome 32-50

Linux 64-bit and 32-bit: Ubuntu 12-15, RHEL 6-7, CentOS 6-7, SLES 11-12 Kernel 2.4 or higher and libc version GLIB 2.3.4+, Debian 6-7, Fedora 16-20
Browsers (for Connect Server clients): Firefox 27-48, Google Chrome 32-50

PACKAGE INFORMATION

Enterprise/Connect Server

Linux 64-bit (deb): aspera-entsrv-3.7.2.137926-linux-64.deb
md5: 89aa3eccb17721b63d224ed2e28ac3f6
sha1: 1781fa6524c23f00a21a5bdfde195585ab6fe973
Linux 64-bit (rpm): aspera-entsrv-3.7.2.137926-linux-64.rpm
md5: 514329af7463a110ef3fcd478584000d
sha1: eeb8d3e18500ed6d7ce8326d4343b67e6e5175d9
Windows: AsperaEnterpriseServer-ML-3.7.2.137926-win-v100-32.exe
md5: 35822f5993c1caa3cfae83c644e2a694
sha1: b314454e2a84e387e696c3dac0b83de0724b3413

Point-to-Point

Linux 64-bit (deb): aspera-scp-p2p-3.7.2.137926-linux-64.deb
md5: 373627c38dd2924f93cf3287b2e1686c
sha1: cad136e26b7476a725c1e4081e16d5dc89f4ed3f
Linux 64-bit (rpm): aspera-scp-p2p-3.7.2.137926-linux-64.rpm
md5: 8d5fa1e53a4670ada565a09982a0d112
sha1: 42df87a8dccbd96725f27df9eaaeb733b09e946e
Windows: AsperaP2P-ML-3.7.2.137926-win-v100-32.exe
md5: 112fdce5b763dfcb2c15968a49e383dc
sha1: bdb4dd3b09851c2733d7501914fef13d97a4a982

Client

Linux 64-bit (deb): aspera-scp-client-3.7.2.137926-linux-64.deb
md5: 0ba78682fb18cf24e956aee0436bef40
sha1: 15183fd0a917db0bc681cf6d0a4cf0c117d3751c
Linux 64-bit (rpm): aspera-scp-client-3.7.2.137926-linux-64.rpm
md5: 0db3b3d7626cd42768892ac300f2161a
sha1: 7d38ff65f5bab7e94e4425b502563519d4a1544d
Windows: AsperaClient-ML-3.7.2.137926-win-v100-32.exe
md5: dc85f59595fe11b25451a39b5b225f29
sha1: a66eb3f3c4e0ab6247d964c508cda70128e380a9

KNOWN ISSUES

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

General

ES-171 - [Windows] When transferring files from a server in the GUI, the destination pane is not automatically refreshed to show the downloaded files.

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-145 (#36083) - [Windows] On non-English operating systems, two File Handling tabs are displayed in the GUI, one in English and one in the language of the operating system.

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-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-102 (#35857) - [Linux] On CentOS 7.x, the GUI may not start unless there is data in the clipboard.

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-69 - [Windows] In the GUI, Chinese characters overlap in some Configuration settings.

ES-67 and 68 - [Windows] In the GUI, all Chinese characters are displayed as question marks when previewing mail templates in text format, and as square boxes in HTML format.

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

#30082 - [Windows] When the upload of a source file to the remove server fails, no error message appears in the UI.

#28683 - asp-check.sh docroot warning message: If global docroot is enabled, asp-check.sh 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.

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

#26618 - The ascmd process does not exit properly on newer versions of SLES (SUSE Linux Enterprise Server).

#26048 - [Windows] If the Nimbus theme is applied to the GUI, multiple files cannot be selected by holding Shift or Control.

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

#21978 - [Linux] ES is unable to view logs as superuser unless a functional browser is installed.

#21629 - Connect Server aspera-dirlist.pl 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.

ascp

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.

ATT-134 - [Windows, Linux]asdelete and ascp --delete-before-transfer commands initiated from Windows machines fail to delete files named with ASCII characters (< | ? * > : " \ ) on Linux machines.

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

ES-96 (#33091) - [Windows] Downloading files or folders that have names that end in a trailing space fail.

#35010 - If the source path in an ascp transfer is a file 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.

#30231 - [Windows] If a pre-post script includes a path that contains ".." and the client is running on Windows, ascp fails with the following message:
Cannot open -e pre-post command: Unknown error

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

A4

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

ATT-238 - The log file does not rotate correctly if the log size is set to more than 2200 MB in aspera.conf.

ATT-208 - Symbolic links are copied when ascp4 is run with --symbolic-link=skip.

ATT-191 - [Linux] Symbolic links are not updated on the destination when the symbolic link option is follow (the default value if none is set) or copy.

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

ATT-37 - ascp4 hangs 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 uploading many small files (for example, 1 million 4 byte files) to S3 storage.

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

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

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

#34322 - ascp fails to authenticate SHH with a large banner file size (approximately 2000 bytes) on CentOS 7.2.

#29613 (Windows) and ATT-44 (Linux) - Timestamps are not preserved on top-level directories.

#26484 - Proxy is not supported.

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.

NODE-183 - [Windows] If redisd and noded are not running, launching asperanoded hangs and asperaredisd is not launched.

NODE-177 - [Linux] ascp transfers and asperanoded may fail when trying to transfer many (thousands) of small files because the Redis db exceeds available disk space. Workaround: Increase the maximum file descriptor from the default of 1024 to a larger value, such as 1000000, 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.

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-175 - [Windows] On 32-bit Windows, a file watch is limited to 300,000 1 kb files.

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.

Sync

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-377 (#27391) - A continuous async session configured to follow symlinks will not sync a symlink file after it has been modified.

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

WAT-355 (#34793) - [Windows] Hard-linked files are not resynchronized. A file that is a hard link to another file is kept in sync until the original file is modified, then only the original file is 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) - 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 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.

#28887 - When a file or directory is moved using the --exclude command in Sync continuous mode, the old file or directory is not removed from the remote side.

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

#25915 - When the sync function is set to continuous, overwriting an existing file on the initiating node may result in the deletion of the previous version of the file on the responding node. Workaround: Perform the sync manually to recreate the deleted file.

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

#24780 - Both --preserve-acls and --remote-preserve-acls must be specified in order for the target side of the pull to apply the acls.

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

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

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

#20767 - -R log dir creation from Linux to Windows with spaces in the path will only get as far as 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 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.

#13826, #13827, #13833 - [Windows] Limited support for Unicode filenames on Windows: The user creates in a directory with a name containing Unicode characters (for example, Japanese), and then creates a file in that directory. The following errors may occur:
  1. Running with an -N set to a string with non-English characters (such as Japanese) causes an error message.
  2. After performing a sync, the UI displays an inaccurate directory name and path separator.
  3. After syncing, using the asyncadmin -M option does not allow the user to delete the file from the database.

#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/asperatrapd_init.sh. 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/trap.properties.

#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, asperatrapd_init.sh. 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.

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.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk