Chapter 82 RPC (Remote Procedure Call) Messages

The messages in this chapter are sent by the remote procedure call (RPC) subsystem. The subsystem ID displayed by these messages includes RPC as the subsystem name.




	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.

subjname: rpc-version started

`subjname`	is the process name of the portmapper process that has been started.
`rpc-version`	is the product number and product version of the remote procedure call (RPC) subsystem used by the portmapper process.

Cause A portmapper process has been started.

Effect None.

Recovery Informational message only; no corrective action is needed.

File system error error from procedure procerr, FILE filename errortext

`error`	is the file-system error.
`procerror`	is the name of the procedure that returned the specified error.
`filename`	is the name of the file where the error occurred.
`errortext`	is a text description of the meaning of the specified error.

Cause The most likely cause of this event is that the device on which the file or process exists is inaccessible. (The device is down or the network connection is lost.)

Effect If the error occurred on a file or process that is critical to the portmapper process, the process abends; otherwise, the subsystem records the error and proceeds as usual. If the error occurred on $RECEIVE, a serious logic problem is indicated. For descriptions of the file-system errors, see the Guardian Procedure Errors and Messages Manual.

Recovery Contact your HP representative and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a saveabend file, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Initialization failure: initerr errarg

initerr

indicates the reason why the portmapper process failed to initialize.

Value	Meaning
1	The portmapper process was unable to locate the parent process to execute remote procedure call (RPC) requests.
2	An illegal argument list was specified.
3	More than one BACKUPCPU value was specified.
4	An invalid BACKUPCPU value was specified.
5	More than one TCP/IP process was specified.
6	An invalid TCP/IP process name was specified.
7	The TCP/IP process does not exist.
8	The process specified as the TCP/IP process was not a TCP/IP process.
9	More than one collector value was specified.
10	An invalid collector device name was specified.
11	The specified collector device does not exist.
12	The device specified for the collector device is not a valid collector device.
13	The user starting the portmapper process is not a super-group user (255, `n`).

errargc

contains the argument or process that caused the error.

Cause The portmapper process failed to initialize.

Effect The portmapper process does not start.

Recovery Based on the values returned for the specified error, correct the problem and restart the portmapper process.

sockfile: Socket Library Routine error error: errortext; Procedure: wait-type slr; Socket type: socktype, Remote IP addr: ipaddr

sockfile

is the name of the file corresponding to the socket where the socket library routine error occurred.

error

is the socket library routine error number.

errortext

is a text description of the meaning of the specified error.

wait-type

indicates whether the failed operation was waited or nowaited:

1	The failed operation was waited.
2	The failed operation was nowaited.

slr

is the socket library routine that returned the specified error.

socktype

is the type of socket being used.

Value	Meaning
1	A transmission control protocol (TCP) stream socket
2	A user datagram protocol (UDP) datagram socket
3	A raw socket

ipaddr

is the IP address of the remote socket in dotted decimal format.

Cause A call to the Transmission Control Protocol/Internet Protocol (TCP/IP) socket library routine (SLR) failed or returned an error. For descriptions of NonStop Kernel TCP/IP error lists, see the TCP/IP Management Programming Manual.

Effect A connection or a datagram may have been lost. If the TCP/IP process was inaccessible (file-system error 201 or 250), the portmapper process records the event, closes all open sockets, and then periodically tries to reestablish communications with the TCP/IP process for a configurable period of time.

If communications are reestablished, the portmapper process reopens its sockets and proceeds as usual. If after the configurable period of time, communications have not been reestablished, the portmapper process abends. All other errors are considered fatal and cause the portmapper process to log the event and abend.

Recovery Operator intervention is required to restart the process. For descriptions of file-system errors, see the Guardian Procedure Errors and Messages Manual. For more information on the TCP/IP configuration, see the TCP/IP Configuration and Management Manual. For more information on the portmapper configuration, see the DSM/Tape Catalog User's Manual.

sockfile Remote Procedure Call rpc failed, error error: errortext

`sockfile`	is the name of the file corresponding to the socket where the remote procedure call (RPC) library routine error occurred.
`rpc`	is the value of the remote procedure call (RPC) in the error list.
`error`	is the error number returned by the RPC routine.
`errortext`	is a text description of the meaning of the specified error.

Cause A procedure in the RPC library failed or returned an error.

Effect The portmapper drops the request that resulted in this error. If the Transmission Control Protocol /Internet Protocol (TCP/IP) process was inaccessible (file-system error 201 or 250), the portmapper process records the event, closes all open sockets, and then periodically tries to reestablish communications with the TCP/IP process for a configurable period of time. If communications are reestablished, the portmapper process reopens its sockets and proceeds as usual. If after the configurable period of time, communications have not been reestablished, the portmapper process abends.

Recovery Operator intervention is required to restart the process. For descriptions of file-system errors, see the Guardian Procedure Errors and Messages Manual. For descriptions of TCP/IP error lists, see the TCP/IP Management Programming Manual. For more information on the TCP/IP configuration, see the TCP/IP Configuration and Management Manual. For more information on the portmapper configuration, see the DSM/Tape Catalog User's Manual.

proctype process creation of objectfile failed. Procedure error: create-error; file system error: error, errortext

`proctype`	is either BACKUP or REMOTE, indicating whether the portmapper was trying to start a copy of itself as a backup process or as a co-process to handle a remote broadcast request.
`objectfile`	is the name of the file for the portmapper program file.
`create-error`	is the error number returned by the NEWPROCESS procedure.
`error`	is the file-system error number corresponding to create-error.
`errortext`	is a text description of error.

Cause The portmapper received a NEWPROCESS error while trying to start a backup process or a co‑process. The portmapper uses a co-process to issue remote procedure calls (RPCs) on behalf of RPC broadcast requests.

Effect If backup process creation fails, the portmapper continues to run without a backup. If co-process creation fails, the RPC broadcast request is dropped.

Recovery Recovery depends on the NEWPROCESS error returned. For descriptions of NEWPROCESS errors and file-system errors, see the Guardian Procedure Errors and Messages Manual.

Unable to communicate with procname

procname

is the name of the process with which the portmapper cannot communicate.

Cause The portmapper process cannot communicate with the Transmission Control Protocol/Internet Protocol (TCP/IP) process.

Effect If the TCP/IP process was inaccessible (file-system error 201 or 250), the portmapper process records the event, closes all open sockets, and then periodically tries to reestablish communications with the TCP/IP process for a configurable period of time. If communications are reestablished, the portmapper process reopens its sockets and proceeds as usual. If after the configurable period of time, communications have not been reestablished, the portmapper process abends.

Recovery Recovery depends on the cause of the error:

If the portmapper process could not communicate with its backup process, and the connection was lost due to a processor failure, reload the failed processor. When the portmapper process detects that the process has been reloaded, it automatically tries to restart its backup process.
If the portmapper process could not communicate with the TCP/IP process, restart or reestablish communication with the TCP/IP process.
If the connection was lost due to a network connection failure, restore the network connection to an operational state.

Backup process in CPU cpu died because reason

`cpu`	is the processor number where the backup process was running.
`reason`	is a text description of the reason why the backup process failed.

Cause The primary portmapper process has stopped unexpectedly or abended, or the backup processor has gone down.

Effect If this message occurs because the backup process stops or abends, the primary portmapper automatically tries to create a new backup process. If the message occurs because the backup CPU has failed, the primary portmapper tries to create a new backup process after the backup CPU has been reloaded.

Recovery Informational message only; no corrective action is needed. However, if repeated, unexplained failures of the backup process occur, contact your HP representative and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a saveabend file, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

This product requires Guardian 90 XF Release C00 or later.

Cause The portmapper process was started on an incompatible version of the operating system.

Effect The process terminates.

Recovery Restart the process on a suitable host processor.

Memory full, mem-err

mem-err

indicates the reason for the memory shortage.

Cause The possible causes of this event 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 TLEs).

Effect The request that encountered the memory-full condition is rejected with the appropriate error.

Recovery Use the RPCINFO program to display the contents of the portmapper table, then use the -d option of rpcinfo to delete entries that are no longer in use. Stopping and restarting the portmapper clears all entries from the table.

Internal Error progerr: progerrtext - Object file: fname, Timestamp: bindtime, Procedure: entrypt, S: s-reg, P: p-reg, E: env-reg, L: l-reg.

`progerr`	contains a code identifying the program error that occurred. The values returned are for HP internal use only.
`progerrtext`	is a text description of the meaning of progerr.
`fname`	is the program file name of the running process.
`bindtime`	is the object file’s BIND timestamp.
`entrypt`	is the procedure entry point label where the error occurred.
`s-reg`	is for HP internal use only.
`p-reg`	is for HP internal use only.
`env-reg`	is for HP internal use only.
`l-reg`	is for HP internal use only.

Cause An internal error has been detected that either should not occur or is unrecoverable. This event should not occur during normal operation.

Effect The portmapper process abends.

Recovery Contact your HP service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a saveabend file, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Unexpected I/O completion on file: filename

filename

is the name of the file where the unexpected I/O completion occurred.

Cause The portmapper process detected the unexpected completion of an I/O operation in the main processing loop. This indicates a serious internal programming error. This event should not occur during normal operation.

Effect The unanticipated I/O completion probably has no effect on the operation of the portmapper process and is dropped.

Recovery Contact your HP service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a saveabend file, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Maximum number of abends exceeded. Process procname aborted.

procname

is the name of the backup portmapper process that abended.

Cause Repeated attempts to start the backup process have failed. The portmapper process detected repeated backup process failures that are not because of processor module failures.

Effect No further attempts to create a backup are made until the problem is corrected.

Recovery Recovery depends on the cause of the backup failure, which is usually a resource failure or a home terminal failure.

Resources failures usually cause a NEWPROCES process to fail. In this case, the portmapper generates Remote Procedure Call (RPC) operator message 6. For the cause of backup creation failure, see the error number reported by that message.
The portmapper is a C program, and the C run-time library always tries to open the stdin, stdout, and stderr files during process initialization. If these files are directed to a nonexistent file (such as a TELNET window that no longer exists), the resulting open failures cause the process to abend. The IN, OUT, and STDERR files of the portmapper must be directed to a permanent terminal device when the portmapper is started.
If the backup process is starting then abending, run the portmapper with SAVEABEND ON, then examine the saveabend file generated by the backup failure.

Unexpected message received from procname, \node,cpu,pin, I/O Type: iotype, User: paid

`procname`	is the name of the process that sent the message.
`node`	is the node number of the process that issued the message.
`cpu`	is the processor number of the process that issued the message.
`pin`	is the process ID number of the process that issued the message.
`iotype`	is the type of unexpected message that has been received: WRITE, READ, or WRITEREAD.
`paid`	is the process access ID number of the process that issued the message.

Cause A message was received from a process that does not have a current open of the portmapper process. This event can occur when the portmapper process is restarted in a CPU and has the same PIN as a previously running process that was opened by the process that issued the message.

Effect The portmapper process rejects the message with a file-system error 60 and posts another read.

Recovery Informational message only; no corrective action is needed.

Unexpected system message on $RECEIVE,code: msgcode

msgcode

is the message ID of the system message.

Cause The portmapper process received a system message that it did not expect or did not recognize. A system message for which there is currently no corresponding processing logic was read by the portmapper process. This event should not occur during normal operation.

Effect The unanticipated system message probably has no effect on the operation of the portmapper process and is dropped.

Recovery Contact your HP service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a saveabend file, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Remote cproc failure, clnt_stat error: errortext; ProgramL prognum Version version, Remote IP addr ipaddr

`rpcproc`	is the name of the remote procedure call (RPC) library routine that returned a clnt_stat error.
`error`	is the clnt_stat error number.
`errortext`	is a text description of the meaning of error.
`prognum`	is the RPC program number.
`version`	is the RPC program version.
`ipaddr`	is the IP address in dotted decimal notation of the target of the RPC that failed.

Cause The portmapper co-process received a client status error from an RPC library routine, most likely the result of an error in the RPC service being targeted.

Effect The RPC broadcast request that resulted in this error is dropped.

Recovery Informational message only; no corrective action is needed.

Invalid request to PORT MAPPER, procedure p From Remote IP addr d.d.d.d

p

is the name of one of the procedures in the portmapper remote procedure call (RPC) protocol, or is the procedure number in the request if the number does not correspond to a valid portmapper RPC procedure:

PMAPPROC_NULL	PMAPPROC_GETPORT
PMAPPROC_SET	PMAPPROC_DUMP
PMAPPROC_UNSET	PMAPPROC_CALLIT

d.d.d.d

is the internet address in dotted decimal notation of the host that sent the invalid request.

Cause The portmapper received an invalid RPC request from the indicated host. The request is probably invalid because of in-transit data corruption of the request or because of programming errors in the RPC client program running on the specified host.

Effect The invalid request is rejected.

Recovery Informational message only; no corrective action is needed. Occasional, random occurrences of this message may be caused by transient data errors. However, if this error occurs frequently:

Find the contents of the RPC request causing this event by using a local area network (LAN) analyzer to trace requests being sent to the portmapper. If the request is valid on the LAN, report this to your system manager as a malfunction in the portmapper or transmission control protocol/internet protocol (TCP/IP) software. If the request is invalid on the LAN, determine whether the message is being corrupted as it is transferred through gateways and routers or if the client software on the originating host is generating an invalid request.
Contact your HP representative and provide all relevant information:
- Descriptions of the problem and accompanying symptoms
- Details from the message or messages generated
- Supporting documentation such as Event Management Service (EMS) logs, trace files, and a saveabend file, if applicable
If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Function function failed with error: err, Detail: error-text

`function`	is the name of the function call or Guardian procedure call that failed.
`err`	is the error number returned by the failed function call.
`error-text`	is a detailed description of the error of the failed function call.

Cause An error is returned by the specified function call. Examine the error details to know more about the cause of the error.

Effect The effect depends on the severity of the error.

Recovery If the error is not severe, the process recovers itself; otherwise, the process abends. Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details of the message(s) generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a SAVEABEND file, if applicable

If your local operating procedures require contacting the HP Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.