Release Notes: IBM Aspera Enterprise Server 3.6.3 for zLinux

Product Release: August 8, 2016
Release Notes Updated: August 8, 2016


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


zLinux on S/390, 64-bit: Red Hat Enterprise Linux Server release 5.11 (Tikanga)


Enterprise Server

zLinux s390: aspera-entsrv-
md5: f037fcf27c69d15e8140852e66bd687f
sha1: 2aef50f219f0f2c20286d6e6154bef243692e0f6


(This release contains tickets created from two tracking systems; thus there are two different formats for ticket identifiers.)

ASDR-624 - Adding an ES node account to Drive fails with errors stating: Error verifying host and Service discovery failed. No services discovered for host. The log displays the following errors:
LOG ERROR: HTTP POST failed: Couldn't resolve host name (CURLcode: 6)

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

#35453 - Parallel transfers started with the Aspera ascp Client on ES 3.5—transferring to ES 3.6 with the -C option—fail with the error Session Stop (Error: Session initiation failed).

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

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

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

#32892 - The xattrs metafile not deleted when a file with xattrs is overwritten by a file without xattrs. This is observed when a file with xattr (created on a Mac) is uploaded to a Linux server with the xattrs preservation options on the command line. For example:
ascp --preserve-xattrs=native --remote-preserve-xattrs=metafile 
After the original file is deleted, and then re-recreated (without xattrs) on Mac, when the user uploads the file to Linux, the.aspera-meta file is not deleted as expected.

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

#32883 - An async bidirectional session fails to complete. Workaround: Manually end the async process.

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

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

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

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

#32080 - An error message spams the log file used by asperanoded each time the console attempts 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.

#31791 - The user is unable to transfer files with the file extension .aspx. Workaround: Edit the resume_suffix setting in the aspera.conf file on the server, and then copy aspera.conf to each source user.

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

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

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

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

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

#28939 - If command line ascp neglects to specify a destination host, then the failed transfer (with the error message 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.

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

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

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

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

#27879 - always_set_home does not work if the user's home directory does not exist.

#27823 - The user's Faspex Server goes down with a 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.

#27311 - Sync: 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.

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

#27007 - Aspera clients on UNIX systems use the HTTP_PROXY and HTTPS_PROXY environment variables when configured to use a FASP proxy; it does not report this in the logs. These variables are not used in HTTP Fallback.

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

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

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

#25042 - In the server-side aspera.conf, the none option for file checksum reporting is no longer supported; only md5 and sha1 are supported. The any option means allow the checksum format to be whichever format the client requests. On the client side, the none option is still available, as a command-line option. A setting of any on the client side results in an error with the message ascp: unknown file checksum type any.

#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 need to be specified in order for the target side of the pull to apply the acls.

#24549 - Drag-and-drop with the Linux version of the desktop client is not supported. Attempting a drag-and-drop upload does nothing. Attempting a drag-and-drop download causes the mouse cursor to display a plus sign, suggesting incorrectly that the feature is available.

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

#23954 - Sync: 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.

#23583 - Certain option values for asperacentral job submission are case-sensitive.

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

#23400 - [Linux] Beginning with async 1.5, the user is permitted to synchronize the root directory.

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

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

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

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

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

#22618 - The behavior of the Node API paths filter changed with Enterprise Server 3.4. It now returns only the directory matching the filter, not the directory's content.

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

#21978 - ES is unable to view logs as superuser.

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

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

#20617 - The SOAP API does not return an error when invalid values are passed into any of a number of parameters. Instead of returning an error, a transfer is either created with a default value, or the bad value is passed to ascp where it will fail.

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

#20347 - Syncing from Linux to Windows when there are many levels of subdirectories may result in an error.

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

#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 - Sync database logging: 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.

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

#18530 - FASP and Sync now accept and verify SSH remote-host keys.

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

#17231 - On Linux, an async pull does not restore access time on the source side.

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

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

#13833 - The asyncadmin -M option fails to delete a file in a directory which has a name containing Japanese characters.

#13826 - Attempting to run a command with -N set a string with Japanese characters results in the following error:
[********] ERROR: -N/--name needs a regular name argument
[stopped ]
Failed. -N/--name needs a regular name argument

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

#11550 - If preserve_attributes is set to none on the server side, when downloading a single file with the -p option, the file has an invalid atime value.

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

#8620 - Enterprise Server for Linux fails to install if the dependency perl-CGI is not installed. Workaround: Install Perl (CGI), then rerun the Enterprise Server installation. For example, to install Perl (CGI) on RHEL, run yum install perl-CGI.

#8538 - If a file fails to be renamed from .partial after it transfers, the transfer is still considered successful and the session will continue (with additional files being renamed successfully). The receiver side logs an error message, but no error is logged on the sender side. Successful transfers that were not properly renamed from .partial should be manually renamed.

#8412 - Backslashes in filenames is not supported.

#6448 - When your regional and language options are set to language standards and formats that do not use "." to represent the decimal point, values are displayed inconsistently using both "." and the native character to represent the decimal point.


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Powered by Zendesk