Q: I can connect and list files with HSI, but file transfers fail. Why?
A: This problem is usually caused by one of two things:
1. The wrong host interface is being used.
By default, HSI uses the network interface associated with the hostname command.
There are two ways to override this:
A. Set the HPSS_HOSTNAME environment variable, in the HSI wrapper script,
to the network interface name or IP address that HSI should send to the movers
for inbound data connections.
For example,
export HPSS_HOSTNAME=clienthost32-e.mgleicher.us
or
export HPSS_HOSTNAME=132.255.12.25
B. Create a "PFTP Client Interfaces" stanza in the HPSS.conf file.
The HPSS.conf file is found in the directory whose path is obtained from the
HPSS_CFG_FILE_PATH environment setting.
Links: HPSS.conf file settings [To be added]
2. A firewall is blocking inbound connections from the HPSS movers.
If this is the case, there are two options:
a. Open a port range to allow HPSS movers to connect, and set the HPSS_PFTPC_PORT_RANGE
environment variable to the range of ports:
export HPSS_PFTPC_PORT_RANGE=ncacn_ip_tcp[start-end]
For example, if a port range from 25000-25999 has been opened,
export HPSS_PFTPC_PORT_RANGE=ncacn_ip_tcp[25000-25999]
Note that the syntax for this setting was adopted from the Distributed Computing Environment
(DCE) from the early days of HPSS. In HPSS 7.4, this syntax will be simplified.
b. If a port range cannot be opened, use the HSI "firewall" command to force store-and-forward
transfers, using a private data socket that is opened on the HSI Gateway Server and connected to
by the HSI client. Note that firewall mode is not currently available for HTAR.
Q: Why are File Transfers slow ?
A: This problem is usually caused by one or more of the following:
- Network tuning option sare not set in HPSS.conf and/or the host kernel
- Wrong host network interface is being used for the transfer
- The buffer size is too small for the HSI or HTAR client
- The HPSS Mover buffer size is configured too small
- The Virtual Volume block size configured for the HPSS storage class is too small
or too large to support effective striping
- The local filesystem is unable to keep up with HPSS
Q: Why does HSI return exit code 0 even when there's an error during a session?
A: This may be a wrapper script problem. HSI is coded to return an exit code any time an error occurs, although it
is possible that there is a bug that causes this not to happen. However, the HSI (and HTAR) wrapper scripts that were originally posted on this web site, and were in use at several sites, substituted exit code 0 for EX_USAGE (64)
errors, and also then issued a warning message:
"###WARNING hsi returned non-zero exit status."
if a non-zero exit code was set.
EX_USAGE is commonly set for common errors such as unrecognized or missing options, and the original
thought was to avoid issuing the above warning message for interactive sessions where the user made
a typing mistake, etc. However, this also could result in setting exit code 0 and causing problems for
scripts that depended on knowing that an error had occurred. The check for EX_USAGE errors has been
removed from the HSI/HTAR wrapper scripts on this web site.