• No results found

NSSL Log Messages and Warnings

In document NonStop SSL Server (NSSL) (Page 130-133)

This section lists all log and warning messages issued by NSSL.

Startup Messages

This section contains messages which are displayed during startup and which are of an informational nature only.

comForte SWAP server version <NSSL version number> version_info

Appears right after startup and notifies about the version umber of the NSSL

using openssl version 0.9.7 - see http://www.openssl.org);

Notifies about the OpenSSL version bound to the NSSL

config file: '<filename>

Displays the name of the configuration file the NSSL has been started with

runtime args: '<list of runtime args>

If the NSSL has been started with runtime args instead or in addition to the a config file or TACL params those args are being displayed.

log level is <log level>

Informs about the log level the NSSL has been started with

your system number is <system number>

The system number of the NSK system on which the NSSL has been started. This number must be the same as the system number given in the license file.

license file check OK, <name of license file>

Notifies about the successful license check. Default license file name in LICENSE

starting collecting of random data

Notifies about the process of collecting random data.

Informs about completion of collecting random data. <number> is the number of collected bytes.

no HTTPZIP archive configured

Informs that the NSSL has been started without a HTTPZIP archive being configured. The HTTPZIP archive is a means to allow the NSSL although running (as a Web server) under Guardian to support Unix like directory structures i.e. real URLs..

couldn't open HTTPZIP archive <filename>, error: <error number>

Warning to inform that the HTTPZIP archive identified by filename could not be opened for the reasons specified by error number. Error number is a GUARDIAN file system error.

no HTTPZIP archive will be used

This message occurs in cases were no HTTPZIP archive has been configured for the NSSL. In this case all resources requested by the browser must reside in the NSK subvolume where the NSSL resides or in the NSK subvolume given by the param HTTPBASE.

using HTTP ZIP archive <filename>

Displays the filename of the HTTPZIP archive.

sysnum wild card not allowed with unlimited expiration date

The license check failed. Please contact Crystal Point.

sysnum wild card not allowed with expiration date more than 6 months in advance

The license check failed. Please contact Crystal Point.

DEFINE =TCPIP^PROCESS^NAME has value '%s'"

Notification about which TCP/IP process name is being used

parameter SUBNET will be ignored

Notification that the value of the SUBNET parameter will be overridden by the DEFINE =TCPIP^PROCESS^^NAME

TCP/IP process is <process name>

Notification about the TCP/IP process used for the communication in the current context of this message.

parameter SUBNET was evaluated

Notification that a SUBNET param has been found and will be used to determine the TCP/IP process

starting HTTPS server on port <port number>, default dir <directory name>

Notification that the NSSL is starting in HTTPS mode listening on port given by port number and defaulting to the subvolume given by the param HTTPBASE. If the latter param ist not set the default dir is the one where the NSSL resides and <default directory> in this message is left empty.

Notification that the NSSL has been started as a Web server in plain HTTP mode listening on port given by port number and defaulting to the subvolume given by the param HTTPBASE. If the latter param ist not set the default dir is the one where the NSSL resides and <default directory> in this message is left empty.

plain-to-plain proxy started on target host <hostname or ip address>, target port <port number>, source port <port number>

Notification that the NSSL has been started in plain-to-plain mode (i.e. no encryption takes place on neither side). Target host, target port and source port involved in the plain-to-plain session are given in the message.

secure-to-plain proxy started on target host <hostname or ip address>, target port <port number>, source port <port number>

Notification that the NSSL has been started in a mode accepting connections for secure data and connecting to the target host on target port for plain data.

plain-to-secure proxy started on target host <hostname or ip address>, target port <port number>, source port <port number>

Notification that the NSSL has been started in a mode accepting connections for plain data and connecting to the target host on target port for secure data.

FTP server proxy started on target host <hostname or ip address>, target port <port number>, source port <port number>

Notification about the NSSL beint started in FTPS mode and connecting to target host, on target port while accepting connections on source port.

FTP client proxy started on source port <port number>

Notification about the NSSL beint started in FTPC mode and accepting connections on source port.

dumping configuration: <config setting>

Displays the settings of the configuration params

loading Server Certificate from file <filename>

Notification that the server certificate is being loaded from the file given by filename

loading next Certificate Chain file from file <filename>

Notification that the next of a sequence (chain) of signing certificates are being loaded by the NSSL.

Fingerprint of Root CA is <MD5 fingerprint>

Notification about the MD5 calculated fingerprint of the root certificate. If fingerprint checking is activated on the client side, this fingerprint must be preconfigured there.

loading private key from file <filename>

Notification about the server private key (see param SERVKEY) being loaded from the file identified by filename.

adding CA Certificate Chain Level <curr number>/<max number> <filename>

Notification about how many certificates the CA certificate chain contains, which of these certificates are currently processed and what the filename of this is.

Connection closed by remote client

This log message will be issued any time a remote client disconnects unexpectedly. In most cases (especially when running in TELNETS mode), this log message can be safely ignored.

In document NonStop SSL Server (NSSL) (Page 130-133)

Related documents