Chapter 106 SSI (Storage Server Interface) Messages

Table of Contents

Event Messages 1 and 2
Event Message 3
Message 4
Messages 5 through 10
Other Error Code

The messages described in this chapter are sent by the Storage Server Interface (SSI) subsystem. The subsystem ID displayed by these messages includes SSI as the subsystem name.

These messages are arranged in numerical order, first by event number, then by error code for events that could report different codes.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

Event Messages 1 and 2

These are the causes, effects, and recovery actions for conditions that generate messages 1 and 2.

ZSSI activated: Initiation started.

Cause $ZSSI has started.

Effect $ZSSI is establishing a connection with the Communications Server Interface (CSI) server.

Recovery Informational message only; no corrective action is needed.

ZSSI available: Initiation completed.

Cause Communications with the Communications Server Interface (CSI) have been successfully established.

Effect $ZSSI has been established as a remote procedure call (RPC) server.

Recovery Informational message only; no corrective action is needed.

Event Message 3

When the Storage Server Interface (SSI) encounters a transient error, various versions of message 3 display, with different reasons and recovery actions for each error condition. All instances of event message 3 are formatted like this:

Transient fault: error-code-text

3 (11)

Can't locate queue Q_id queue_id, Member: member_id

`queue_id`	is the identifier of the $ZSSI connection queue.
`member_id`	is the ID of the queue member it is trying to locate.

Cause $ZSSI cannot find specific members in an internal queue.

Effect $ZSSI ignores the request. $ZSSI does not find a specific member in an internal queue.

Recovery None of the queue members are dropped because they are older than the connection queue aging time (defined by the CSI_CONNECT_AGETIME environment variable). However, if this error occurs more frequently than the connections queue aging time, contact your service provider. (Provide your service provider with the EMS log that contains the message.)

3 (12)

Can't delete Q-id queue_id, Member: member_id

`queue_id`	is the identifier of the $ZSSI connection queue.
`member_id`	is the ID of the queue member it is trying to delete.

Cause $ZSSI cannot delete a message in an internal queue.

Effect $ZSSI ignores the request and does not delete a message in an internal queue.

Recovery This event should not occur during normal operation. If it occurs frequently, contact your service provider. Provide your service provider with the EMS log that contains the message.

3 (14)

Invalid procedure number.

Cause $ZSSI received a packet from the network interface, but it is not using one of two valid procedure numbers.

Effect $ZSSI discards the message.

Recovery This is a programming error. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide.

3 (16)

Cannot reply to RPC message.

Cause The call to the svc_freeargs ( ) function failed. This is an error in the network connection between the NonStop Kernel and the file server.

Effect $ZSSI cannot reply to a remote procedure call (RPC) message.

Recovery Depending on the errors found in the EMS log, reestablish communication with the portmapper and RPC. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide.

3 (19)

Invalid network protocol.

Cause An unsupported network protocol has been passed to the csi_rpccalln ( ) function.

Effect $ZSSI terminates.

Recovery This is a $ZSSI programming error. Contact your service provider.

3 (21)

Can't get queue status Q-id: queue_id, Member: member_id

`queue_id`	is the identifier of the $ZSSI connection queue.
`member_id`	is the ID of the queue member for which $ZSSI is seeking status information.

Cause $ZSSI cannot get status information about a message in an internal queue.

Effect $ZSSI ignores the request and does not get status information.

Recovery This event should not occur during normal operation. If it occurs frequently, contact your service provider and provide the EMS log that contains the message.

3 (22)

Can't add member to queue Q-id: queue_id.

queue_id

is the identifier of the $ZSSI connection queue.

Cause $ZSSI cannot put the ZSVR return address or the Communications Server Interface (CSI) return address on its queue. Possible causes are:

Insufficient configured memory. The process was initiated with a fixed amount of memory and that memory was insufficient.
Insufficient disk space. Even if an allowance was made for extensible memory, the swap volume does not have sufficient space to accommodate the needs of the process.
Overload of CPU. Too many demands were made of the CPU, causing it to use up internal resources (such as memory allocated for time-list elements (TLEs)).

Effect The request fails.

Recovery Recovery depends on the cause of the error:

If the configured memory was insufficient, the PMAP_MAXENTRIES define (default 1000) in the portmapper might need to be increased.
If disk space was insufficient, move the data-swap volume to a disk with more available space.
If a CPU overload occurred, the process might need to be run on another CPU that is not heavily loaded, or the system might need to be reconfigured to increase the amount of system resources (such as system data space for TLEs and process control blocks (PCBs).

3 (23)

Queue cleanup Q-id: id_num, Member: mem_num

`id_num`	is the queue ID number.
`mem_num`	is the queue member number.

Cause $ZSSI has purged a process from its connective queue. $ZSSI routinely searches for processes older than the current process and purges them.

Effect None

Recovery Informational message only; no corrective action is needed.

3 (24)

Undefined message detected: discarded.

Cause $ZSSI encountered a message from the $ZSVR, or the NI network interface that cannot be delivered because of an incorrect message format or $ZSSI failure.

Effect The message is discarded.

Recovery This is a programming error of the client software that tried to communicate with $ZSSI. For more information, see the specified server’s manual. If the error recurs, contact your network or UNIX-based server support representative.

3 (27)

Message for unknown client discarded.

Cause $ZSSI detected a message from the Communications Server Interface (CSI) for an invalid or unknown client.

Effect The message for the unknown client is discarded.

Recovery If the error is repeated, contact your service provider.

3 (34)

Invalid communications service.

Cause Invalid information was received for communications.

Effect $ZSSI ignores the request or terminates.

Recovery Check the EMS log for additional errors. If the EMS log shows that additional errors occurred, reconnect to the portmapper or remote procedure call (RPC) service.

3 (35)

XDR message translation failure.

Cause The $ZSSI External Data Representation (XDR) translation routines cannot translate a message completely because it was damaged. This error might be due to an error in the client network or the client application.

Effect $ZSSI tries to translate the message up to the point where the error was detected. If the header part of the message is translatable, the message is forwarded. Otherwise it is dropped.

Recovery If the error is not caused by an error in the client network, report the problem to your service provider. Provide the EMS log for analysis.

3 (36)

Cannot decode to free memory allocated by XDR.

Cause The call to the svc_sendreply ( ) function failed. An error occurred in the network connection between the NonStop Kernel and the file server. XDR is Sun Microsystems’s External Data Representation communications syntax.

Effect $ZSSI cannot reply to a remote procedure call (RPC) message.

3 (44)

Duplicate packet from network detected: discarded. Remote IP address: address, Process-ID: ident, Sequence number: num, ID: id

`address`	is the remote internet address.
`ident`	is the process ID number.
`num`	is the sequence number in the queue.
`id`	is the ID of the queue member.

Cause $ZSSI has received a duplicate packet from the Communications Server Interface (CSI).

Effect $ZSSI automatically drops the duplicate packet.

Recovery Informational message only; no corrective action is needed.

3 (45)

Network timeout.

Cause $ZSSI cannot connect to the network.

Effect If this message occurs more than three times, $ZSSI automatically retries the communication.

Recovery Informational message only; no corrective action is needed.

3 (46)

Unexpected failure detected: errno = errno.

errno

is the C run-time error number.

Cause $ZSSI received an error it did not expect.

Effect $ZSSI terminates.

Recovery For an interpretation of the errno value, see the C/C++ Programmer’s Guide.

3 (47)

Invalid command, requestnum

requestnum

is the request number.

Cause $ZSSI received a request packet from $ZSVR with an unrecognizable request number.

Effect $ZSSI ignores the request.

Recovery This is a programming error of the client software that tried to communicate with $ZSSI. If the error recurs, contact your network or UNIX-based server support representative.

3 (48)

Invalid type.

Cause The Storage Server Interface (SSI) received a packet from the network interface with either an unrecognizable type in the IPC_HEADER portion of the Communications Server Interface (CSI)_REQUEST_HEADER or an unrecognizable IDENTIFIER type in the message packet. A problem exists with the server software that tried to communicate with the SSI.

Effect $ZSSI ignores the request.

Recovery If the error recurs, contact your network or UNIX-based server support representative.

3 (49)

Invalid connection queue aging time defined_time, default:default-time seconds substituted.

`defined_time`	is the assigned time.
`default_time`	is the time substituted and used by $ZSSI.

Cause The $ZSSI connection queue aging time is not a usable number. The time is defined by the defined_time parameter in the obey file that starts $ZSVR.

Effect $ZSSI substitutes and uses the default time.

Recovery Correct the defined_time parameter in the obey file and restart $ZSVR.

3 (50)

Invalid location type: number

number

is the invalid value in the location type field.

Cause The Communications Server Interface (CSI) received a request packet from $ZSSI with an unrecognizable location type specified in the message_data portion of the request.

Effect $ZSSI ignores the request.

Recovery This is a programming error of the server software that tried to communicate with $ZSSI. If the error recurs, contact your network or UNIX-based server support representative.

3 (52)

Invalid version number, number.

Cause The version number in the message header is not supported.

Effect $ZSSI discards the message.

Recovery This is a programming error. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide.

3 (54)

Validation warning: csi_header.csi_syntax

`csi_header`	is the header description for the Communications Server Interface (CSI).
`csi_syntax`	is the communications syntax being used for the CSI.

Cause $ZSSI notifies you that the CSI is not communicating using the Sun Microsystems External Data Representation (XDR) communications syntax.

Effect If this message occurs more than three times, $ZSSI automatically retries the communication.

Recovery Informational message only; no corrective action is needed.

3 (55)

Validation warning: csi_header.csi_proto

`csi_header`	is the header description for the Communications Server Interface (CSI).
`csi_prot`	is the communications protocol being used for the CSI.

Cause $ZSSI notifies you that the CSI is not communicating using the transmission control protocol (TCP) or the user datagram protocol (UDP).

Effect If this message occurs more than three times, $ZSSI automatically retries the communication.

Recovery Informational message only; no corrective action is needed.

3 (500)

Unexpected status.

Cause $ZSSI received status information that it did not expect.

Effect The message is discarded.

Recovery Informational message only; no corrective action is needed.

3 (501)

Non-successful status returned from CSI.

Cause The Communications Server Interface (CSI) cannot successfully complete the request.

Effect None

Recovery Informational message only; no corrective action is needed.

Message 4

When the Storage Server Interface (SSI) encounters a fatal error, various versions of message 4 display, with different reasons and recovery actions for each error condition. All instances of event message 4 are formatted like this:

Fatal fault: error-code-text

4 (2)

Create of RPC TCP service failed, Address: address, Port: port

`address`	is the remote internet address.
`port`	is the port number of the client for which a connection was tried.

Cause The RPC call to the svctcp_create ( ) function failed.

Effect Remote procedure call (RPC) transmission control protocol (TCP) service is not created.

Recovery For recovery information, see the DSM/Tape Catalog User’s Guide.

4 (3)

Can't register RPC TCP service.

Cause The call to the svc_register ( ) function failed.

Effect Remote procedure call (RPC) transmission control protocol (TCP) service is not registered.

Recovery For recovery information, see the DSM/Tape Catalog User’s Guide.

4 (8)

Initiation of $ZSSI failed.

Cause The cause is reported in a prior EMS message.

Effect $ZSSI initiation failed.

Recovery Depends on the cause of the error. Check the recovery heading under the appropriate EMS message.

4 (9)

Creation of connect queue failed.

Cause $ZSSI cannot initialize the internal address connection queue. Possible causes are:

Insufficient configured memory. The process was initiated with a fixed amount of memory, and that memory was insufficient.
Insufficient disk space. Even if an allowance was made for extensible memory, the swap volume does not have sufficient space to accommodate the needs of the process.
Overload of CPU. Too many demands were made of the CPU, causing it to use up internal resources (such as memory allocated for time-list elements (TLEs)).

Effect Connect queue is not initialized. $ZSSI terminates with a fatal fault.

Recovery Recovery depends on the cause of the error:

If the configured memory was insufficient, the PMAP_MAXENTRIES define (default 1000) in the portmapper might need to be increased.
If disk space was insufficient, move the data-swap volume to a disk with more available space.
If a CPU overload occurred, the process might need to be run on another CPU that is not heavily loaded, or the system might need to be reconfigured to increase the amount of system resources such as system data space for TLEs and process control blocks (PCBs).

4 (10)

Creation of network output queue failed.

Cause $ZSSI could not create the network output queue that is used for messages between the Communications Server Interface (CSI) and $ZSSI. Possible causes are:

Insufficient configured memory. The process was initiated with a fixed amount of memory, and that memory was insufficient.
Insufficient disk space. Even if an allowance was made for extensible memory, the swap volume does not have sufficient space to accommodate the needs of the process.
Overload of CPU. Too many demands were made of the processor, causing it to use up internal resources such as memory allocated for time-list elements (TLEs).

Effect Network output queue is not created. $ZSSI terminates with a fatal fault.

Recovery Recovery depends on the cause of the error:

If the configured memory was insufficient, the PMAP_MAXENTRIES define (default 1000) in the portmapper might need to be increased.
If disk space was insufficient, move the data-swap volume to a disk with more available space.
If a CPU overload occurred, the process might need to be run on another CPU that is not heavily loaded, or the system might need to be reconfigured to increase the amount of system resources such as system data space for TLEs and process control blocks (PCBs).

4 (12)

Can't delete Q-id queue_id, Member: member_id

`queue_id`	is the identifier of the $ZSSI connection queue.
`member_id`	is the ID of the queue member it is trying to delete.

Cause $ZSSI cannot delete a message in an internal queue.

Effect The message is discarded. $ZSSI does not delete a message in an internal queue.

Recovery This event should not occur during normal operation. If it occurs frequently, contact your service provider. Provide your service provider with the EMS log that contains the message.

4 (13)

Operating system error error_num.

error_num

is the operating system error number.

Cause $ZSSI has encountered an operating system error. This message indicates a problem with the operating system itself, not with $ZSSI.

Effect $ZSSI terminates

Recovery For corrective action for the error number, see Appendix B.

4 (17)

RPC TCP client connection failed: rpc_error_msg, Address: address, Port: port

`rpc_error_msg`	is a detailed error message generated by the remote procedure call (RPC) service itself. In most cases, this message is “Program number not registered,” which indicates that either the Communications Server Interface (CSI) or $ZSSI is not running.
`address`	is the address of the client host.
`port`	is the port number of the client where a connection was tried.

Cause The attempted transmission control protocol (TCP) connection is not possible. This is an error in the client system network.

Effect RPC TCP client connection is not made. $ZSSI terminates.

Recovery Restart or reestablish communications with the NonStop Kernel TCP/IP service, the portmapper/RPC service, or both.

4 (20)

Queue creation failure.

Cause $ZSSI cannot create either its connection queue or the network queue. Possible causes are:

Insufficient configured memory. The process was initiated with a fixed amount of memory, and that memory was insufficient.
Insufficient disk space. Even if an allowance was made for extensible memory, the swap volume does not have sufficient space to accommodate the needs of the process.
Overload of CPU. Too many demands were made of the CPU, causing it to use up internal resources (such as memory allocated for time-list elements (TLEs)).

Effect $ZSSI terminates

Recovery Recovery depends on the cause of the error:

If the configured memory was insufficient, the PMAP_MAXENTRIES define (default 1000) in the portmapper might need to be increased.
If disk space was insufficient, move the data-swap volume to a disk with more available space.
If a CPU overload occurred, the process might need to be run on another CPU that is not heavily loaded, or the system might need to be reconfigured to increase the amount of system resources such as system data space for TLEs and process control blocks (PCBs).

4 (32)

Cannot send message to NI: discarded.

Cause The NI’s (Network Interface’s) communications mechanism cannot accept a message from the $ZSSI.

Effect $ZSSI terminates

Recovery Depending on the errors found in the EMS log, reestablish communication with the portmapper and remote procedure call (RPC). If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide.

4 (35)

XDR message translation failure.

Effect $ZSSI tries to translate the message up to the point where the error was detected. If the header part of the message is translatable, the message is forwarded. Otherwise it is dropped.

Recovery If the error is not caused by an error in the client network, report the problem to your service provider. Provide the EMS log for analysis.

4 (38)

Undefined hostname.

Cause $ZSSI encountered an undefined client host on startup.

Effect $ZSSI terminates

Recovery Check that the NonStop and UNIX-based server system host names are defined for both system configurations: either a host file or the domain_name resolver process. Check that the NonStop server and the UNIX-based server are assigned the appropriate host names. To define the NonStop server’s host name, use the Subsystem Control Facility (SCF) command ALTER,HOSTNAME, name.

4 (43)

Invalid network time-out value.

Cause The calculated network time-out value is not a usable number.

Effect $ZSSI terminates

Recovery Check parameter values in the obey file used to start $ZSVR and make any necessary changes.

4 (46)

Unexpected failure detected: errno = errno.

errno

is the C run-time error number.

Cause $ZSSI received an error that it did not expect.

Effect $ZSSI terminates

Recovery For an interpretation of the errno value, see the C/C++ Programmer’s Guide.

4 (52)

Invalid version number, number.

number

is the invalid version number.

Cause The version number in the message header is not supported.

Effect The message is discarded.

Recovery This is a $ZSSI programming error. If the error is repeated, contact your service provider. For more information, see the DSM/Tape Catalog User’s Guide.

4 (205)

Creating socket socket-name failed on error-number.

Cause $ZSSI cannot initialize the socket.

Effect $ZSSI terminates

Recovery Recovery depends on the cause of the error.

4 (500)

Unexpected status.

Cause $ZSSI received status information that it did not expect.

Effect The message is discarded.

Recovery Informational message only; no corrective action is needed.

Messages 5 through 10

ZSSI deactivating: Termination Started.

Cause $ZSSI termination started.

Effect None

Recovery Informational message only; no corrective action is needed.

ZSSI not available: Termination Completed.

Cause $ZSSI termination completed successfully.

Effect None

Recovery Informational message only; no corrective action is needed.

I/O error: error, filename: filename.

Cause An I/O error occurred. This is most likely due to an Open Error 12, which is a file-system error indicating that the specified file is in use.

Effect The specified file could not be opened.

Recovery Correct the indicated file system error.

Unrecognized system message on $RECEIVE, code: message-code.

Cause An unrecognized system message was received.

Effect Depends on the message code.

Recovery Review the message code to see if any action is needed.

RPC error: message-details.

Cause An RPC error occurred.

Effect Depends on the message details.

Recovery Review the message details to see what action is needed.

SLR error: message-details.

Cause An SLR socket error occurred.

Effect Depends on the message details.

Recovery Review the message details to see what action is needed.

Other Error Code

This is another error code that might be indicated in SSI event messages.

(1)

Unmapped previously registered RPC service.

Cause $ZSSI notifies you that a remote procedure call (RPC) number previously assigned to $ZSSI still exists.

Effect $ZSSI unmaps the number and remaps to a new one as a normal part of the initiation. $ZSSI is initiated.

Recovery Informational message only; no corrective action is needed.