Filter
Top Products
RTR log messages
%RTR-E-BADIDSIZ, Bad node ID size [A] detected at 0x[A]
Explanation: This message indicates that errors have been detected in
processing of an internal node identifier. The presence of this message
indicates a serious problem in the configuration of the network name/address
databases, and RTR will likely be unable to operate correctly. Quorum and
fault tolerance will be adversely affected. Check all network databases for
consistency of node & host name and address consistency.
%RTR-E-BADIDTYP, Empty node ID encountered at 0x[A]
Explanation: This message indicates that errors have been detected in
processing of an internal node identifier. The presence of this message
indicates a serious problem in the configuration of the network name/address
databases, and RTR will likely be unable to operate correctly. Quorum and
fault tolerance will be adversely affected. Check all network databases for
consistency of node & host name and address consistency.
%RTR-E-BADNETMSG, Bad message received from [A] - check network
hardware? Indications %u %u %u %u %u %u %u
Explanation: This message is logged when RTR in unable to interpret the
content of a network message received from a remote RTR ACP process.
Message corruption is the most likely culprit. If the condition persists,
consider a network health check. The indication numbers printed at the end
of the message have meaning to RTR support engineers only.
%RTR-I-BEINQUO, Backend is quorate in facility [A]
Explanation: The backend role now has quorum in the facility [A]
%RTR-W-BENOQUO, Backend has no quorum in facility [A]
Explanation: The backend role has lost quorum for facility [A]
%RTR-E-BEREPLAYQDELETED, Replay queue for BE deleted
Explanation: A transaction in progress on a backend has had its (replay)
queue of replies to the client deleted. Please report to RTR Engineering.
%RTR-E-BMHDRVSN, Unrecognised broadcast from [A] for facility [A] - check
network? Indications %u %u %u [A]
Explanation: A node has received an unrecognised broadcast event from the
indicated node. If the sending and receiving nodes are running compatible
versions of RTR, the cause of this might be message corruption. If the
condition persists, consider performing a network health check.
%RTR-F-BRODISBLO, Broadcast message(s) discarded because of network
blockage
Explanation: One or more broadcast messages had to be discarded because
the network throughput is not fast enough. Reduce broadcast rate or increase
communications link capacity.
%RTR-F-BRODISCAC, Broadcast message(s) discarded because of memory cache
congestion
Explanation: One or more broadcast messages had to be discarded because
local memory was exhausted. Reduce the rate at which broadcasts are sent,
or increase the efficiency of broadcast processing by the recipient applications.
E–2 RTR log messages