RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

828
Killing backup process ...
Cause
The primary process of a process pair has detected a problem in communicating with the backup
process. An earlier message will have indicated the communications problem.
Effect
Because of the severity of the problem, the primary process attempts to stop the backup process.
If the backup process stops, the primary process then attempts to create a new backup process.
Recovery
This is an informational message; no recovery is required.
829
An RDF takeover operation was initiated on the backup system
Cause
This message indicates that the monitor detected an RDF takeover operation was executed on
the RDF backup system.
Effect
This is a catastrophic error and will cause the RDF processes on the primary system to stop.
Recovery
You must reinitialize RDF and you might need to synchronize your databases.
830
Warning - Network down when stopping process name
name
is the name of the RDF process that was not stopped.
Cause
The RDF monitor is attempting to stop a process on the backup node but cannot do so because
the communications lines are down.
Effect
If a STOP RDF command was being processed, the RDF monitor continues with the shutdown,
and all processes on the primary system will stop. The backup processes will remain running.
Recovery
To stop the RDF processes on the backup system, you must run RDFCOM on the backup system
and issue a second STOP RDF command.
Once all processes have stopped, RDF can be restarted when the network is restored.
831
RDF fatal error information text
text
is the stack trace.
Cause
An RDF process is terminating abnormally.
Effect
The equivalent of an INSPECT TRACE is written and then the process will abend.
Recovery
This message gives your service provider information about the state of a process that is
terminating abnormally.
382 Messages