HP NonStop SSL Reference Manual page 125

This error indicates a failure to set up a FTPC proxy with the shown parameter values. Check that these values are
correct, and that no other process does already listen on port <port>. Watch for other message which come along
with this one for additional hints on why the FTPC setup failed.
Error when processing cipher suite list, empty list. At least one cipher suite has to be given.
This error indicates that an empty value has been given for the CIPHERSUITES parameter. Make sure your
command line does not (e.g. due to a wrong comma) include such an empty CIPHERSUITES entry.
Error when importing cipher suite list, given string <givenCipherList> was invalid (No existing cipher
suite found for token <givenCipherListEntry>)
This error indicates that an invalid cipher entry <givenCipherListEntry> was given in the value of the
CIPHERSUITES parameter. Make sure your CIPHERSUITES entries are according to the manual and are separated
by a comma each.
Cannot init EXPANDSecureProxy, SRCIPADDR/DESTIPADDR in invalid format: <detailed reason>
This error indicates that the SRCIPADDR/DESTIPADDR parameters were given in an invalid format. This can e.g.
happen when running in IPMODE IPv4 but specifying IPv6 an address. Please see the <detailed reason> for the
detailed error reason.
ACTIVE FTP mode not supported in run mode FTPCPLAIN, set parameter PASSIVE to TRUE
This error indicates an unsupported runmode/parameter combination which occurs when an FTP proxy is started in
runmode FTPCPLAIN and the parameter PASSIVE was set to FALSE. Either remove set the parameter PASSIVE
to true, or in case you don't need to run plain connections use the regular FTPC run mode.
Multi-tunnel configuration not valid for EXPANDS mode
This error occurs when you try to specify a multi tunnel configuration by passing multiple entries in at least one of
PORT/TARGETPORT/TARGETHOST (unused parameters for EXPANDS anyway). Remove any of
PORT/TARGETPORT/TARGETHOST to resolve the error condition.
Invalid (Multi-)Proxy configuration given: <detailed reason>
This error indicates that one or more values given in parameters PORT/TARGETPORT/TARGETHOST are invalid.
The detailed reason at the end of the message should give you enough information about how the error condition can
be resolved.
Invalid or inconsistent IP Address given for INTERFACE or TARGETINTERFACE: <detailed reason>
This error indicates that at least one of the values for INTERFACE respectively TARGETINTERFACE was invalid.
The detailed reason at the end of the message should give you enough information about how the error condition can
be resolved.
IP address <IP> given for parameter <param> invalid in the corresponding IPMODE(=<ipmode>)
This error occurs when an IP address was given for param <param> that does not correspond to the IPMODE. This
can occur if an IPv6 address was specified in IPMODE IPv4. To resolve the error condition check which runmode is
intended and specify the IP address in parameter <param> accordingly.
Host name resolution for <hostname> "<interface param>" failed: <detailed reason>
This error occurs when a hostname was given for at least one of the values of INTERFACE respectively
TARGETINTERFACE, and the hostname could not be resolved to an IP address. Please check the hostname and
your DNS settings. Alternatively specify the IP address instead of the hostname.
Invalid IPMODE specified, ODBC/MX does only support IPv4
This error occurs when an IPMODE other than IPv4 was specified in run mode ODBC/MX. Although ODBC/MX
supports IPv6 starting with release H06.26/J06.15, NonStop SSL currently only supports ODBCMXS mode for
IPv4.
HP NonStop SSL Reference Manual
Appendix • 125