Message 100 - Out
of memory
- Explanation:
This message is issued when there is not enough memory
in the system to complete the task requested of znode.
- Action:
Free up some memory resources and try again.
Message 102 - Couldn't
get <name>/<name> service from
/etc/services
- Explanation:
This message is issued when znode fails
to obtain the znode name service from /etc/services.
- Action:
To add the name service manually, refer to preceding topic "Adding
Naming Services".
Message 103 - Couldn't
create socket, error: <reason>
- Explanation:
This message is issued when znode fails
to create a socket.
- Action:
If the reason for the failure is related to shortage
of system resources or that networking subsystem has not been started
up, correct it and retry. For other unresolvable reasons, contact
your HP support representative.
Message 104 - Couldn't
bind to socket, error: <reason>
- Explanation:
This message is issued when znode fails
to bind a socket to an address.
- Action:
If the reason for the failure is related to shortage
of system resources, inadequate access permission, or X.25 line
is not working; correct the problem and retry. For other unresolvable
reasons, contact your HP support representative.
Message 105 - Link
unusable, couldn't resolve linkname <name> to
an IP address
- Explanation:
This message is issued when znode fails
to resolve an internet address for the given hostname or IP address string.
- Action:
Report this problem to your HP support representative.
Message 107 - Couldn't
fork daemon process, error: <reason>
- Explanation:
This message is issued when znode fails
to fork a child.
- Action:
Correct the indicated problem related to excess
number of processes or insufficient swap/physical memory, and retry.
Message 108 - Couldn't
change process group, error: <reason>
- Explanation:
This message is issued when znode fails
to change process group.
- Action:
Report this problem to your HP support representative.
Message 109 - ZCOM
system down, exiting
- Explanation:
This message is issued when znode is
getting ready to exit as a result of detecting that the ZCOM system
is down.
- Action:
None.
Message 110 - Couldn't
open /dev/zremote, error: <reason>
- Explanation:
This message is issued when znode fails
to open the /dev/zremote device file.
- Action:
Correct the problem with the given reason if possible. Otherwise,
contact your HP support representative.
Message 111 - Bad
magic number <number> from read
- Explanation:
This message is issued when znode detects
a read error signified by an erroneous magic number in the message buffer.
- Action:
This problem may occur if the znode program is incompatible
with the ZCOM driver (i.e., different versions). Make sure that
the system has been regenerated and rebooted after it has been updated with
the new ACC software.
Message 112 - Bad
message type <number> from read
- Explanation:
This message is issued when znode detects
a read error signified by an erroneous message type in the buffer.
- Action:
Report this problem to your HP support representative.
Message 113 - Unknown
destination node <number>
- Explanation:
This message is issued when znode fails
to get a node entry from a node number in the symbol table.
- Action:
This is a znode internal error. Report this problem
to your HP support representative.
Message 115 - Error
on write: <reason>
- Explanation:
This message is issued when znode detects
an error on writing to the LDM.
- Action:
Report this problem to your HP support representative.
Message 116 - Bad
magic number <number> from write
- Explanation:
This message is issued when znode detects
a bad magic number error in the message buffer which znode tries to
write to the LDM.
- Action:
Report this problem to your HP support representative.
Message 117 - Message
len (<number>) doesn't match result from write(<reason>)
- Explanation:
This message is issued when znode detects
that there is a mismatch in message length between the length of the
message buffer and the length resulted from the write operation
performed on the LDM.
- Action:
Report this problem to your HP support representative.
Message 119 - Error
accessing /dev/zremote: <reason>
- Explanation:
This message is issued when znode fails
to access /dev/zremote.
- Action:
Report this problem to your HP support representative.
Message 120 - Duplicate
linkname <name> ignored, same as <name>.
- Explanation:
This message is issued when znode detects
two links with identical addresses; and hence one of the links is ignored.
- Action:
None.
Message 121 - Warning:
Could not set RT priority (errno=<number>:<reason>)
- Explanation:
This message is issued when znode fails
to set real time priority.
- Action:
None.
Message 122 - Warning:
Could not set memory lock (errno=<number>:<reason>)
- Explanation:
This message is issued when an attempt to lock znode in memory failed.
- Action:
None.
Message 123 - Can't
create /dev/zremote, error: <reason>
- Explanation:
This message is issued when znode fails
to create the/dev/zremote device file.
- Action:
Correct the problem with the given reason if possible. This
device file can be created manually using mknod (refer to the ACC
Installation and Configuration Guide, Appendix A on "Device
Files") with read and write access. If this also fails,
contact your HP support representative.
Message 124 - Can't
get the znode semaphore: <reason>
- Explanation:
This message is issued when znode fails
to obtain the znode semaphore.
- Action:
Report this problem to your HP support representative.
Message 125 - znode
daemon is already active, terminating this copy
- Explanation:
This message is issued when znode detects
that the znode daemon is already active in the system; hence this
copy will be terminated.
- Action:
None.
Message 126 - Message
from node %d discarded/ Too long (%d bytes)
- Explanation:
A message from the specified remote node was too
long. The message was discarded. The maximum sized message supported
is 65,534 bytes. The local node received a remote message/request
which exceeded this length.
- Action:
Check the application implementation and verify
that the maximum message length for remote request is not exceeded.
If the application is correctly coded, this may be an internal defect
and you should contact your local HP representative.
Message 127 - Error
on socket recvfrom() call (errno=%d:%s)
- Explanation:
System call recvfrom() failed with the given error.
- Action:
Examine the system error returned (errno) and take corrective
action.
Message 128 - Possible
socket read truncation. Received %d bytes. Expected %d bytes.
- Explanation:
A message received from a remote node was shorter than
expected. Data may have been lost. This is an internal error.
- Action:
Contact your local HP representative.
Message 129 - Unknown
source node %d.
- Explanation:
The local node received a message from a node that
is not configured in the local .answ file.
- Action:
Review the node configuration on all nodes to ensure
it is consistent.
Message 130 - Unknown
link for source node %d.
- Explanation:
The IP address from which the remote request arrived does
not match any of the IP addresses defined for the links on that
node in the local TTGEN .answ file.
- Action:
Review the node configuration on all nodes to ensure
it is consistent.
Message 131 - Remote
node %d marked down. Packet on queue %d seconds
- Explanation:
The local node received a partial message from the remote
node, but the full message was not received within the allowed amount
of time. The status of the remote node has been set to "down".
This could be due to the remote node, itself, physically failing
or to a failure in the communications link.
- Action:
Determine why the remote node is down and take corrective
action. Note that communication will automatically resume once the
link between the two systems has been reestablished.
Message 132 - Bad
packet revision %d received from node %d. Packet dropped.
- Explanation:
The znode program on the remote node is not of a compatible
revision with the znode program on the local node. All ZCOM nodes
which communicate using the ZNODE functionality must have identical
revision of the ACC software installed.
- Action:
Update the remote node with the same version of
the ACC products as the local node. (Note that the znode program
is supplied with the ACC Base Software product as well as the X.25/ACC
Bundled ACC product.)
Message 133 - Msg
rcvd for wrong node: Local =%d, dest=%d, sender=%d.
- Explanation:
The local node received a message from a remote system
that was not addressed to the local node. This is an internal znode
error.
- Action:
Contact your local HP representative.
Message 134 - LDM
info rcvd for %d nodes; znode runstring only configured %d.
- Explanation:
The number of nodes specified in the ZNODE runstring (-N <#>)
was less than the number of nodes defined in the local TTGEN .answ
configuration file.
- Action:
Schedule znode with a larger parameter for the -N option,
or reduce the number of remote nodes defined in the TTGEN configuration
file.
Message 135 - Possibly
remote node %d is running old, incompatible znode software!
- Explanation:
The znode program on the remote node is not of a compatible
revision with the znode program on the local node.
- Action:
Update the remote node with the same version of
the ACC products as the local node. (Note that the znode program
is supplied with the ACC Base Software product as well as the X.25/ACC
Bundled ACC product.)
Printable version
