The following errors are returned by Transmission Control Protocol (TCP) as the
32-bit integer "PMERR" parameter in calls to IPCCHECK. They
are also found in the "PARM" field of the TCP Statistics, PM
Deactivated and PM Deactivated with Error logging entries.
NOTE: The Network Transport is technically not part of network services;
it is a subsystem of the NS links. However it is included here because it is
available to the user.
MESSAGE: NO ERROR
Level: 0
CAUSE:IPCCHECK has been called when no PMERR
has occurred. This message is also returned when a connection or socket is
closed at the local user's request.
ACTION: None.
MESSAGE: WAIT FOR REPLY
Level: 1
CAUSE: The operation is pending. A reply message will
be received when the operation has been completed.
ACTION: None.
MESSAGE: NO DATA SENT
Level: 2
CAUSE: TCP was unable to send any of the requested data
on a partial send request.
ACTION: Either wait for the connection to become writable
and then retry the send, or do a waited send.
MESSAGE: END OF URGENT DATA
Level: 10
CAUSE: The data received ends at the urgent data boundary.
ACTION: None. For notification purposes only.
MESSAGE: MORE URGENT DATA
Level: 11
CAUSE: The most recent urgent data boundary has not yet
been reached.
ACTION: None. For notification purposes only.
MESSAGE: GRACEFUL RELEASE
Level: 20
CAUSE: The connection has entered either simplex-in or
simplex-out mode.
ACTION: None. For notification purposes only.
MESSAGE: SHUTDOWN COMPLETE
Level: 21
CAUSE: The graceful release shutdown for the connection
has been completed. The connection has been released.
ACTION: None. For notification purposes only.
MESSAGE: IPC SHUTDOWN COMPLETE
Level: 22
CAUSE: The connection has been terminated by IPC.
ACTION: None. For notification purposes only.
MESSAGE: FIN BEFORE OPEN
Level: -10
CAUSE: TCP has had an internal error which has caused it to
process an inbound FIN packet before the open handshake with IPC was
complete.
ACTION: This is an internal error. See Appendix
A "Submitting a CR" of this manual. A protocol level trace of TCP
header information will enhance resolution of this defect.
MESSAGE: LOOPBACK FRAGMENTATION
Level: -11
CAUSE: A message for a loopback connection in message
mode was fragmented.
ACTION: This is an internal error. See Appendix
A "Submitting a CR" of this manual. A protocol level trace including
buffer and message level tracing will enhance resolution of this
defect.
MESSAGE: Network Type Manager (NWTM) Error
Level: -12
CAUSE: A call to a Network Type Manager procedure returned
an error status.
ACTION: Enable class 2 logging for NS Transport if not previously
enabled. Locate matching log instance for Network Type Manager Error. Error
message will indicate class 2, subsystem 3, entity TCP, location 100xx.
Parameter is NWTM error returned. (Sign bit set indicates error,
not set indicates warning.) Consult NWTM error documentation if
available, submit an CR with this information if necessary.
MESSAGE: SEND MESSAGE (Ports) ERROR
Level: -13
CAUSE: A call to a port send message procedure returned
an error status.
ACTION: Enable class 2 logging for NS Transport if not previously
enabled. Locate matching log instance for send message error. Error message
will indicate class 2, subsystem 3, entity TCP, location 101xx. Parameter
is ports error returned. (Sign bit set indicates error, not set indicates
warning.) Consult MPE/iX operating system error documentation if available,
submit an CR with this information if necessary.
MESSAGE: CONNECTION ENTRY ALLOCATION FAILED
Level: -20
CAUSE: TCP was unable to allocate a connection entry.
Potential reasons include running out of memory space for resident
data structures, table management failure, or TCP internal error.
ACTION: Enable class 2 logging for NS Transport if not
previously enabled. Locate matching log instance for resource error
if possible. Error message will indicate class 2, subsystem 3, entity
TCP, location 102xx. Parameter is table management error returned.
(Sign bit set indicates error, not set indicates warning.) Consult
MPE/iX operating system error documentation if available, submit
an CR with this information if necessary.
MESSAGE: CONNECTION ALREADY EXISTS
Level: -21
CAUSE: An attempt was made to open a connection which
already exists.
ACTION: The connection attempt used a set of local and
remote socket numbers (sap) and local and remote IP addresses which
were identical to the set in use by a currently functioning connection.
If you are connecting from a user socket, open a new local socket
or allow transport to choose a random sap in the connect call. If
you are connecting using transport chosen random saps, the original
connector must have marked the local socket for immediate reuse.
In this case, retrying the connect should succeed.
MESSAGE: SOCKET ALLOCATION FAILED
Level: -30
CAUSE: TCP was unable to allocate a socket entry. Potential
reasons include running out of memory space for resident data structures,
table management failure, or TCP internal error.
ACTION: Enable class 2 logging for NS Transport if not
previously enabled. Locate matching log instance for resource error
if possible. Error message will indicate class 2, subsystem 3, entity
TCP, location 102xx. Parameter is table management error returned.
(Sign bit set indicates error, not set indicates warning.) Consult
MPE/iX operating system error documentation if available, submit
an CR with this information if necessary.
MESSAGE: SOCKET ALREADY EXISTS
Level: -31
CAUSE: An attempt was made to open a socket with a TCP
sap number which is already in use by a currently open socket.
ACTION: Close the original socket.
MESSAGE: INCONSISTENT IPC STATE
Level: -40
CAUSE: A TCP operation was attempted which conflicts
with expected (IPC/BSD sockets) operation in this state.
ACTION: This is an internal error between TCP and the
upper layer protocol (IPC or BSD Sockets). You should submit an
CR on this defect. Please include the nature of the call being made,
and some indication of the current connection state. If possible
please include a copy of the program and the input which caused
the error to aid resolution of the problem.
MESSAGE: IPC PROTOCOL VIOLATION
Level: -41
CAUSE: A TCP operation was attempted which is in direct
violation of (IPC/BSD sockets) /TCP interface rules.
ACTION: This is an internal error between TCP and the
upper layer protocol (IPC or BSD Sockets). You should submit an
CR on this defect. Please include the nature of the call being made,
and some indication of the current connection state. If possible
please include a copy of the program and the input which caused
the error to aid resolution of the problem.
MESSAGE: RECEIVE REPLY WITHOUT DATA
Level: -42
CAUSE: A receive reply call was made on a TCP connection;
however, there was no data pending at the time.
ACTION: This is an internal error between TCP and the
upper layer protocol (IPC or BSD Sockets). You may wish to submit
an CR for this defect. Please include the nature of the call being
made, and some indication of the current connection state. If possible
please include a copy of the program and the input which caused
the error to aid resolution of the problem.
MESSAGE: RECEIVE REPLY WITHOUT MESSAGE
Level: -43
CAUSE: A receive reply call was made on a TCP connection
in message mode; however, there were no messages pending at the time.
ACTION: This is an internal error between TCP and the
upper layer protocol (IPC or BSD Sockets). You may wish to submit
an CR for this defect. Please include the nature of the call being
made, and some indication of the current connection state. If possible
please include a copy of the program and the input which caused
the error to aid resolution of the problem.
MESSAGE: MESSAGE QUEUE FULL
Level: -44
CAUSE: TCP was unable to process a send because it has
run out of message queue elements.
ACTION: This is an internal error between TCP and the
upper layer protocol (IPC or BSD Sockets). You may wish to submit
an CR for this defect. Please include the nature of the call being
made, and some indication of the current connection state. If possible
please include a copy of the program and the input which caused
the error to aid resolution of the problem.
MESSAGE: DATA SENT AFTER SHUTDOWN
Level: -45
CAUSE: An attempt was made to send data after a simplex-in
or graceful release lingering shutdown call had been executed.
ACTION: This is an internal error between TCP and the
upper layer protocol (IPC or BSD Sockets). The upper layer protocol
should circumvent any further sends before they reach TCP. You may
wish to submit an CR for this defect. Please include the nature
of the call being made, and some indication of the current connection
state. If possible please include a copy of the program and the input which
caused the error to aid resolution of the problem.
MESSAGE: DATA SENT AFTER SHUTDOWN
Level: -50
CAUSE: Data was received on a connection after a shutdown call
with how = "graceful release now" (available only in BSD sockets) had been
executed.
ACTION: The remote connection half should not be sending data
after the local side has issued a "graceful release now shutdown." This is
an application timing issue. The application needs to coordinate the
connection shutdown or the local side should do a "simple-in shutdown" and
continue to receive until the remote graceful release notification is
received.
MESSAGE: NETWORK SHUTDOWN
Level: -60
CAUSE: A Netcontrol shutdown was issued. A connection or sockets
may have been shutdown due to the network shutdown; or an operation may
have been denied because a network shutdown is in progress.
ACTION: Restart the network to be able to establish new
sockets and/or connections.
MESSAGE: NETWORK NOT STARTED
Level: -61
CAUSE: An operation was denied because a NETCONTROL START
has not been issued yet (i.e., the transport has not been started.)
ACTION: Issue a NETCONTROL START and retry the
operation.
MESSAGE: CONNECTION ABORTED
Level: -70
CAUSE: A TCP Connection was aborted either due to a local error or
due to a remote connection abortion (i.e., a reset packet was received).
ACTION: Use IPC or BSD error code to discover source of
connection abortion.
MESSAGE: RETRANSMISSION RETRIES EXCEEDED
Level: -80
CAUSE: A TCP connection did not receive any acknowledgment from
the remote connection half for a data packet within the configured
number of retransmissions.
ACTION: There are many possible reasons for a retransmission time
out to occur. Potential problems include severe network bottlenecks, remote
system CPU starvation, incorrect or improperly tuned configuration, remote
node failure, gateway or network failure, and servers which are not
processing new connection requests (or which are becoming backlogged).
Check for remote system and network failure first. If there is no problem
reaching the remote system, then the problem is most likely a system or
network load problem. Check CPU usage on remote system and/or network
traffic capacity especially at gateways or over slow (non-LAN) links. Also,
if the problem is at connect time, check that the remote server is
processing connection requests in a timely manner. Also see the NS
3000/iX NMMGR Screens Reference Manual for a discussion on tuning TCP
retransmission parameters.
MESSAGE: RETRANSMISSION TIMEOUT EXCEEDED
Level: -81
CAUSE: A TCP connection did not receive any acknowledgment from
the remote connection half for a data packet within the configured
MAXIMUM TIME TO WAIT FOR REMOTE RESPONSE.
ACTION: There are many possible reasons for a retransmission time
out to occur. Potential problems include severe network bottlenecks, remote
system CPU starvation, incorrect or improperly tuned configuration, remote
node failure, gateway or network failure, and servers which are not
processing new connection requests (or which are becoming backlogged).
Check for remote system and network failure first. If there is no problem
reaching the remote system, then the problem is most likely a system or
network load problem. Check CPU usage on remote system and/or network
traffic capacity especially at gateways or over slow (non-LAN) links. Also,
if the problem is at connect time, check that the remote server is
processing connection requests in a timely manner. Also see the NS
3000/iX NMMGR Screens Reference Manual for a discussion on tuning TCP
retransmission parameters.
MESSAGE: CONNECTION ASSURANCE TIMEOUT
Level: -82
CAUSE: A TCP connection has not received any acknowledgment from
the remote connection half within the configured number of connection
assurance retries; therefore we assume that the remote system half has
experienced an abrupt termination.
ACTION: Check for remote system failure or network failure.
If both the network and the remote system are intact, you may wish
to readjust the time out parameters, or disable the connection assurance
function by configuring a maximum of zero retries.
MESSAGE: PATH FAILURE
Level: -90
CAUSE: The operation failed because TCP was unable to
resolve a path to the remote system.
ACTION: Check for proper network configuration. If the
configuration appears correct, enable Class 5 logging for NS Transport
if not already enabled and locate matching logging entry. Logging
event will indicate Class 5, Subsystem 3, Entity TCP, Location 104xx,
path failure error. Parameter is path resolution error returned. Consult
path resolution error listings to diagnose problem.
MESSAGE: PATH FAILURE
Level: -91
CAUSE: Excessive retransmissions prompted TCP to test
the path to the remote node (an algorithm called active rerouting
or negative advice) and path was reported as lost.
ACTION: Suspect gateway or network failure. If necessary,
enable Class 5 logging for NS Transport if not already
enabled and locate matching logging entry. Logging event will indicate
Class 5, Subsystem 3, Entity TCP, Location 104xx, path
failure error. Parameter is path resolution error returned. Consult
path resolution error listings to diagnose problem.
MESSAGE: RESEGMENTATION FAILURE
Level: -92
CAUSE: In an attempt to adjust to a new path, TCP was
unable to resegment the currently outstanding outbound data to the
new segment size. Most likely this was due to a lack of available
buffers in the outbound pool associated with the new link.
ACTION: To prevent future occurrences, increase the buffer pool
size of the link which TCP failed over to, or diagnose and prevent the
original link failure which caused the fail over.
MESSAGE: DATA AFTER FIN
Level: -100
CAUSE: The remote connection half continued to send data
beyond the advertised final (FIN) sequence number.
ACTION: This is a remote protocol violation. Fix or remove
the offending remote implementation.
MESSAGE: PRECEDENCE FAULT
Level: -101
CAUSE: The remote connection half violated IP precedence
conventions and sent a packet with an incorrect precedence.
ACTION: This is a remote protocol violation. Fix or remove
the offending remote implementation.
MESSAGE: SYN IN WINDOW
Level: -102
CAUSE: A valid SYN packet was discovered within the
window of an already established connection.
ACTION: This is a remote protocol violation. Fix or remove
the offending remote implementation.
MESSAGE: DATA BEFORE CONNECT
Level: -103
CAUSE: The remote connection half has begun to send data
before the connection startup handshake has been completed (i.e.,
before the SYN/ACK was sent).
ACTION: This is a remote protocol violation. Fix or remove
the offending remote implementation.
MESSAGE: SEND ATTEMPT BEFORE NETWORK START
Level: -110
CAUSE: An attempt was made to send data before the network
was started.
ACTION: This is an IPC or BSD sockets internal error.
Please submit an CR.
MESSAGE: EMPTY RETRANSMISSION QUEUE
Level: -120
CAUSE: A TCP connection attempted to remove packets from
its retransmission queue, but no packets were found.
ACTION: This is an internal error in TCP. Please submit
an CR. A protocol or link level trace including TCP header information
will facilitate resolution of this problem.
MESSAGE: UNEXPECTED EXCAPE
Level: -121
CAUSE: An unexpected escape or trap condition was detected by TCP.
ACTION: This is a software error. Please submit an CR.
A detailed description of the network and system state along with
a copy of the program and input which uncovered the error may enhance
timely resolution of this problem.
MESSAGE: UNKNOWN CONTROL OPTION
Level: -121
CAUSE: An unknown control option was passed to TCP from
a call to IPCCONTROL.
ACTION: Identify and remove offending control
option.
Chapter 9 Remote Process Management Error Messages
Complete PDF