ACC Error Guide

ZCOM Driver Log Messages
ZCOM Driver Messages
Chapter 5 97
zcom 00163: ZNODE has terminated, all nodes set DOWN
Explanation: This message is logged when the LDM detects that
ZNODE has terminated. ZNODE could have
terminated abnormally (core dump), been killed (kill
-9), or the user could have shutdown znode (zmasterd
deact znode). The LDM will mark all remote nodes as
down. In addition, the local node is also marked down
to indicate that ZNODE is no longer running. Any
requests requiring remote node access are rejected
with error ZENDOWN (-61, Remote node is DOWN).
This message may or may not indicate a problem.
Action: If znode was killed or deactivated using zmasterd, the
message is normal and can be ignored. However, if the
application expects to make requests to remote ZCOM
nodes, corrective action is needed. If it is determined
that ZNODE is terminating abnormally, contact your
HP Support Representative.
zcom 00164: Node <#> has gone DOWN
Explanation: This message is logged when the local system is no
longer receiving heartbeat messages from the indicated
remote node. This means either the communication
link(s) has gone down, the remote node has failed, or
the remote ZNODE has been shutdown. The indicated
remote node is now inaccessible. All remote requests to
this node are rejected with error ZENDOWN (-61,
Remote node is DOWN).
Action: Check the relevant ZCOM message log files for other
related error messages. Correct the problems as
needed.
zcom 00165: Node <#> is now UP
Explanation: This message is logged when a remote node previously
marked as down begins to receive heartbeat messages
(or request) from the indicated remote node. The
remote node can now be accessed and any request
issued to this node will be processed normally.
Action: None. This is an informational message.