RMS consists of a number of individual programs that contribute to the overall high availability management. Each of these programs can generate its own trace and error messages in a dedicated log file, which can be found at
RELIANT_LOG_PATH/<program_name>log
For example, the RMS base monitor program is named bm, and its dedicated log file is RELIANT_LOG_PATH/bmlog.
Program trace and error messages are intended for internal troubleshooting purposes only. The format is described here in case you are asked to provide the information to a PRIMECLUSTER consultant.
Trace messages have the following prefix:
timestamp: file: line:
Error messages have the following prefix:
timestamp: file: line: ERROR
Here is an example of a short sequence of trace messages:
2005-12-17 14:42:46.256: det_generic.C: 756: Return from GdCheck 2005-12-17 14:42:46.256: det_generic.C: 773: Call to GdGetAttribute 2005-12-17 14:42:46.257: det_generic.C: 775: Return from GdGetAttribute 2005-12-17 14:42:46.257: det_generic.C: 790: reporting state to bm
